Execute complex tasks across multiple Claude Code sessions with automatic continuation,
Works with
progress tracking, and two completion mechanisms (promise tags + checkbox counting).
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionautonomous-skillExecute the skills CLI command in your project's root directory to begin installation:
Fetches autonomous-skill from feiskyer/claude-code-settings 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 autonomous-skill. Access via /autonomous-skill 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.4K
stars
Execute complex tasks across multiple Claude Code sessions with automatic continuation, progress tracking, and two completion mechanisms (promise tags + checkbox counting).
Spawns claude -p child sessions in a bash loop. Best for background/unattended work.
bash <skill-dir>/scripts/run-session.sh "Build a REST API" --max-sessions 10
Uses a Stop hook to intercept session exit and feed the prompt back. Runs inside the current interactive session — no nesting issues.
bash <skill-dir>/scripts/setup-loop.sh "Build a REST API" --max-iterations 10
Full task decomposition: Initializer creates task_list.md with phased sub-tasks,
Executor picks up and completes them one by one. Best for complex, multi-phase projects.
bash <skill-dir>/scripts/run-session.sh "Build a REST API for todo app"
--lightweight)Ralph-style iteration: same prompt repeated each session, no task decomposition. Best for iterative tasks with clear success criteria (TDD, bug fixing, refactoring).
bash <skill-dir>/scripts/run-session.sh "Fix all failing tests in src/" --lightweight
Two complementary mechanisms — whichever triggers first wins:
Promise tags (both modes): The agent outputs <promise>DONE</promise> when
work is genuinely complete. Default promise is DONE; customize with
--completion-promise. The agent is instructed to only output the promise when
the work is truly finished — not to escape the loop.
Checkbox counting (structured mode only): All [ ] items in task_list.md
are marked [x].
project-root/
├── .autonomous/
│ └── <task-name>/
│ ├── task_list.md # Master checklist (structured mode)
│ ├── progress.md # Per-session progress log
│ ├── .mode # "structured" or "lightweight"
│ ├── sessions/ # Transcript logs per session
│ │ ├── session-001.log
│ │ └── session-002.log
│ └── run.lock # Prevents concurrent runs
└── .claude/
└── autonomous-loop.local.md # Hook mode state (when active)
bash <skill-dir>/scripts/run-session.sh "task description" [OPTIONS]
| Flag | Description | Default |
|---|---|---|
--lightweight |
Ralph-style iteration (no task decomposition) | structured |
--task-name <name> |
Explicit task name | Auto-generated |
--continue, -c |
Continue most recent or named task | — |
--list, -l |
List all tasks with progress | — |
--completion-promise TEXT |
Promise phrase for completion | DONE |
--max-sessions N |
Stop after N sessions | Unlimited |
--max-budget N.NN |
Per-session dollar budget | 5.00 |
--model <model> |
Model alias or full name | sonnet |
--fallback-model <m> |
Fallback if primary overloaded | — |
--effort <level> |
Thinking effort (low/medium/high) | high |
--no-auto-continue |
Run one session only | — |
--permission-mode <m> |
Permission mode | auto |
--add-dir <dirs> |
Extra directories to allow | — |
For in-session loops (no child process spawning):
bash <skill-dir>/scripts/setup-loop.sh "task description" [OPTIONS]
| Flag | Description | Default |
|---|---|---|
--mode structured|lightweight |
Task strategy | structured |
--max-iterations N |
Max loop iterations | Unlimited |
--completion-promise TEXT |
Promise phrase | DONE |
--task-name NAME |
Explicit task name | Auto-generated |
The hook is registered in hooks/hooks.json. When active, the Stop hook reads
.claude/autonomous-loop.local.md and blocks exit until the promise is detected
or max iterations reached.
To cancel an active hook-mode loop: rm .claude/autonomous-loop.local.md
task_list.md, begins work| Scenario | Strategy | Mode |
|---|---|---|
| Build a full application | Structured | Headless |
| Fix all failing tests | Lightweight | Either |
| Refactor a module | Lightweight | Either |
| Multi-phase project | Structured | Headless |
| Quick iterative fix | Lightweight | Hook |
| Overnight batch work | Structured | Headless |
[ ] → [x].autonomous/ is only for tracking<promise>DONE</promise> until genuinely complete--max-budget| Issue | Solution |
|---|---|
| "Lock file exists" | Previous run crashed. Remove .autonomous/<task>/run.lock |
| Session keeps failing | Check sessions/session-NNN.log for errors |
| Nested session error | Script auto-unsets CLAUDECODE; use hook mode as alternative |
| Hook loop won't stop | Delete .claude/autonomous-loop.local.md |
| Task not found | Run --list to see available tasks |
| Want to restart | Delete the task directory and start fresh |
| Cost too high | Lower --max-budget or use --model sonnet |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: autonomous-skill is focused, and the summary matches what you get after install.
autonomous-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: autonomous-skill is focused, and the summary matches what you get after install.
autonomous-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added autonomous-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
autonomous-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added autonomous-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
autonomous-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: autonomous-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added autonomous-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 29