[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F5FND45J89XDBPT8KPJKG":3,"skill-same:01M73F5FND45J89XDBPT8KPJKG":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73F5FND45J89XDBPT8KPJKG","plan-first",null,"Use before touching any code when user gives a task, spec, or feature request. Forces writing a plan before implementation. Examples: 'implement X', 'add feature Y', 'fix Z and also update A', any multi-step task that would touch 2+ files.","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\u002Fcore\u002Fskills\u002Fplan-first\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: plan-first\ndescription: \"Use before touching any code when user gives a task, spec, or feature request. Forces writing a plan before implementation. Examples: 'implement X', 'add feature Y', 'fix Z and also update A', any multi-step task that would touch 2+ files.\"\n---\n\n# Plan First Skill\n\nBefore writing code, write a plan. This exists to stop the pattern of AI jumping\nstraight into editing files without understanding what should and should not change.\n\n## When to use this skill\n\n- User describes a feature, task, or fix that touches 2+ files\n- Task has unclear scope — what NOT to change is as important as what to change\n- Agent is about to run a bash command that modifies files without a written plan\n- User says \"implement\", \"add\", \"refactor\", \"migrate\", \"update\"\n\nDo NOT use for: single-file typo fixes, running a specific command the user named,\nanswering a question.\n\n## Workflow\n\n### Step 1 — Write the plan (before any file edits)\n\nOutput a plan with this structure:\n\n```markdown\n## Plan: [task name]\n\n**Goal:** [one sentence — what this achieves when done]\n\n**Files to change:**\n- `path\u002Fto\u002Ffile.ts` — [why it changes]\n- `path\u002Fto\u002Fother.ts` — [why it changes]\n\n**Files NOT to touch:**\n- `app\u002F` — product code, out of YAMTAM scope\n- [any other explicit boundary]\n\n**Steps:**\n1. [concrete action]\n2. [concrete action]\n3. ...\n\n**Verify after:**\n- [command to run that proves it worked]\n- [expected output]\n\n**Risks:**\n- [anything that could go wrong or needs human decision]\n```\n\n### Step 2 — Wait for approval\n\nDo not proceed to code until the user confirms or modifies the plan.\nIf user says \"go\" or \"ok\" or \"looks good\" — proceed to Step 3.\nIf user modifies the plan — update it, confirm, then proceed.\n\n### Step 3 — Execute step by step\n\nWork through the plan steps in order.\nAfter each step: show what changed (`git diff --stat` or file path).\nDo not bundle multiple steps into one edit.\n\n### Step 4 — Verify\n\nRun the verify commands from the plan.\nShow actual output — do not summarise.\nOnly claim done after output confirms it.\n\n## Constraints\n\n- Never edit files before the plan is written and approved.\n- Never expand scope mid-task without writing a plan amendment.\n- If a step reveals unexpected complexity, stop and update the plan.\n- \"I'll plan as I go\" is not a plan.\n","# Plan First Skill\n\nBefore writing code, write a plan. This exists to stop the pattern of AI jumping\nstraight into editing files without understanding what should and should not change.\n\n## When to use this skill\n\n- User describes a feature, task, or fix that touches 2+ files\n- Task has unclear scope — what NOT to change is as important as what to change\n- Agent is about to run a bash command that modifies files without a written plan\n- User says \"implement\", \"add\", \"refactor\", \"migrate\", \"update\"\n\nDo NOT use for: single-file typo fixes, running a specific command the user named,\nanswering a question.\n\n## Workflow\n\n### Step 1 — Write the plan (before any file edits)\n\nOutput a plan with this structure:\n\n```markdown\n## Plan: [task name]\n\n**Goal:** [one sentence — what this achieves when done]\n\n**Files to change:**\n- `path\u002Fto\u002Ffile.ts` — [why it changes]\n- `path\u002Fto\u002Fother.ts` — [why it changes]\n\n**Files NOT to touch:**\n- `app\u002F` — product code, out of YAMTAM scope\n- [any other explicit boundary]\n\n**Steps:**\n1. [concrete action]\n2. [concrete action]\n3. ...\n\n**Verify after:**\n- [command to run that proves it worked]\n- [expected output]\n\n**Risks:**\n- [anything that could go wrong or needs human decision]\n```\n\n### Step 2 — Wait for approval\n\nDo not proceed to code until the user confirms or modifies the plan.\nIf user says \"go\" or \"ok\" or \"looks good\" — proceed to Step 3.\nIf user modifies the plan — update it, confirm, then proceed.\n\n### Step 3 — Execute step by step\n\nWork through the plan steps in order.\nAfter each step: show what changed (`git diff --stat` or file path).\nDo not bundle multiple steps into one edit.\n\n### Step 4 — Verify\n\nRun the verify commands from the plan.\nShow actual output — do not summarise.\nOnly claim done after output confirms it.\n\n## Constraints\n\n- Never edit files before the plan is written and approved.\n- Never expand scope mid-task without writing a plan amendment.\n- If a step reveals unexpected complexity, stop and update the plan.\n- \"I'll plan as I go\" is not a plan.\n",{"name":5,"description":7},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fplan-first",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-13 13:15:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill plan-first",{"tool":40,"command":41},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill plan-first",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill plan-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fplan-first\u002FSKILL.md",true,[],[49,57,64,72,80,88],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"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":91,"categories":92,"keywords":93,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]