Set up coding agents
Connect coding agents to Composal with skills and MCP tools. Set up browser verification, maintain product knowledge, and inspect recorded run evidence.
Contents
Verify with an agent
Connect your assistant to Verify MCP to prepare environments and scenarios, launch hosted browser runs, and inspect evidence. The remote connector needs no local CLI installation. For a coding harness, install the CLI and add Composal skills with the setup commands below.
Use the single composal skill for setup, Scenario authoring and upload, project test runs, and deployment. Its focused references load only when needed. Project runs preserve their prepared definitions and return browser evidence for review.
For recurring checks, use Verify schedules. Agree the target, permitted actions, personas, and expected outcomes before automating the run.
Choose capabilities
Choose the integrations your agent needs:
- Skills provide durable guidance for safe Composal workflows.
- MCP tools let the agent configure verification, launch runs, and inspect results, as well as act on other Composal resources.
Install skills for workflow guidance, and add MCP when you want the agent to use Composal tools directly.
Install and inspect
Start with the compact composal skill. It directs your agent to the installed command guide, schemas, JSON receipts, and recovery steps. Run these commands from your project directory; source control is optional:
com skills install --targets codex --dry-run --json
com skills install --targets codex --json
com skills setup performs the same installation. The skill lives at .agents/skills/composal/SKILL.md, with workflows under references/. The skill focuses on testing: its QA planning workflow reads your code, Composal knowledge, and plans to set up Scenarios. Add --with deploy to also install the com-deploy deployment skill. Use --targets claude-code,cursor for those agents, or omit --targets to detect installed agents. If none are detected, the skill is still installed into the project's shared skills folder. Rerun installation to refresh the skill and its references. Unmodified older product skills are consolidated; local edits and unrelated skills are preserved. Use com skills install --help for options.
Inspect the skill and read a focused workflow offline:
com skills list --json
com skills get composal
com skills get --topic scenarios
com skills get --topic tests
Use com skills setup --targets codex,claude-code,cursor --mcp to install the same single skill and configure the local MCP server. Setup stays project-local; global and source-control skill installations are managed separately. If your CLI lacks com skills, run com update once. Until the new CLI release is available, agents can read /agent.md directly and use the installed command schemas.
Research product knowledge
Ask your agent to research a feature, explain its user flows and prerequisites, and save what it learns with com knowledge. It can list and search project documents, read their Markdown and sources, add new guides, and edit existing topics with conflict protection.
Keep requirements, observations, and open questions clear. This knowledge helps future discovery and verifier runs navigate the product and interpret what they see. Store credentials in Verify's secure account forms.
Machine-readable docs
Start at /llms.txt for a categorized index of agent-readable documentation and integration guides.
Append .md to any documentation URL to read the same page as Markdown, without the site navigation or JavaScript. For example, use /docs/quickstart.md, /docs/verify.md, or /docs.md for the overview. HTML documentation pages advertise their Markdown alternate in a rel="alternate" link.
Composal also serves separate Markdown and JSON endpoints for agent integrations:
/agent.md: the compact Composal CLI skill, also available throughcom skills get composal./skill.md/skills/index.json/docs/import/prompt.md
Those endpoints have stable machine-oriented contracts and remain separate from the public docs navigation.