[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73AVW08T0JD7RB95S64EKXE":3,"skill-same:01M73AVW08T0JD7RB95S64EKXE":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73AVW08T0JD7RB95S64EKXE","extract",null,"Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-self-improving-agent\u002Fskills\u002Fextract\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"extract\"\ndescription: \"Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.\"\n---\n\n# \u002Fsi:extract — Create Skills from Patterns\n\nTransforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.\n\n## Usage\n\n```\n\u002Fsi:extract \u003Cpattern description>                  # Interactive extraction\n\u002Fsi:extract \u003Cpattern> --name docker-m1-fixes       # Specify skill name\n\u002Fsi:extract \u003Cpattern> --output .\u002Fskills\u002F            # Custom output directory\n\u002Fsi:extract \u003Cpattern> --dry-run                     # Preview without creating files\n```\n\n## When to Extract\n\nA learning qualifies for skill extraction when ANY of these are true:\n\n| Criterion | Signal |\n|---|---|\n| **Recurring** | Same issue across 2+ projects |\n| **Non-obvious** | Required real debugging to discover |\n| **Broadly applicable** | Not tied to one specific codebase |\n| **Complex solution** | Multi-step fix that's easy to forget |\n| **User-flagged** | \"Save this as a skill\", \"I want to reuse this\" |\n\n## Workflow\n\n### Step 1: Identify the pattern\n\nRead the user's description. Search auto-memory for related entries:\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -rni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002F\"\n```\n\nIf found in auto-memory, use those entries as source material. If not, use the user's description directly.\n\n### Step 2: Determine skill scope\n\nAsk (max 2 questions):\n- \"What problem does this solve?\" (if not clear)\n- \"Should this include code examples?\" (if applicable)\n\n### Step 3: Generate skill name\n\nRules for naming:\n- Lowercase, hyphens between words\n- Descriptive but concise (2-4 words)\n- Examples: `docker-m1-fixes`, `api-timeout-patterns`, `pnpm-workspace-setup`\n\n### Step 4: Create the skill files\n\n**Spawn the `skill-extractor` agent** for the actual file generation.\n\nThe agent creates:\n\n```\n\u003Cskill-name>\u002F\n├── SKILL.md            # Main skill file with frontmatter\n├── README.md           # Human-readable overview\n└── reference\u002F          # (optional) Supporting documentation\n    └── examples.md     # Concrete examples and edge cases\n```\n\n### Step 5: SKILL.md structure\n\nThe generated SKILL.md must follow this format:\n\n```markdown\n---\nname: \"skill-name\"\ndescription: \"\u003Cone-line description>. Use when: \u003Ctrigger conditions>.\"\n---\n\n# \u003CSkill Title>\n\n> One-line summary of what this skill solves.\n\n## Quick Reference\n\n| Problem | Solution |\n|---------|----------|\n| {{problem 1}} | {{solution 1}} |\n| {{problem 2}} | {{solution 2}} |\n\n## The Problem\n\n{{2-3 sentences explaining what goes wrong and why it's non-obvious.}}\n\n## Solutions\n\n### Option 1: {{Name}} (Recommended)\n\n{{Step-by-step with code examples.}}\n\n### Option 2: {{Alternative}}\n\n{{For when Option 1 doesn't apply.}}\n\n## Trade-offs\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Option 1 | {{pros}} | {{cons}} |\n| Option 2 | {{pros}} | {{cons}} |\n\n## Edge Cases\n\n- {{edge case 1 and how to handle it}}\n- {{edge case 2 and how to handle it}}\n```\n\n### Step 6: Quality gates\n\nBefore finalizing, verify:\n\n- [ ] SKILL.md has valid YAML frontmatter with `name` and `description`\n- [ ] `name` matches the folder name (lowercase, hyphens)\n- [ ] Description includes \"Use when:\" trigger conditions\n- [ ] Solutions are self-contained (no external context needed)\n- [ ] Code examples are complete and copy-pasteable\n- [ ] No project-specific hardcoded values (paths, URLs, credentials)\n- [ ] No unnecessary dependencies\n\n### Step 7: Report\n\n```\n✅ Skill extracted: {{skill-name}}\n\nFiles created:\n  {{path}}\u002FSKILL.md          ({{lines}} lines)\n  {{path}}\u002FREADME.md         ({{lines}} lines)\n  {{path}}\u002Freference\u002Fexamples.md  ({{lines}} lines)\n\nInstall: \u002Fplugin install (copy to your skills directory)\nPublish: clawhub publish {{path}}\n\nSource: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is portable, the memory is project-specific)\n```\n\n## Examples\n\n### Extracting a debugging pattern\n\n```\n\u002Fsi:extract \"Fix for Docker builds failing on Apple Silicon with platform mismatch\"\n```\n\nCreates `docker-m1-fixes\u002FSKILL.md` with:\n- The platform mismatch error message\n- Three solutions (build flag, Dockerfile, docker-compose)\n- Trade-offs table\n- Performance note about Rosetta 2 emulation\n\n### Extracting a workflow pattern\n\n```\n\u002Fsi:extract \"Always regenerate TypeScript API client after modifying OpenAPI spec\"\n```\n\nCreates `api-client-regen\u002FSKILL.md` with:\n- Why manual regen is needed\n- The exact command sequence\n- CI integration snippet\n- Common failure modes\n\n## Tips\n\n- Extract patterns that would save time in a *different* project\n- Keep skills focused — one problem per skill\n- Include the error messages people would search for\n- Test the skill by reading it without the original context — does it make sense?\n","# \u002Fsi:extract — Create Skills from Patterns\n\nTransforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.\n\n## Usage\n\n```\n\u002Fsi:extract \u003Cpattern description>                  # Interactive extraction\n\u002Fsi:extract \u003Cpattern> --name docker-m1-fixes       # Specify skill name\n\u002Fsi:extract \u003Cpattern> --output .\u002Fskills\u002F            # Custom output directory\n\u002Fsi:extract \u003Cpattern> --dry-run                     # Preview without creating files\n```\n\n## When to Extract\n\nA learning qualifies for skill extraction when ANY of these are true:\n\n| Criterion | Signal |\n|---|---|\n| **Recurring** | Same issue across 2+ projects |\n| **Non-obvious** | Required real debugging to discover |\n| **Broadly applicable** | Not tied to one specific codebase |\n| **Complex solution** | Multi-step fix that's easy to forget |\n| **User-flagged** | \"Save this as a skill\", \"I want to reuse this\" |\n\n## Workflow\n\n### Step 1: Identify the pattern\n\nRead the user's description. Search auto-memory for related entries:\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -rni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002F\"\n```\n\nIf found in auto-memory, use those entries as source material. If not, use the user's description directly.\n\n### Step 2: Determine skill scope\n\nAsk (max 2 questions):\n- \"What problem does this solve?\" (if not clear)\n- \"Should this include code examples?\" (if applicable)\n\n### Step 3: Generate skill name\n\nRules for naming:\n- Lowercase, hyphens between words\n- Descriptive but concise (2-4 words)\n- Examples: `docker-m1-fixes`, `api-timeout-patterns`, `pnpm-workspace-setup`\n\n### Step 4: Create the skill files\n\n**Spawn the `skill-extractor` agent** for the actual file generation.\n\nThe agent creates:\n\n```\n\u003Cskill-name>\u002F\n├── SKILL.md            # Main skill file with frontmatter\n├── README.md           # Human-readable overview\n└── reference\u002F          # (optional) Supporting documentation\n    └── examples.md     # Concrete examples and edge cases\n```\n\n### Step 5: SKILL.md structure\n\nThe generated SKILL.md must follow this format:\n\n```markdown\n---\nname: \"skill-name\"\ndescription: \"\u003Cone-line description>. Use when: \u003Ctrigger conditions>.\"\n---\n\n# \u003CSkill Title>\n\n> One-line summary of what this skill solves.\n\n## Quick Reference\n\n| Problem | Solution |\n|---------|----------|\n| {{problem 1}} | {{solution 1}} |\n| {{problem 2}} | {{solution 2}} |\n\n## The Problem\n\n{{2-3 sentences explaining what goes wrong and why it's non-obvious.}}\n\n## Solutions\n\n### Option 1: {{Name}} (Recommended)\n\n{{Step-by-step with code examples.}}\n\n### Option 2: {{Alternative}}\n\n{{For when Option 1 doesn't apply.}}\n\n## Trade-offs\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Option 1 | {{pros}} | {{cons}} |\n| Option 2 | {{pros}} | {{cons}} |\n\n## Edge Cases\n\n- {{edge case 1 and how to handle it}}\n- {{edge case 2 and how to handle it}}\n```\n\n### Step 6: Quality gates\n\nBefore finalizing, verify:\n\n- [ ] SKILL.md has valid YAML frontmatter with `name` and `description`\n- [ ] `name` matches the folder name (lowercase, hyphens)\n- [ ] Description includes \"Use when:\" trigger conditions\n- [ ] Solutions are self-contained (no external context needed)\n- [ ] Code examples are complete and copy-pasteable\n- [ ] No project-specific hardcoded values (paths, URLs, credentials)\n- [ ] No unnecessary dependencies\n\n### Step 7: Report\n\n```\n✅ Skill extracted: {{skill-name}}\n\nFiles created:\n  {{path}}\u002FSKILL.md          ({{lines}} lines)\n  {{path}}\u002FREADME.md         ({{lines}} lines)\n  {{path}}\u002Freference\u002Fexamples.md  ({{lines}} lines)\n\nInstall: \u002Fplugin install (copy to your skills directory)\nPublish: clawhub publish {{path}}\n\nSource: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is portable, the memory is project-specific)\n```\n\n## Examples\n\n### Extracting a debugging pattern\n\n```\n\u002Fsi:extract \"Fix for Docker builds failing on Apple Silicon with platform mismatch\"\n```\n\nCreates `docker-m1-fixes\u002FSKILL.md` with:\n- The platform mismatch error message\n- Three solutions (build flag, Dockerfile, docker-compose)\n- Trade-offs table\n- Performance note about Rosetta 2 emulation\n\n### Extracting a workflow pattern\n\n```\n\u002Fsi:extract \"Always regenerate TypeScript API client after modifying OpenAPI spec\"\n```\n\nCreates `api-client-regen\u002FSKILL.md` with:\n- Why manual regen is needed\n- The exact command sequence\n- CI integration snippet\n- Common failure modes\n\n## Tips\n\n- Extract patterns that would save time in a *different* project\n- Keep skills focused — one problem per skill\n- Include the error messages people would search for\n- Test the skill by reading it without the original context — does it make sense?\n",{"name":5,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-self-improving-agent\u002Fskills\u002Fextract","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill extract",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill extract",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill extract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-self-improving-agent\u002Fskills\u002Fextract\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\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},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\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":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"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":81,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]