Agent Team template
Inspect one website for visible signup, pricing, and messaging friction. Return evidence-backed findings and suggested fixes, without submitting forms.
One-message setup · 2 specialists · Managed browser · Browser setup required
Provide one authorized HTTPS URL and its allowed domain. Hosted Browser availability and model funding are required. BYOK does not cover hosted compute. No live run has been verified for this template.
Example input, expected output, and recovery guideDesigned for
Product, support, and operations teams that need evidence from a website without an API or browser extension
Outcome
Inspect only the supplied page for visible friction in its value proposition, pricing clarity, signup links, and form labels. Use read-only observations; do not submit forms, create accounts, accept terms, or purchase. Return prioritized findings with visible evidence, confidence, and suggested fixes. Distinguish an observed defect from a conversion hypothesis. Do not invent conversion rates or claim a full mobile, checkout, or accessibility audit from a single viewport.
Say what should be true when the work is done.
Codelit runs one labeled Sample with no account, model, or external App calls.
Review the evidence, then reuse the same brief with your data when it is useful.
Completes one bounded website goal through policy-validated accessible actions.
Fast structured planning model
Turns the final page evidence into a concise owner-ready result.
Balanced reasoning model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for Website Conversion Check.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
tools · resources · prompts
Pursue the configured website goal through the Browser Operator and return final evidence.
Using only the collected page evidence, return at most five findings with source reference, observed issue, likely impact labeled as a hypothesis, confidence, and suggested fix. State the inspected URL and viewport if known. Mark untested mobile, form submission, and checkout journeys explicitly. Do not claim measured conversion improvement.
Open it in Codelit and describe the result. Codelit handles common setup while Flow stays available for direct editing and Activity keeps the proof.
Use this teamA code-first support agent built around specialist ownership, function tools, MCP resources, guardrails, traces, and eval loops so customer answers can move fast without leaking account state.
An n8n-centered workflow that turns a business automation request into a tested app workflow with conditional logic, human-in-the-loop checks, cost controls, and failed-run repair notes.
A controlled workflow for small teams that want an internal agent to answer operational questions, create tickets, inspect connected apps, and prepare approved actions across the company stack.