Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问clear审计未展示

claude-code-x---autonomous-execution-subagentClaude 代码 X autonomous execution subagent

Agent Skill

claude-code-x---autonomous-execution-subagent 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

12,914

周安装

406

GitHub Stars

31

下载量

3,001
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:claude-code-x---autonomous-execution-subagent(Claude 代码 X autonomous execution subagent)
来源仓库:https://github.com/shunsukehayashi/miyabi-claude-plugins
仓库路径:skills/claude-code-x---autonomous-execution-subagent
安装命令:
npx skills add https://github.com/shunsukehayashi/miyabi-claude-plugins --skill 'Claude Code X - Autonomous Execution Subagent'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/shunsukehayashi/miyabi-claude-plugins --skill 'Claude Code X - Autonomous Execution Subagent'

简介

claude-code-x-autonomous-execution-subagent 支持后台自主执行多个独立任务,最大并发数 5。

  • 适用于无需用户干预的批量作业,如并行处理相似 Issue 或自动化测试套件。
  • 采用背景模式运行,不影响主会话操作,适合多任务并行提升整体产出效率。
  • 禁止用于需要实时反馈或交互式调试的场景,仅限确定性强、模式清晰的任务流。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Claude Code X - Autonomous Execution Subagent

Type: Task Execution Agent Mode: Background Autonomous Version: 1.0.0


🎯 Purpose

Execute Claude Code autonomously in the background for well-defined tasks, enabling parallel execution of up to 5 concurrent sessions while the user continues other work.


🚀 When to Use This Skill

✅ Use When:

  • You have 3+ independent, well-defined tasks
  • Tasks don't require user interaction during execution
  • You want to maximize throughput with parallel execution
  • User can benefit from multitasking during execution
  • Tasks follow clear patterns (e.g., similar Issues)

❌ Don't Use When:

  • Task requires user decisions during execution
  • Requirements are unclear or exploratory
  • Task has complex dependencies on other running tasks
  • Immediate interactive feedback is needed

📋 Capabilities

Core Features

  • Parallel Execution: Run up to 5 Claude Code sessions concurrently
  • Session Management: JSON-based persistence and lifecycle tracking
  • Background Operation: Non-blocking, allows user to continue other work
  • Timeout Control: Configurable timeout (default 10 minutes)
  • Result Retrieval: Access full output logs after completion
  • Session Monitoring: Check status and progress in real-time

Session Lifecycle

  1. Spawn: Create new background Claude Code session
  2. Execute: Run task autonomously with specified tools
  3. Monitor: Check status and output
  4. Complete: Retrieve results and clean up

🛠️ Usage

Basic Execution

Please use the Claude Code X skill to execute the following task in the background:

"Implement logging for the authentication module in crates/miyabi-auth/src/lib.rs"

Parallel Batch Execution

Use Claude Code X to execute these 5 tasks in parallel:

1. Add logging to crates/miyabi-auth/src/lib.rs
2. Add logging to crates/miyabi-database/src/lib.rs
3. Add logging to crates/miyabi-api/src/lib.rs
4. Add logging to crates/miyabi-cache/src/lib.rs
5. Add logging to crates/miyabi-worker/src/lib.rs

Monitor their progress and report when all are complete.

With Custom Configuration

Use Claude Code X with:
- Timeout: 15 minutes
- Tools: Bash, Read, Write, Edit, Grep
- Task: "Refactor error handling in crates/miyabi-core/src/errors.rs"

🎬 Implementation Instructions

When this skill is invoked, execute the following steps:

Step 1: Validate Task

Check that the task is:

  • Well-defined with clear success criteria
  • Independent (no dependencies on user input)
  • Suitable for autonomous execution

If unclear, ask user for clarification before proceeding.

Step 2: Execute with Shell Script

Use the claude-code-x.sh shell script:

# Execute task
./.claude/commands/claude-code-x.sh exec "Task description here"

# Optional: Custom configuration
./.claude/commands/claude-code-x.sh exec "Task description" \
  --timeout 900 \
  --tools "Bash,Read,Write,Edit,Glob,Grep"

Step 3: Capture Session ID

The script will output:

✅ Session started successfully
🔗 Session ID: claude-code-x-20251027-123456-abc123
🔗 PID: 12345

Store this session ID for monitoring.

Step 4: Monitor Progress (Optional)

During execution, you can check status:

# Check status
./.claude/commands/claude-code-x.sh status claude-code-x-20251027-123456-abc123

# List all sessions
./.claude/commands/claude-code-x.sh sessions

Step 5: Retrieve Results

After completion, get full output:

./.claude/commands/claude-code-x.sh result claude-code-x-20251027-123456-abc123

Step 6: Report to User

Provide summary:

  • Session ID
  • Execution time
  • Exit code (0 = success)
  • Files modified
  • Any issues encountered

📊 Best Practices

Task Breakdown

Good Task:
"Add comprehensive logging to crates/miyabi-auth/src/lib.rs:
- Log all function entries/exits
- Log all errors with context
- Use tracing::info!, tracing::error!
- Include test coverage"

Bad Task:
"Fix the auth module" (too vague)
"Implement OAuth" (needs user decisions)

Parallel Execution Strategy

Pattern 1: Similar Tasks (Ideal)

Task 1: Add logging to module A
Task 2: Add logging to module B
Task 3: Add logging to module C
Task 4: Add logging to module D
Task 5: Add logging to module E

→ All 5 tasks in parallel (max efficiency)

Pattern 2: Phased Execution (Good)

Phase 1 (parallel): Infrastructure setup tasks
  - Task 1: Create config struct
  - Task 2: Add database schema
  - Task 3: Implement Redis cache

Phase 2 (interactive): Critical logic (use regular Claude Code)

Phase 3 (parallel): Provider implementations
  - Task 4: Google provider
  - Task 5: GitHub provider
  - Task 6: Discord provider

Error Handling

If a session fails:

  1. Check the log file for error details
  2. Determine if it's retryable
  3. Fix any issues (e.g., missing files)
  4. Re-execute with corrected task description

🔍 Session Management Commands

List Active Sessions

./.claude/commands/claude-code-x.sh sessions

Check Session Status

./.claude/commands/claude-code-x.sh status <session-id>

Get Full Results

./.claude/commands/claude-code-x.sh result <session-id>

Kill Running Session

./.claude/commands/claude-code-x.sh kill <session-id>

Cleanup Old Sessions

./.claude/commands/claude-code-x.sh cleanup

⚙️ Configuration

Environment Variables

# Session directory (default: .ai/sessions/claude-code-x)
export CLAUDE_CODE_X_SESSION_DIR=".ai/sessions/claude-code-x"

# Log directory (default: $SESSION_DIR/logs)
export CLAUDE_CODE_X_LOG_DIR="$SESSION_DIR/logs"

# Max concurrent sessions (default: 5)
export CLAUDE_CODE_X_MAX_SESSIONS=5

# Default timeout in seconds (default: 600 = 10 minutes)
export CLAUDE_CODE_X_TIMEOUT=600

Default Tools

The following tools are enabled by default:

  • Bash (command execution)
  • Read (file reading)
  • Write (file writing)
  • Edit (file editing)
  • Glob (file pattern matching)
  • Grep (content search)

Permission Mode

  • Default: acceptEdits (auto-accept file edits)
  • Can be changed to ask for approval prompts

📈 Performance Characteristics

Speed

  • Overhead: ~2-3 seconds per session spawn
  • Execution: Similar to interactive Claude Code
  • Parallel: Up to 5x throughput with 5 concurrent sessions

Resource Usage

  • Memory: ~200MB per session
  • Disk: ~1MB per session log
  • CPU: Minimal (most time spent in AI inference)

Limits

  • Max Sessions: 5 concurrent (configurable)
  • Max Timeout: 10 minutes default (configurable up to 30 min)
  • Log Retention: Logs persist until manual cleanup

🎓 Examples

Example 1: Single Task

User Request: "Add logging to the auth module"

Agent Action:

./.claude/commands/claude-code-x.sh exec \
  "Add comprehensive logging to crates/miyabi-auth/src/lib.rs:
  - Log all function entries/exits with tracing::info!
  - Log all errors with tracing::error!
  - Include request IDs in log context
  - Add tests for logging behavior"

Agent Response:

✅ Started Claude Code X session: claude-code-x-20251027-100000-abc123
📝 Executing task in background (timeout: 10 minutes)
💡 Monitor with: /claude-code-x status claude-code-x-20251027-100000-abc123

I'll check back in 2 minutes to see progress.

Example 2: Parallel Batch

User Request: "Add logging to all 5 core modules"

Agent Action:

# Launch 5 parallel sessions
./.claude/commands/claude-code-x.sh exec "Add logging to crates/miyabi-auth/src/lib.rs"
./.claude/commands/claude-code-x.sh exec "Add logging to crates/miyabi-database/src/lib.rs"
./.claude/commands/claude-code-x.sh exec "Add logging to crates/miyabi-api/src/lib.rs"
./.claude/commands/claude-code-x.sh exec "Add logging to crates/miyabi-cache/src/lib.rs"
./.claude/commands/claude-code-x.sh exec "Add logging to crates/miyabi-worker/src/lib.rs"

Agent Response:

✅ Started 5 parallel Claude Code X sessions:
1. claude-code-x-20251027-100000-abc123 (auth)
2. claude-code-x-20251027-100015-def456 (database)
3. claude-code-x-20251027-100030-ghi789 (api)
4. claude-code-x-20251027-100045-jkl012 (cache)
5. claude-code-x-20251027-100100-mno345 (worker)

Estimated completion: ~5 minutes
I'll monitor progress and report when all complete.

Example 3: Phased Hybrid

User Request: "Implement OAuth 2.0 authentication"

Agent Action (Pattern 3: Hybrid Orchestration):

Phase 1: Planning (Interactive)
- Breaking down OAuth into discrete tasks...

Phase 2: Infrastructure (Claude Code X - Parallel)
- Spawning 3 sessions for config, DB, Redis...

Phase 3: Core Flow (Interactive)
- Implementing security-critical OAuth flow interactively...

Phase 4: Providers (Claude Code X - Parallel)
- Spawning 3 sessions for Google, GitHub, Discord providers...

Phase 5: Testing (Interactive)
- Reviewing all code and creating integration tests...

Result: 42 minutes (30% faster than all-interactive)

🔗 Related Documentation


🐛 Troubleshooting

Session Won't Start

Error: Maximum concurrent sessions (5) reached

Solution:

# List active sessions
./.claude/commands/claude-code-x.sh sessions

# Kill inactive sessions or wait for completion
./.claude/commands/claude-code-x.sh kill <session-id>

# Or cleanup old sessions
./.claude/commands/claude-code-x.sh cleanup

Session Timeout

Error: Session times out before completion

Solution:

# Increase timeout for complex tasks
./.claude/commands/claude-code-x.sh exec "Complex task" --timeout 1200

Session Fails

Check logs:

./.claude/commands/claude-code-x.sh result <session-id>

Common issues:

  • Missing files → Add file creation to task description
  • Dependency errors → Ensure dependencies are available
  • Unclear task → Make task description more specific

📊 Success Metrics

Track these metrics to evaluate Claude Code X effectiveness:

  • Time Savings: Compare total execution time vs sequential
  • Success Rate: Percentage of sessions completing successfully
  • Parallelization Factor: Average concurrent sessions used
  • Task Clarity: Percentage requiring clarification before execution

Target Metrics:

  • Time Savings: >25%
  • Success Rate: >90%
  • Parallelization: 3-5 concurrent sessions
  • Task Clarity: <10% requiring clarification

Version: 1.0.0 Created: 2025-10-27 Author: Claude Code (Sonnet 4.5) Status: ✅ Production Ready

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

26.51%
按下载量换算796

windsurf

21.67%
按下载量换算650

trae

17.24%
按下载量换算517

OpenCode

13.26%
按下载量换算398

Codex

7.93%
按下载量换算238

Antigravity

2.98%
按下载量换算89

安全审计

暂无安全审计结果可展示。

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源字段存在多来源差异,先按来源优先级自动处理,无法消解时进入异常复核队列。

来源信息

继续浏览同类 Skills