[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FFARX0V2WY034NRY2BKZVZ":3,"skill-same:01M7FFARX0V2WY034NRY2BKZVZ":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M7FFARX0V2WY034NRY2BKZVZ","marshal",null,"Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmarshal\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: marshal\nlicense: MIT\ndescription: >-\n  Meta-orchestrator that takes any direction — broad, specific, or vague — and\n  autonomously chains skills and context into actionable work. Gathers context\n  from codebase, docs, and memory. Only asks the user when it genuinely cannot\n  proceed. Single-session orchestrator.\nuser-invocable: true\nauto-trigger: false\ntrigger_keywords:\n  - orchestrate\n  - chain skills\n  - multi-step\nlast-updated: 2026-03-20\n---\n\n# \u002Fmarshal — Session Commander\n\n## Orientation\n\nUse Marshal when the task is:\n- Multi-step but bounded (completable in one session)\n- Needs investigation before action\n- Spans multiple skills but doesn't need campaign persistence\n- Too complex for a single skill but doesn't need Archon\u002FFleet\n\n**Don't use when:** the task spans multiple sessions (use \u002Farchon); work decomposes into 3+ parallel streams (use \u002Ffleet); you only need research with no action (use \u002Fresearch).\n- Parallel execution (use Fleet)\n\n## Commands\n\n| Command | Behavior |\n|---|---|\n| `\u002Fmarshal [direction]` | Full loop: understand → plan → execute → report |\n| `\u002Fmarshal assess [area]` | Read-only: understand the area, produce findings, don't fix |\n\n## Protocol\n\n### Phase 1: UNDERSTAND\n\nParse the user's direction into structured intent:\n\n1. Read CLAUDE.md to understand the project's architecture and conventions\n2. Identify: scope (which files\u002Fdirectories), perspective (user, developer, admin),\n   mode (audit, fix, build, improve, map), depth (surface scan vs deep investigation)\n3. If the direction is ambiguous, make a reasonable interpretation and state it.\n   Do NOT ask clarifying questions unless genuinely stuck.\n\n### Phase 2: PLAN CHAIN\n\nMap the intent to a sequence of actions:\n\n| Direction Pattern | Chain |\n|---|---|\n| \"audit [area]\" | explore → analyze → report findings |\n| \"fix [thing]\" | investigate root cause → fix → verify → report |\n| \"map [area]\" | read files in parallel → synthesize → produce analysis |\n| \"improve [area]\" | audit current state → identify gaps → implement → verify |\n| \"what should [X] be\" | research → analyze options → recommend with reasoning |\n| \"research [topic]\" | search codebase + web → synthesize → report |\n\nAnnounce the chain before executing: \"I'll [step 1], then [step 2], then [step 3].\"\n\n### Phase 3: EXECUTE\n\nFor each step in the chain:\n\n1. Load the relevant skill if one exists (e.g., `\u002Freview` for audit steps)\n2. Gather context: read relevant files, check git history, search for patterns\n3. Perform the action\n4. Check the result against the plan — did it produce what was expected?\n5. If a step fails, try one alternative approach before escalating\n\n### Phase 4: REPORT\n\nProduce a structured report:\n\n```\n=== Marshal Report ===\n\nDirection: {original direction}\nScope: {what was examined}\n\nFindings:\n- {finding 1 with file:line reference}\n- {finding 2}\n\nActions Taken:\n- {what was changed, if anything}\n\nRecommendations:\n- {next steps if applicable}\n```\n\n### Phase 5: LEARN\n\nIf the investigation revealed reusable patterns or pitfalls:\n- Note them in the report\n- Suggest creating a skill if a pattern will recur: \"This pattern would\n  make a good skill. Run `\u002Fcreate-skill` to capture it.\"\n\n## Agent Timeouts\n\nWhen Marshal spawns sub-agents (e.g., for parallel investigation or delegated\nskill execution), it must enforce execution time limits. Sub-agents can hang\nindefinitely on tool calls — the circuit breaker catches failures, not hangs.\n\n### Default Timeouts\n\n| Agent Type | Default Timeout |\n|---|---|\n| Skill-level agents | 10 minutes |\n| Research agents | 15 minutes |\n\nTimeouts are configurable in `harness.json` under `agentTimeouts` (same config\nFleet uses). If an agent exceeds its timeout:\n\n1. Log the timeout in telemetry\n2. Check for partial output — extract usable findings if any\n3. Try one alternative approach (simpler prompt, reduced scope)\n4. If retry also times out, skip and note the gap in the report\n\nNever wait indefinitely. A timed-out agent's scope becomes a \"gap\" in the\nMarshal Report's Findings section.\n\n## Fringe Cases\n\n- **Direction is vague** (e.g., \"do the thing\", \"fix it\", \"make it better\"): Ask one clarifying question before proceeding. Do not attempt to guess scope on truly ambiguous input — one focused question is cheaper than executing the wrong plan.\n- **A sub-task fails on first attempt**: Retry once with a different approach (narrower scope, different tool, simpler method). If the second attempt also fails, record the blocker in the report and move on.\n- **No relevant files found for the stated scope**: Report the empty result honestly. Do not fabricate findings. Suggest the user verify the scope or file paths.\n- **CLAUDE.md missing**: Proceed without it. Note the absence in the report so the user knows project conventions weren't applied.\n- **Typecheck not configured**: Skip the verification step and note it as \"unverified\" in the report rather than blocking completion.\n\n## Quality Gates\n\n- Every finding must cite a specific file and line number\n- Every action must be verified (typecheck passes, tests pass)\n- If a fix was applied, confirm the original issue is resolved\n- The report must be concise — no filler, no repetition\n- If you're stuck on a step for more than 3 attempts, skip it and report the blocker\n\n## Exit Protocol\n\n1. Output the Marshal Report (format above)\n2. If work items were discovered but not addressed, suggest creating intake items\n3. Output a HANDOFF block summarizing what was done\n\n```\n---HANDOFF---\n- What: {behavior changed or goal achieved — not the file name, the outcome}\n- Decisions: {key tradeoffs made — include the alternative that was rejected}\n- Unresolved: {what is still open or blocked — actionable next step}\n- Reversibility: {green | amber | red} — {how to undo}\n---\n```\n","# \u002Fmarshal — Session Commander\n\n## Orientation\n\nUse Marshal when the task is:\n- Multi-step but bounded (completable in one session)\n- Needs investigation before action\n- Spans multiple skills but doesn't need campaign persistence\n- Too complex for a single skill but doesn't need Archon\u002FFleet\n\n**Don't use when:** the task spans multiple sessions (use \u002Farchon); work decomposes into 3+ parallel streams (use \u002Ffleet); you only need research with no action (use \u002Fresearch).\n- Parallel execution (use Fleet)\n\n## Commands\n\n| Command | Behavior |\n|---|---|\n| `\u002Fmarshal [direction]` | Full loop: understand → plan → execute → report |\n| `\u002Fmarshal assess [area]` | Read-only: understand the area, produce findings, don't fix |\n\n## Protocol\n\n### Phase 1: UNDERSTAND\n\nParse the user's direction into structured intent:\n\n1. Read CLAUDE.md to understand the project's architecture and conventions\n2. Identify: scope (which files\u002Fdirectories), perspective (user, developer, admin),\n   mode (audit, fix, build, improve, map), depth (surface scan vs deep investigation)\n3. If the direction is ambiguous, make a reasonable interpretation and state it.\n   Do NOT ask clarifying questions unless genuinely stuck.\n\n### Phase 2: PLAN CHAIN\n\nMap the intent to a sequence of actions:\n\n| Direction Pattern | Chain |\n|---|---|\n| \"audit [area]\" | explore → analyze → report findings |\n| \"fix [thing]\" | investigate root cause → fix → verify → report |\n| \"map [area]\" | read files in parallel → synthesize → produce analysis |\n| \"improve [area]\" | audit current state → identify gaps → implement → verify |\n| \"what should [X] be\" | research → analyze options → recommend with reasoning |\n| \"research [topic]\" | search codebase + web → synthesize → report |\n\nAnnounce the chain before executing: \"I'll [step 1], then [step 2], then [step 3].\"\n\n### Phase 3: EXECUTE\n\nFor each step in the chain:\n\n1. Load the relevant skill if one exists (e.g., `\u002Freview` for audit steps)\n2. Gather context: read relevant files, check git history, search for patterns\n3. Perform the action\n4. Check the result against the plan — did it produce what was expected?\n5. If a step fails, try one alternative approach before escalating\n\n### Phase 4: REPORT\n\nProduce a structured report:\n\n```\n=== Marshal Report ===\n\nDirection: {original direction}\nScope: {what was examined}\n\nFindings:\n- {finding 1 with file:line reference}\n- {finding 2}\n\nActions Taken:\n- {what was changed, if anything}\n\nRecommendations:\n- {next steps if applicable}\n```\n\n### Phase 5: LEARN\n\nIf the investigation revealed reusable patterns or pitfalls:\n- Note them in the report\n- Suggest creating a skill if a pattern will recur: \"This pattern would\n  make a good skill. Run `\u002Fcreate-skill` to capture it.\"\n\n## Agent Timeouts\n\nWhen Marshal spawns sub-agents (e.g., for parallel investigation or delegated\nskill execution), it must enforce execution time limits. Sub-agents can hang\nindefinitely on tool calls — the circuit breaker catches failures, not hangs.\n\n### Default Timeouts\n\n| Agent Type | Default Timeout |\n|---|---|\n| Skill-level agents | 10 minutes |\n| Research agents | 15 minutes |\n\nTimeouts are configurable in `harness.json` under `agentTimeouts` (same config\nFleet uses). If an agent exceeds its timeout:\n\n1. Log the timeout in telemetry\n2. Check for partial output — extract usable findings if any\n3. Try one alternative approach (simpler prompt, reduced scope)\n4. If retry also times out, skip and note the gap in the report\n\nNever wait indefinitely. A timed-out agent's scope becomes a \"gap\" in the\nMarshal Report's Findings section.\n\n## Fringe Cases\n\n- **Direction is vague** (e.g., \"do the thing\", \"fix it\", \"make it better\"): Ask one clarifying question before proceeding. Do not attempt to guess scope on truly ambiguous input — one focused question is cheaper than executing the wrong plan.\n- **A sub-task fails on first attempt**: Retry once with a different approach (narrower scope, different tool, simpler method). If the second attempt also fails, record the blocker in the report and move on.\n- **No relevant files found for the stated scope**: Report the empty result honestly. Do not fabricate findings. Suggest the user verify the scope or file paths.\n- **CLAUDE.md missing**: Proceed without it. Note the absence in the report so the user knows project conventions weren't applied.\n- **Typecheck not configured**: Skip the verification step and note it as \"unverified\" in the report rather than blocking completion.\n\n## Quality Gates\n\n- Every finding must cite a specific file and line number\n- Every action must be verified (typecheck passes, tests pass)\n- If a fix was applied, confirm the original issue is resolved\n- The report must be concise — no filler, no repetition\n- If you're stuck on a step for more than 3 attempts, skip it and report the blocker\n\n## Exit Protocol\n\n1. Output the Marshal Report (format above)\n2. If work items were discovered but not addressed, suggest creating intake items\n3. Output a HANDOFF block summarizing what was done\n\n```\n---HANDOFF---\n- What: {behavior changed or goal achieved — not the file name, the outcome}\n- Decisions: {key tradeoffs made — include the alternative that was rejected}\n- Unresolved: {what is still open or blocked — actionable next step}\n- Reversibility: {green | amber | red} — {how to undo}\n---\n```\n",{"name":5,"license":15,"description":7,"auto-trigger":20,"last-updated":24,"user-invocable":25,"trigger_keywords":26},1773964800000,true,[27,28,29],"orchestrate","chain skills","multi-step","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fmarshal",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":25},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill marshal",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill marshal",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill marshal","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmarshal\u002FSKILL.md",[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"__benchmarks__\u002Faudit-and-report.md","REFERENCE","参考文档",999,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmarshal\u002F__benchmarks__\u002Faudit-and-report.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"__benchmarks__\u002Fvague-direction.md",948,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmarshal\u002F__benchmarks__\u002Fvague-direction.md",[62,69,74,81,88,95],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":70,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]