Agent skill · Workflow & Productivity

autonomous-skill

Use when user wants to execute long-running tasks that require multiple sessions to complete. This skill manages task decomposition, progress tracking, and autonomous execution using Codex non-interactive mode with auto-continuation. Trigger phrases include autonomous, long-running task, multi-session, 自主执行, 长时任务, autonomous skill.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill autonomous-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/agent/autonomous-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Autonomous Skill - Long-Running Task Execution Execute complex, long-running tasks across multiple sessions using a dual-agent pattern (Initializer + Executor) with automatic session continuation via Codex non-interactive mode. ## Quick Start Use the `run-session.sh` script to manage autonomous tasks: ```bash # Start a new autonomous task ~/.codex/skills/autonomous-skill/scripts/run-session.sh "Build a REST API for todo app" # Continue an existing task ~/.codex/skills/autonomous-skill/scripts/run-session.sh --task-name build-rest-api-todo --continue # List all tasks and their progress ~/.codex/skills/autonomous-skill/scripts/run-session.sh --list # Show help ~/.codex/skills/autonomous-skill/scripts/run-session.sh --help ``` ## Directory Structure All task data is stored in `.autonomous/<task-name>/` under the project root: ```text project-root/ └── .autonomous/ ├── build-rest-api/ │ ├── task_list.md # Master task checklist │ ├── progress.md # Session-by-session notes │ ├── session.id # Last Codex session ID for resumption │ └── session.log # JSON Lines output from sessions ├── refactor-auth/ │ ├── task_list.md │ ├── progress.md │ └── session.id └── ... ``` This allows multiple au

What's inside
Steps it walks through
  1. Quick Start
  2. Directory Structure
  3. Script Options
  4. Workflow Overview
  5. Usage Examples
  6. Example 1: Start New Task
  7. Example 2: Continue Existing Task
  8. Example 3: Resume with Session Context
  9. Example 4: List All Tasks
  10. Example 5: With Network Access
  11. Key Files
  12. Important Notes
  13. Codex CLI Reference
  14. Troubleshooting
Ships with 1 file
  • metadata.json
Commands it runs
Start a new autonomous task
Continue an existing task
List all tasks and their progress
Show help
Resume the Codex session (preserves conversation context)
Enable network access for tasks that need API calls
Non-interactive execution with file edits (fully autonomous)
codex exec --full-auto --json "prompt"
Resume previous session
codex exec --full-auto --json resume <SESSION_ID> "prompt"
More from claude-skill-registry
All skills →
About this skill
What does the autonomous-skill skill do?

Use when user wants to execute long-running tasks that require multiple sessions to complete. This skill manages task decomposition, progress tracking, and autonomous execution using Codex non-interactive mode with auto-continuation. Trigger phrases include autonomous, long-running task, multi-session, 自主执行, 长时任务, autonomous skill.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill autonomous-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going