You are setting up a loop — an iterative worker/verifier cycle managed by the Paseo daemon.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpaseo-loopExecute the skills CLI command in your project's root directory to begin installation:
Fetches paseo-loop from getpaseo/paseo and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate paseo-loop. Access via /paseo-loop in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
645
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
645
stars
You are setting up a loop — an iterative worker/verifier cycle managed by the Paseo daemon.
User's arguments: $ARGUMENTS
Load the Paseo skill first. It contains the CLI reference for paseo loop and related commands.
A loop repeats: launch a worker → verify → repeat until done or limits hit.
Every loop needs at least one form of verification:
--verify "<prompt>" — a verifier agent judges the worker's output--verify-check "<command>" — a shell command that must exit 0 (repeatable)Choose the right provider/model for worker and verifier independently:
--provider <provider/model> — sets the worker (e.g. codex/gpt-5.4)--verify-provider <provider/model> — sets the verifier (e.g. claude/opus)Default: both use Claude/sonnet. For implementation loops, use Codex for the worker and Claude for the verifier — each catches the other's blind spots.
--archive preserves worker and verifier agents after each iteration instead of destroying them. Use this when you need to inspect conversation history for debugging.
paseo loop run "Check PR #42. Review CI, comments, and branch status. Fix issues as they arise." \
--verify-check "gh pr checks 42 --fail-fast" \
--sleep 2m \
--max-time 1h \
--name babysit-pr-42
paseo loop run "Run the test suite, investigate failures, and fix the code." \
--provider codex/gpt-5.4 \
--verify "Run the test suite. Return done=true only if all tests pass. Cite the exact command and outcome." \
--verify-check "npm test" \
--max-iterations 10 \
--name fix-tests
paseo loop run "Implement issue #456. Make incremental progress each iteration." \
--provider codex/gpt-5.4 \
--verify "Verify issue #456 is complete. Check changed files, run typecheck and tests." \
--verify-provider claude/sonnet \
--max-iterations 8 \
--max-time 2h \
--archive \
--name issue-456
paseo loop ls # List all loops
paseo loop inspect <id> # Show details and iteration history
paseo loop logs <id> # Stream logs
paseo loop stop <id> # Stop a running loop
$ARGUMENTSpaseo loop run with the final argumentsThe worker prompt must be:
The verifier prompt should:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
kostja94/marketing-skills
JuliusBrussee/caveman
dengineproblem/agents-monorepo
We added paseo-loop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: paseo-loop is focused, and the summary matches what you get after install.
I recommend paseo-loop for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
paseo-loop has been reliable in day-to-day use. Documentation quality is above average for community skills.
paseo-loop fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: paseo-loop is the kind of skill you can hand to a new teammate without a long onboarding doc.
paseo-loop reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend paseo-loop for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for paseo-loop matched our evaluation — installs cleanly and behaves as described in the markdown.
paseo-loop reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 70