[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAD7BV0WC24YSPTPY307FT":3,"skill-same:01M6CAD7BV0WC24YSPTPY307FT":74},{"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":28,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6CAD7BV0WC24YSPTPY307FT","flow-guided-implementation",null,"Orchestrate autonomous issue-to-code implementation using existing tools and agents with bounded iteration","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-guided-implementation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41],"flow","flow guided implementation","implementation","code","code implementation","orchestrate","Tools","autonomous","issue","iteration","with","Existing","bounded","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-guided-implementation\nplatforms: [all]\ndescription: Orchestrate autonomous issue-to-code implementation using existing tools and agents with bounded iteration\n---\n\n> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-guided-implementation.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# \u002Fflow-guided-implementation\n\nOrchestrate autonomous issue-to-code implementation using existing tools and agents with bounded iteration.\n\n## Usage\n\n```\n\u002Fflow-guided-implementation [issue-description]\n\u002Fflow-guided-implementation --issue \u003Curl>\n\u002Fflow-guided-implementation --max-retries 5\n```\n\n## Parameters\n\n| Parameter | Default | Description |\n|-----------|---------|-------------|\n| `[issue-description]` | - | Natural language description of what to implement |\n| `--issue \u003Curl>` | - | GitHub\u002FGitea issue URL to fetch |\n| `--max-retries` | 3 | Maximum iterations per task before escalating |\n| `--skip-review` | false | Skip code review (faster, less safe) |\n| `--dry-run` | false | Plan only, don't execute changes |\n\n## Design Principles\n\nFrom issue requirements:\n1. **Run to completion** - Minimal user interaction during execution\n2. **Complement existing tools** - Use Grep, Glob, Edit, TodoWrite, Task\n3. **Bounded iteration** - Auto-retry up to N times, then escalate\n4. **Autonomous decision-making** - Don't ask unless truly blocked\n\n## Workflow\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 1: ANALYSIS                                               │\n│ Tools: Read, Grep, Glob                                         │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Parse issue\u002Frequirement                                      │\n│ 2. Extract keywords and intent                                  │\n│ 3. Search codebase for relevant files:                          │\n│    - Grep for keywords in file contents                         │\n│    - Glob for naming patterns                                   │\n│ 4. Read top candidate files for context                         │\n│ 5. Rank files by relevance (keyword density + path match)       │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 2: TASK DECOMPOSITION                                     │\n│ Tool: TodoWrite                                                 │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Create task per file to modify                               │\n│ 2. Include task dependencies (e.g., types before implementation)│\n│ 3. Order by dependency graph                                    │\n│ 4. Estimate complexity per task                                 │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 3: ITERATIVE CODING                                       │\n│ Tools: Edit, Bash, Task(agents)                                 │\n│ Skill: iteration-control                                        │\n├─────────────────────────────────────────────────────────────────┤\n│ FOR EACH task (respecting dependencies):                        │\n│   iteration = 0                                                 │\n│                                                                 │\n│   LOOP while iteration \u003C max_retries:                           │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 1: LOCATE                                          │ │\n│     │ - Grep for specific patterns in target file             │ │\n│     │ - Read surrounding context                              │ │\n│     │ - Identify line ranges for modification                 │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 2: GENERATE                                        │ │\n│     │ Simple change: Edit tool directly                       │ │\n│     │ Complex change: Task(software-implementer)              │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 3: VALIDATE                                        │ │\n│     │ - Bash: Run tests (npm test, pytest, etc.)              │ │\n│     │ - If tests fail: Task(debugger) for diagnosis           │ │\n│     │ - If tests pass && !skip_review: Task(code-reviewer)    │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 4: DECIDE (iteration-control skill)                │ │\n│     │                                                         │ │\n│     │ IF pass + approved: mark task complete, BREAK           │ │\n│     │ IF fail + iteration \u003C max: retry with feedback          │ │\n│     │ IF fail + iteration >= max: ESCALATE to user            │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                                                                 │\n│   Mark task complete in TodoWrite                               │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 4: INTEGRATION                                            │\n│ Tools: Bash (git)                                               │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Verify all tasks complete                                    │\n│ 2. Run full test suite                                          │\n│ 3. Stage changes: git add                                       │\n│ 4. Generate commit message from tasks                           │\n│ 5. Commit (or prompt user for \u002Fcommit-and-push)                 │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## Agents Used\n\n| Agent | When | Purpose |\n|-------|------|---------|\n| `software-implementer` | Complex code generation | TDD cycle, multi-file changes |\n| `code-reviewer` | After code passes tests | Quality, security, style review |\n| `debugger` | When tests fail | Root cause analysis |\n| `test-engineer` | If tests need creation | Generate test coverage |\n\n## Example Session\n\n```\nUser: \u002Fflow-guided-implementation Add refresh token support to authentication\n\nClaude: Starting guided implementation...\n\n## Phase 1: Analysis\nSearching for authentication-related files...\n- Found: src\u002Fauth\u002FauthService.ts (high relevance)\n- Found: src\u002Fauth\u002FtokenService.ts (high relevance)\n- Found: src\u002Ftypes\u002Fauth.ts (medium relevance)\n- Found: src\u002Froutes\u002Fauth.ts (medium relevance)\n\n## Phase 2: Task Decomposition\nCreating tasks:\n[1\u002F4] [ ] Add RefreshToken type to src\u002Ftypes\u002Fauth.ts\n[2\u002F4] [ ] Add refresh config to src\u002Fconfig\u002Fauth.ts\n[3\u002F4] [ ] Implement refresh in src\u002Fauth\u002FtokenService.ts (depends: 1,2)\n[4\u002F4] [ ] Add \u002Frefresh endpoint to src\u002Froutes\u002Fauth.ts (depends: 3)\n\n## Phase 3: Iterative Coding\n\n### Task 1: Add RefreshToken type\nLocating insertion point... line 15\nGenerating type definition...\nRunning tests... PASS\n[1\u002F4] [✓] Add RefreshToken type\n\n### Task 2: Add refresh config\nLocating config section... line 8\nAdding refreshTokenExpiry config...\nRunning tests... PASS\n[2\u002F4] [✓] Add refresh config\n\n### Task 3: Implement refresh in tokenService\nLocating token generation... lines 20-35\nGenerating refresh token logic...\nRunning tests... FAIL\n  - refreshToken is undefined\nIteration 1\u002F3: Retrying with feedback...\n  Fixed: Added refreshToken to return object\nRunning tests... PASS\nCode review... APPROVED\n[3\u002F4] [✓] Implement refresh in tokenService\n\n### Task 4: Add \u002Frefresh endpoint\nLocating routes... line 45\nAdding POST \u002Frefresh handler...\nRunning tests... PASS\nCode review... APPROVED\n[4\u002F4] [✓] Add \u002Frefresh endpoint\n\n## Phase 4: Integration\nAll tasks complete. Running full test suite... PASS\nChanges ready to commit.\n\nGenerated commit message:\n  feat(auth): add refresh token support\n\n  - Add RefreshToken type\n  - Configure refresh token expiry\n  - Implement token refresh in tokenService\n  - Add POST \u002Frefresh endpoint\n\nRun \u002Fcommit-and-push to commit, or review changes with `git diff`.\n```\n\n## Escalation Example\n\n```\n### Task 3: Implement refresh (iteration 3\u002F3)\nRunning tests... FAIL\n  - userId format mismatch\n\nESCALATION: Max iterations reached\n\nAfter 3 attempts, the test still fails:\n- Iter 1: refreshToken undefined\n- Iter 2: refreshToken missing userId\n- Iter 3: userId format mismatch (string vs number)\n\nThe implementation uses: { userId: \"123\" } (string)\nThe test expects: { userId: 123 } (number)\n\nWhich format should be used?\n1. String - I'll update the test\n2. Number - I'll update the implementation\n```\n\n## Progress Tracking\n\nProgress tracked via TodoWrite. Check status anytime:\n\n```\nUser: What's the implementation status?\n\nClaude:\n[1\u002F4] [✓] Add RefreshToken type (1 iteration)\n[2\u002F4] [✓] Add refresh config (1 iteration)\n[3\u002F4] [..] Implement refresh in tokenService (iteration 2\u002F3)\n[4\u002F4] [ ] Add \u002Frefresh endpoint (pending)\n\nCurrent: Task 3, waiting for test fix\n```\n\n## Traceability\n\n- @research @.aiwg\u002Fresearch\u002FREF-004-magis-multi-agent-issue-resolution.md\n- @skill @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fguided-implementation\u002Fskills\u002Fiteration-control\u002FSKILL.md\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fsoftware-implementer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fcode-reviewer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fdebugger.md\n","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-guided-implementation.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# \u002Fflow-guided-implementation\n\nOrchestrate autonomous issue-to-code implementation using existing tools and agents with bounded iteration.\n\n## Usage\n\n```\n\u002Fflow-guided-implementation [issue-description]\n\u002Fflow-guided-implementation --issue \u003Curl>\n\u002Fflow-guided-implementation --max-retries 5\n```\n\n## Parameters\n\n| Parameter | Default | Description |\n|-----------|---------|-------------|\n| `[issue-description]` | - | Natural language description of what to implement |\n| `--issue \u003Curl>` | - | GitHub\u002FGitea issue URL to fetch |\n| `--max-retries` | 3 | Maximum iterations per task before escalating |\n| `--skip-review` | false | Skip code review (faster, less safe) |\n| `--dry-run` | false | Plan only, don't execute changes |\n\n## Design Principles\n\nFrom issue requirements:\n1. **Run to completion** - Minimal user interaction during execution\n2. **Complement existing tools** - Use Grep, Glob, Edit, TodoWrite, Task\n3. **Bounded iteration** - Auto-retry up to N times, then escalate\n4. **Autonomous decision-making** - Don't ask unless truly blocked\n\n## Workflow\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 1: ANALYSIS                                               │\n│ Tools: Read, Grep, Glob                                         │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Parse issue\u002Frequirement                                      │\n│ 2. Extract keywords and intent                                  │\n│ 3. Search codebase for relevant files:                          │\n│    - Grep for keywords in file contents                         │\n│    - Glob for naming patterns                                   │\n│ 4. Read top candidate files for context                         │\n│ 5. Rank files by relevance (keyword density + path match)       │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 2: TASK DECOMPOSITION                                     │\n│ Tool: TodoWrite                                                 │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Create task per file to modify                               │\n│ 2. Include task dependencies (e.g., types before implementation)│\n│ 3. Order by dependency graph                                    │\n│ 4. Estimate complexity per task                                 │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 3: ITERATIVE CODING                                       │\n│ Tools: Edit, Bash, Task(agents)                                 │\n│ Skill: iteration-control                                        │\n├─────────────────────────────────────────────────────────────────┤\n│ FOR EACH task (respecting dependencies):                        │\n│   iteration = 0                                                 │\n│                                                                 │\n│   LOOP while iteration \u003C max_retries:                           │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 1: LOCATE                                          │ │\n│     │ - Grep for specific patterns in target file             │ │\n│     │ - Read surrounding context                              │ │\n│     │ - Identify line ranges for modification                 │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 2: GENERATE                                        │ │\n│     │ Simple change: Edit tool directly                       │ │\n│     │ Complex change: Task(software-implementer)              │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 3: VALIDATE                                        │ │\n│     │ - Bash: Run tests (npm test, pytest, etc.)              │ │\n│     │ - If tests fail: Task(debugger) for diagnosis           │ │\n│     │ - If tests pass && !skip_review: Task(code-reviewer)    │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                         │                                       │\n│                         v                                       │\n│     ┌─────────────────────────────────────────────────────────┐ │\n│     │ STEP 4: DECIDE (iteration-control skill)                │ │\n│     │                                                         │ │\n│     │ IF pass + approved: mark task complete, BREAK           │ │\n│     │ IF fail + iteration \u003C max: retry with feedback          │ │\n│     │ IF fail + iteration >= max: ESCALATE to user            │ │\n│     └─────────────────────────────────────────────────────────┘ │\n│                                                                 │\n│   Mark task complete in TodoWrite                               │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              v\n┌─────────────────────────────────────────────────────────────────┐\n│ PHASE 4: INTEGRATION                                            │\n│ Tools: Bash (git)                                               │\n├─────────────────────────────────────────────────────────────────┤\n│ 1. Verify all tasks complete                                    │\n│ 2. Run full test suite                                          │\n│ 3. Stage changes: git add                                       │\n│ 4. Generate commit message from tasks                           │\n│ 5. Commit (or prompt user for \u002Fcommit-and-push)                 │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## Agents Used\n\n| Agent | When | Purpose |\n|-------|------|---------|\n| `software-implementer` | Complex code generation | TDD cycle, multi-file changes |\n| `code-reviewer` | After code passes tests | Quality, security, style review |\n| `debugger` | When tests fail | Root cause analysis |\n| `test-engineer` | If tests need creation | Generate test coverage |\n\n## Example Session\n\n```\nUser: \u002Fflow-guided-implementation Add refresh token support to authentication\n\nClaude: Starting guided implementation...\n\n## Phase 1: Analysis\nSearching for authentication-related files...\n- Found: src\u002Fauth\u002FauthService.ts (high relevance)\n- Found: src\u002Fauth\u002FtokenService.ts (high relevance)\n- Found: src\u002Ftypes\u002Fauth.ts (medium relevance)\n- Found: src\u002Froutes\u002Fauth.ts (medium relevance)\n\n## Phase 2: Task Decomposition\nCreating tasks:\n[1\u002F4] [ ] Add RefreshToken type to src\u002Ftypes\u002Fauth.ts\n[2\u002F4] [ ] Add refresh config to src\u002Fconfig\u002Fauth.ts\n[3\u002F4] [ ] Implement refresh in src\u002Fauth\u002FtokenService.ts (depends: 1,2)\n[4\u002F4] [ ] Add \u002Frefresh endpoint to src\u002Froutes\u002Fauth.ts (depends: 3)\n\n## Phase 3: Iterative Coding\n\n### Task 1: Add RefreshToken type\nLocating insertion point... line 15\nGenerating type definition...\nRunning tests... PASS\n[1\u002F4] [✓] Add RefreshToken type\n\n### Task 2: Add refresh config\nLocating config section... line 8\nAdding refreshTokenExpiry config...\nRunning tests... PASS\n[2\u002F4] [✓] Add refresh config\n\n### Task 3: Implement refresh in tokenService\nLocating token generation... lines 20-35\nGenerating refresh token logic...\nRunning tests... FAIL\n  - refreshToken is undefined\nIteration 1\u002F3: Retrying with feedback...\n  Fixed: Added refreshToken to return object\nRunning tests... PASS\nCode review... APPROVED\n[3\u002F4] [✓] Implement refresh in tokenService\n\n### Task 4: Add \u002Frefresh endpoint\nLocating routes... line 45\nAdding POST \u002Frefresh handler...\nRunning tests... PASS\nCode review... APPROVED\n[4\u002F4] [✓] Add \u002Frefresh endpoint\n\n## Phase 4: Integration\nAll tasks complete. Running full test suite... PASS\nChanges ready to commit.\n\nGenerated commit message:\n  feat(auth): add refresh token support\n\n  - Add RefreshToken type\n  - Configure refresh token expiry\n  - Implement token refresh in tokenService\n  - Add POST \u002Frefresh endpoint\n\nRun \u002Fcommit-and-push to commit, or review changes with `git diff`.\n```\n\n## Escalation Example\n\n```\n### Task 3: Implement refresh (iteration 3\u002F3)\nRunning tests... FAIL\n  - userId format mismatch\n\nESCALATION: Max iterations reached\n\nAfter 3 attempts, the test still fails:\n- Iter 1: refreshToken undefined\n- Iter 2: refreshToken missing userId\n- Iter 3: userId format mismatch (string vs number)\n\nThe implementation uses: { userId: \"123\" } (string)\nThe test expects: { userId: 123 } (number)\n\nWhich format should be used?\n1. String - I'll update the test\n2. Number - I'll update the implementation\n```\n\n## Progress Tracking\n\nProgress tracked via TodoWrite. Check status anytime:\n\n```\nUser: What's the implementation status?\n\nClaude:\n[1\u002F4] [✓] Add RefreshToken type (1 iteration)\n[2\u002F4] [✓] Add refresh config (1 iteration)\n[3\u002F4] [..] Implement refresh in tokenService (iteration 2\u002F3)\n[4\u002F4] [ ] Add \u002Frefresh endpoint (pending)\n\nCurrent: Task 3, waiting for test fix\n```\n\n## Traceability\n\n- @research @.aiwg\u002Fresearch\u002FREF-004-magis-multi-agent-issue-resolution.md\n- @skill @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fguided-implementation\u002Fskills\u002Fiteration-control\u002FSKILL.md\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fsoftware-implementer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fcode-reviewer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fdebugger.md\n",{"name":5,"namespace":47,"platforms":48,"description":7},"aiwg",[49],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-guided-implementation",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 00:33:10",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add jmagly\u002Faiwg --skill flow-guided-implementation",{"tool":66,"command":67},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-guided-implementation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-guided-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-guided-implementation\u002FSKILL.md",true,[],[75,103,127,133,140,154],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":82,"publishedAt":42},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[81],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":113,"publishedAt":42},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116,86,117,91,118,119,93,120,83,121,95,122,123,98,99,124,125,126],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":128,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":42},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[131],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[85,83,84,94,86,102,89,88,97,90,91,92,93,101,95,96,87,98,99,100],{"skillNo":134,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":139,"publishedAt":42},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[137,138],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[115,114,98,117,91,118,93,116,83,121,95,122,123,86,99,120,119,124,125,126],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":42},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,150,151,152,153],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":42},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[160],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[162,163,122,164,149],"pi","pi local","duplicate"]