firefrost-gaming/claude-skills-reference

Files

Reza Rezvani 2f57ef8948 feat(agenthub): add AgentHub plugin with cross-domain examples, SEO optimization, and docs site fixes

- AgentHub: 13 files updated with non-engineering examples (content drafts,
  research, strategy) — engineering stays primary, cross-domain secondary
- AgentHub: 7 slash commands, 5 Python scripts, 3 references, 1 agent,
  dry_run.py validation (57 checks)
- Marketplace: agenthub entry added with cross-domain keywords, engineering
  POWERFUL updated (25→30), product (12→13), counts synced across all configs
- SEO: generate-docs.py now produces keyword-rich <title> tags and meta
  descriptions using SKILL.md frontmatter — "Claude Code Skills" in site_name
  propagates to all 276 HTML pages
- SEO: per-domain title suffixes (Agent Skill for Codex & OpenClaw, etc.),
  slug-as-title cleanup, domain label stripping from titles
- Broken links: 141→0 warnings — new rewrite_skill_internal_links() converts
  references/, scripts/, assets/ links to GitHub source URLs; skills/index.md
  phantom slugs fixed (6 marketing, 7 RA/QM)
- Counts synced: 204 skills, 266 tools, 382 refs, 16 agents, 17 commands,
  21 plugins — consistent across CLAUDE.md, README.md, docs/index.md,
  marketplace.json, getting-started.md, mkdocs.yml
- Platform sync: Codex 163 skills, Gemini 246 items, OpenClaw compatible

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-17 12:10:46 +01:00

3.8 KiB

Raw Blame History

title, description

title	description
/hub:spawn — Launch Parallel Agents — Agent Skill for Codex & OpenClaw	Launch N parallel subagents in isolated git worktrees to compete on the session task. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw.

/hub:spawn — Launch Parallel Agents

:material-rocket-launch: Engineering - POWERFUL :material-identifier: `spawn` :material-github: Source

Install: claude /plugin install engineering-advanced-skills

Spawn N subagents that work on the same task in parallel, each in an isolated git worktree.

Usage

/hub:spawn                                    # Spawn agents for the latest session
/hub:spawn 20260317-143022                    # Spawn agents for a specific session
/hub:spawn --template optimizer               # Use optimizer template for dispatch prompts
/hub:spawn --template refactorer              # Use refactorer template

Templates

When --template <name> is provided, use the dispatch prompt from references/agent-templates.md instead of the default prompt below. Available templates:

Template	Pattern	Use Case
`optimizer`	Edit → eval → keep/discard → repeat x10	Performance, latency, size reduction
`refactorer`	Restructure → test → iterate until green	Code quality, tech debt
`test-writer`	Write tests → measure coverage → repeat	Test coverage gaps
`bug-fixer`	Reproduce → diagnose → fix → verify	Bug fix with competing approaches

When using a template, replace all {variables} with values from the session config. Assign each agent a different strategy appropriate to the template and task — diverse strategies maximize the value of parallel exploration.

What It Does

Load session config from .agenthub/sessions/{session-id}/config.yaml
For each agent 1..N:
- Write task assignment to .agenthub/board/dispatch/
- Build agent prompt with task, constraints, and board write instructions
Launch ALL agents in a single message with multiple Agent tool calls:

Agent(
  prompt: "You are agent-{i} in hub session {session-id}.

Your task: {task}

Read your full assignment at .agenthub/board/dispatch/{seq}-agent-{i}.md

Instructions:
1. Work in your worktree — make changes, run tests, iterate
2. Commit all changes with descriptive messages
3. Write your result summary to .agenthub/board/results/agent-{i}-result.md
   Include: approach taken, files changed, metric if available, confidence level
4. Exit when done

Constraints:
- Do NOT read or modify other agents' work
- Do NOT access .agenthub/board/results/ for other agents
- Commit early and often with descriptive messages
- If you hit a dead end, commit what you have and explain in your result",
  isolation: "worktree"
)

Update session state to running via:

python {skill_path}/scripts/session_manager.py --update {session-id} --state running

Critical Rules

All agents in ONE message — spawn all Agent tool calls simultaneously for true parallelism
isolation: "worktree" is mandatory — each agent needs its own filesystem
Never modify session config after spawn — agents rely on stable configuration
Each agent gets a unique board post — dispatch posts are numbered sequentially

After Spawn

Tell the user:

{N} agents launched in parallel
Each working in an isolated worktree
Monitor with /hub:status
Evaluate when done with /hub:eval

3.8 KiB Raw Blame History