[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730RAZY5HRSMKRGC1P88DFN":3,"skill-same:01M730RAZY5HRSMKRGC1P88DFN":52},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M730RAZY5HRSMKRGC1P88DFN","blue-team-fix",null,"Defensive response to red team security findings — analyze each vulnerability, propose a targeted fix, and add a test that covers the fix. Use when the user has a security finding list (from red-team-check or a manual audit) and wants to fix the vulnerabilities. Produces: root cause analysis, code fix, and test. Does not auto-apply fixes — proposes and waits for user approval per fix.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fblue-team-fix\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: blue-team-fix\ndescription: >\n  Defensive response to red team security findings — analyze each vulnerability,\n  propose a targeted fix, and add a test that covers the fix. Use when the user\n  has a security finding list (from red-team-check or a manual audit) and wants\n  to fix the vulnerabilities. Produces: root cause analysis, code fix, and test.\n  Does not auto-apply fixes — proposes and waits for user approval per fix.\norigin: yamtam\nversion: 1.0.0\ncompatibility: >\n  Expects input in red-team-check finding format. Works on local codebase.\n  Does not auto-commit. Does not auto-apply — proposes per fix.\n---\n\n\u003C!-- Concept inspired by Strix (Apache 2.0) — defensive security framing.\n     All content written original for YAMTAM. No code ported. -->\n\n## When to Use\n\n- After running red-team-check and receiving a finding list\n- When user shares a security audit report and wants fixes\n- When a CVE or bug report references specific vulnerabilities in the codebase\n- When a penetration test report needs to be remediated\n\nDo NOT use:\n- Without a finding list — always needs red-team-check output or equivalent as input\n- To auto-apply fixes without user review — propose only, never apply unilaterally\n\n## How It Works\n\n### Step 1 — Triage Finding List\n\nRead all findings from input. Prioritize by severity:\n```\nCRITICAL → fix first, block deploy if unresolved\nHIGH     → fix before next release\nMEDIUM   → fix in current sprint\nLOW      → track in backlog, fix opportunistically\nINFO     → no action required, document only\n```\n\nOutput a triage table before starting any fixes:\n```\n| # | Severity | Category | Title | Fix Priority |\n|---|----------|----------|-------|-------------|\n| 1 | CRITICAL | A02 | Hardcoded DB password | P0 — fix now |\n| 2 | HIGH     | A01 | IDOR on \u002Fapi\u002Fusers\u002F:id | P1 — before release |\n```\n\n### Step 2 — Per Finding: Root Cause → Fix → Test\n\nFor each finding (start with CRITICAL, work down):\n\n**Root Cause Analysis**\n```\nWhat pattern caused this?\n  - Missing input validation\n  - Hardcoded value that should be env var\n  - Missing auth check\n  - Unsafe library call\nWhy was it introduced?\n  - Copy-paste from example code\n  - Missing security requirement in spec\n  - Insufficient code review\n```\n\n**Proposed Fix**\n- Show the exact diff (before\u002Fafter)\n- Explain why the fix addresses the root cause\n- Reference the secure pattern to use going forward\n- Note any breaking changes\n\n**Test to Cover the Fix**\n- Write a test that would have caught this before it was introduced\n- The test must FAIL on the unfixed code and PASS after the fix\n- Test type: unit \u002F integration depending on the vulnerability\n\n**Present fix for approval before applying:**\n```\nFix #N ready for review:\n  File: path\u002Fto\u002Ffile.ext\n  Change: [diff shown]\n  Test: [test code shown]\n\nApply this fix? (yes \u002F skip \u002F modify)\n```\n\nDo not apply the fix until the user confirms. If user says \"yes to all\" for a batch,\napply in order, stop and re-confirm if any fix has unexpected side effects.\n\n### Step 3 — Verify Each Applied Fix\n\nAfter user approves and fix is applied:\n1. Show the actual diff in the file\n2. Confirm the test file exists and references the correct assertion\n3. Note if a full test run is needed (and prompt user to run it)\n\n### Step 4 — Output Fix Summary\n\nAfter all fixes are processed:\n```\n## Blue Team Fix Summary\n\n| # | Severity | Title | Status | Test Added |\n|---|----------|-------|--------|-----------|\n| 1 | CRITICAL | Hardcoded DB password | FIXED | yes — test\u002Fsecurity\u002Ftest_secrets.py |\n| 2 | HIGH     | IDOR on \u002Fapi\u002Fusers\u002F:id | FIXED | yes — test\u002Fapi\u002Ftest_users_auth.py |\n| 3 | MEDIUM   | Missing rate limit | SKIPPED by user | — |\n\nOpen items: 1 MEDIUM skipped — user to track in backlog.\nEvidence: diffs shown above, test files created at paths listed.\n```\n\n## Gotchas\n\n- Never apply a CRITICAL fix that touches auth or session handling without showing full diff first\n- If a fix introduces a breaking API change, flag it explicitly — user must decide\n- Fixes for A06 (vulnerable deps) require running package managers — ask before `npm install`\n- Do not suggest \"add a comment explaining why this is safe\" as a fix — it is not a fix\n\n## Anti-Fake-Pass Rules\n\nBefore claiming a finding is FIXED, you MUST show:\n- [ ] The actual code diff (before and after)\n- [ ] The test file path and key assertion\n- [ ] User approval confirmation noted in output\n\nMUST NOT say \"fixed\" if only proposed — use \"proposed, awaiting approval\".\nMUST NOT say \"all fixed\" if any finding was skipped — use \"N fixed, M skipped\".\nMUST NOT say \"tests pass\" without the user running them — use \"test written, not yet run\".\n","\u003C!-- Concept inspired by Strix (Apache 2.0) — defensive security framing.\n     All content written original for YAMTAM. No code ported. -->\n\n## When to Use\n\n- After running red-team-check and receiving a finding list\n- When user shares a security audit report and wants fixes\n- When a CVE or bug report references specific vulnerabilities in the codebase\n- When a penetration test report needs to be remediated\n\nDo NOT use:\n- Without a finding list — always needs red-team-check output or equivalent as input\n- To auto-apply fixes without user review — propose only, never apply unilaterally\n\n## How It Works\n\n### Step 1 — Triage Finding List\n\nRead all findings from input. Prioritize by severity:\n```\nCRITICAL → fix first, block deploy if unresolved\nHIGH     → fix before next release\nMEDIUM   → fix in current sprint\nLOW      → track in backlog, fix opportunistically\nINFO     → no action required, document only\n```\n\nOutput a triage table before starting any fixes:\n```\n| # | Severity | Category | Title | Fix Priority |\n|---|----------|----------|-------|-------------|\n| 1 | CRITICAL | A02 | Hardcoded DB password | P0 — fix now |\n| 2 | HIGH     | A01 | IDOR on \u002Fapi\u002Fusers\u002F:id | P1 — before release |\n```\n\n### Step 2 — Per Finding: Root Cause → Fix → Test\n\nFor each finding (start with CRITICAL, work down):\n\n**Root Cause Analysis**\n```\nWhat pattern caused this?\n  - Missing input validation\n  - Hardcoded value that should be env var\n  - Missing auth check\n  - Unsafe library call\nWhy was it introduced?\n  - Copy-paste from example code\n  - Missing security requirement in spec\n  - Insufficient code review\n```\n\n**Proposed Fix**\n- Show the exact diff (before\u002Fafter)\n- Explain why the fix addresses the root cause\n- Reference the secure pattern to use going forward\n- Note any breaking changes\n\n**Test to Cover the Fix**\n- Write a test that would have caught this before it was introduced\n- The test must FAIL on the unfixed code and PASS after the fix\n- Test type: unit \u002F integration depending on the vulnerability\n\n**Present fix for approval before applying:**\n```\nFix #N ready for review:\n  File: path\u002Fto\u002Ffile.ext\n  Change: [diff shown]\n  Test: [test code shown]\n\nApply this fix? (yes \u002F skip \u002F modify)\n```\n\nDo not apply the fix until the user confirms. If user says \"yes to all\" for a batch,\napply in order, stop and re-confirm if any fix has unexpected side effects.\n\n### Step 3 — Verify Each Applied Fix\n\nAfter user approves and fix is applied:\n1. Show the actual diff in the file\n2. Confirm the test file exists and references the correct assertion\n3. Note if a full test run is needed (and prompt user to run it)\n\n### Step 4 — Output Fix Summary\n\nAfter all fixes are processed:\n```\n## Blue Team Fix Summary\n\n| # | Severity | Title | Status | Test Added |\n|---|----------|-------|--------|-----------|\n| 1 | CRITICAL | Hardcoded DB password | FIXED | yes — test\u002Fsecurity\u002Ftest_secrets.py |\n| 2 | HIGH     | IDOR on \u002Fapi\u002Fusers\u002F:id | FIXED | yes — test\u002Fapi\u002Ftest_users_auth.py |\n| 3 | MEDIUM   | Missing rate limit | SKIPPED by user | — |\n\nOpen items: 1 MEDIUM skipped — user to track in backlog.\nEvidence: diffs shown above, test files created at paths listed.\n```\n\n## Gotchas\n\n- Never apply a CRITICAL fix that touches auth or session handling without showing full diff first\n- If a fix introduces a breaking API change, flag it explicitly — user must decide\n- Fixes for A06 (vulnerable deps) require running package managers — ask before `npm install`\n- Do not suggest \"add a comment explaining why this is safe\" as a fix — it is not a fix\n\n## Anti-Fake-Pass Rules\n\nBefore claiming a finding is FIXED, you MUST show:\n- [ ] The actual code diff (before and after)\n- [ ] The test file path and key assertion\n- [ ] User approval confirmation noted in output\n\nMUST NOT say \"fixed\" if only proposed — use \"proposed, awaiting approval\".\nMUST NOT say \"all fixed\" if any finding was skipped — use \"N fixed, M skipped\".\nMUST NOT say \"tests pass\" without the user running them — use \"test written, not yet run\".\n",{"name":5,"origin":24,"version":25,"description":26,"compatibility":27},"yamtam","1.0.0","Defensive response to red team security findings — analyze each vulnerability, propose a targeted fix, and add a test that covers the fix. Use when the user has a security finding list (from red-team-check or a manual audit) and wants to fix the vulnerabilities. Produces: root cause analysis, code fix, and test. Does not auto-apply fixes — proposes and waits for user approval per fix.\n","Expects input in red-team-check finding format. Works on local codebase. Does not auto-commit. Does not auto-apply — proposes per fix.","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fblue-team-fix",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill blue-team-fix",{"tool":44,"command":45},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill blue-team-fix",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill blue-team-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fblue-team-fix\u002FSKILL.md",true,[],[53,61,68,76,84,92],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]