Follow your quickstart guide and report where it breaks
Each step of your guide tried in the product, with the steps that are wrong, unclear or out of date.
- You start it: When you start it
What it does
The task
Open the guide at guide url and follow each step in the product at app url with the test account from the vault. Compare the names of menus, buttons and fields, and the screenshots, with what you see. Check each code sample against the API reference at api reference url: the endpoints, the parameter names and the versions. Do not run code, and change only the settings that the guide tells you to change. Write a list of each step with a result of works, wrong, unclear or out of date, and a fix for each problem.
- It works in any website and Google Docs, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- It runs once, when you start it.
What you give it
| Blank | What to give | Example |
|---|---|---|
| guide url | The link to the guide | https://docs.brightleaf.app/quickstart |
| app url | The link to the product | https://app.brightleaf.app |
| api reference url | The link to the API reference | https://docs.brightleaf.app/api |
What you get back
An example run with the example values above. Your run uses your own data.
Quickstart: 9 steps, 4 problems
1. Create an API key: Wrong. The menu is now Settings, Developers.
2. Install the SDK: Works.
3. Send the first request: Out of date. The sample uses /v1/items, the reference lists /v2/items.
4. Add a webhook: Unclear. The guide does not say which events to select.
5. Read the webhook payload: Out of date. The screenshot shows the old dashboard.
6 to 9: Works.
Saved as "Quickstart check, 4 Nov" with a fix for each problem.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 3 blanks
Type guide url, app url and api reference url. Tab moves to the next blank.
- 03
Run it
Run sends it to the agent. Follow each step in the panel, and stop it at any time.
From the terminal
cuiar exec "Open the guide at https://docs.brightleaf.app/quickstart and follow each step in the product at https://app.brightleaf.app with the test account from the vault. Compare the names of menus, buttons and fields, and the screenshots, with what you see. Check each code sample against the API reference at https://docs.brightleaf.app/api: the endpoints, the parameter names and the versions. Do not run code, and change only the settings that the guide tells you to change. Write a list of each step with a result of works, wrong, unclear or out of date, and a fix for each problem."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call run_task yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool run_task to run my "Follow your quickstart guide and report where it breaks" template with guide url = https://docs.brightleaf.app/quickstart; app url = https://app.brightleaf.app; api reference url = https://docs.brightleaf.app/api.Setup for other agents: AI agents.
The tool call
{
"name": "run_task",
"arguments": {
"task": "Open the guide at https://docs.brightleaf.app/quickstart and follow each step in the product at https://app.brightleaf.app with the test account from the vault. Compare the names of menus, buttons and fields, and the screenshots, with what you see. Check each code sample against the API reference at https://docs.brightleaf.app/api: the endpoints, the parameter names and the versions. Do not run code, and change only the settings that the guide tells you to change. Write a list of each step with a result of works, wrong, unclear or out of date, and a fix for each problem."
}
}Related templates
All engineering templatesEngineering
Check web pages for accessibility problems
WCAG 2.2 AA problems on each page, with the element, the rule and a fix, the blockers first.
You start it: When you start it- Any website
- Google Docs
Engineering
Compare staging with production before a release
Text, layout and console differences page by page, with the ones that look like bugs marked.
You start it: When you start it- Any website
- Google Docs
Engineering
Check your pages at phone, tablet and desktop sizes
Layout problems at each screen width, with a screenshot and the element that breaks.
You start it: When you start it- Any website
- Google Docs
Engineering
Write an incident postmortem from the timeline
A blameless draft with the timeline, impact, cause and actions, built from chat, monitors and deploys.
You start it: When you start it- SSlack
- Datadog
- GitHub
- +1 more: Google Docs
ResearchOdyssey
Research a topic into a cited report
Many sources, compared, in one report with a citation for each claim.
You start it: When you start it- Google Scholar
- Wikipedia
- Google Docs
ResearchOdyssey
Write a literature review on a research question
Recent studies grouped by theme, what they agree on, where the evidence is weak, and a full reference list.
You start it: When you start it- Google Scholar
- Semantic Scholar
- PubMed
- +1 more: Google Docs