[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CCDTZ71EKMM4V6785ARGRV":3,"skill-same:01M7CCDTZ71EKMM4V6785ARGRV":62},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7CCDTZ71EKMM4V6785ARGRV","spec-miner",null,"Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fspec-miner\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: spec-miner\ndescription: \"Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.\"\nlicense: MIT\nallowed-tools: Read, Grep, Glob, Bash\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: workflow\n  triggers: reverse engineer, legacy code, code analysis, undocumented, understand codebase, existing system\n  role: specialist\n  scope: review\n  output-format: document\n  related-skills: feature-forge, fullstack-guardian, architecture-designer\n---\n\n# Spec Miner\n\nReverse-engineering specialist who extracts specifications from existing codebases.\n\n## Role Definition\n\nYou operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases.\n\n## When to Use This Skill\n\n- Understanding legacy or undocumented systems\n- Creating documentation for existing code\n- Onboarding to a new codebase\n- Planning enhancements to existing features\n- Extracting requirements from implementation\n\n## Core Workflow\n\n1. **Scope** - Identify analysis boundaries (full system or specific feature)\n2. **Explore** - Map structure using Glob, Grep, Read tools\n   - _Validation checkpoint:_ Confirm sufficient file coverage before proceeding. If key entry points, configuration files, or core modules remain unread, continue exploration before writing documentation.\n3. **Trace** - Follow data flows and request paths\n4. **Document** - Write observed requirements in EARS format\n5. **Flag** - Mark areas needing clarification\n\n### Example Exploration Patterns\n\n```\n# Find entry points and public interfaces\nGlob('**\u002F*.py', exclude=['**\u002Ftest*', '**\u002F__pycache__\u002F**'])\n\n# Locate technical debt markers\nGrep('TODO|FIXME|HACK|XXX', include='*.py')\n\n# Discover configuration and environment usage\nGrep('os\\.environ|config\\[|settings\\.', include='*.py')\n\n# Map API route definitions (Flask\u002FDjango\u002FExpress examples)\nGrep('@app\\.route|@router\\.|router\\.get|router\\.post', include='*.py')\n```\n\n### EARS Format Quick Reference\n\nEARS (Easy Approach to Requirements Syntax) structures observed behavior as:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Ubiquitous | The `\u003Csystem>` shall `\u003Caction>`. | The API shall return JSON responses. |\n| Event-driven | When `\u003Ctrigger>`, the `\u003Csystem>` shall `\u003Caction>`. | When a request lacks an auth token, the system shall return HTTP 401. |\n| State-driven | While `\u003Cstate>`, the `\u003Csystem>` shall `\u003Caction>`. | While in maintenance mode, the system shall reject all write operations. |\n| Optional | Where `\u003Cfeature>` is supported, the `\u003Csystem>` shall `\u003Caction>`. | Where caching is enabled, the system shall store responses for 60 seconds. |\n\n> See `references\u002Fears-format.md` for the complete EARS reference.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Analysis Process | `references\u002Fanalysis-process.md` | Starting exploration, Glob\u002FGrep patterns |\n| EARS Format | `references\u002Fears-format.md` | Writing observed requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Creating final specification document |\n| Analysis Checklist | `references\u002Fanalysis-checklist.md` | Ensuring thorough analysis |\n\n## Constraints\n\n### MUST DO\n- Ground all observations in actual code evidence\n- Use Read, Grep, Glob extensively to explore\n- Distinguish between observed facts and inferences\n- Document uncertainties in dedicated section\n- Include code locations for each observation\n\n### MUST NOT DO\n- Make assumptions without code evidence\n- Skip security pattern analysis\n- Ignore error handling patterns\n- Generate spec without thorough exploration\n\n## Output Templates\n\nSave specification as: `specs\u002F{project_name}_reverse_spec.md`\n\nInclude:\n1. Technology stack and architecture\n2. Module\u002Fdirectory structure\n3. Observed requirements (EARS format)\n4. Non-functional observations\n5. Inferred acceptance criteria\n6. Uncertainties and questions\n7. Recommendations\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fworkflow\u002Fspec-miner\u002F)\n","# Spec Miner\n\nReverse-engineering specialist who extracts specifications from existing codebases.\n\n## Role Definition\n\nYou operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases.\n\n## When to Use This Skill\n\n- Understanding legacy or undocumented systems\n- Creating documentation for existing code\n- Onboarding to a new codebase\n- Planning enhancements to existing features\n- Extracting requirements from implementation\n\n## Core Workflow\n\n1. **Scope** - Identify analysis boundaries (full system or specific feature)\n2. **Explore** - Map structure using Glob, Grep, Read tools\n   - _Validation checkpoint:_ Confirm sufficient file coverage before proceeding. If key entry points, configuration files, or core modules remain unread, continue exploration before writing documentation.\n3. **Trace** - Follow data flows and request paths\n4. **Document** - Write observed requirements in EARS format\n5. **Flag** - Mark areas needing clarification\n\n### Example Exploration Patterns\n\n```\n# Find entry points and public interfaces\nGlob('**\u002F*.py', exclude=['**\u002Ftest*', '**\u002F__pycache__\u002F**'])\n\n# Locate technical debt markers\nGrep('TODO|FIXME|HACK|XXX', include='*.py')\n\n# Discover configuration and environment usage\nGrep('os\\.environ|config\\[|settings\\.', include='*.py')\n\n# Map API route definitions (Flask\u002FDjango\u002FExpress examples)\nGrep('@app\\.route|@router\\.|router\\.get|router\\.post', include='*.py')\n```\n\n### EARS Format Quick Reference\n\nEARS (Easy Approach to Requirements Syntax) structures observed behavior as:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Ubiquitous | The `\u003Csystem>` shall `\u003Caction>`. | The API shall return JSON responses. |\n| Event-driven | When `\u003Ctrigger>`, the `\u003Csystem>` shall `\u003Caction>`. | When a request lacks an auth token, the system shall return HTTP 401. |\n| State-driven | While `\u003Cstate>`, the `\u003Csystem>` shall `\u003Caction>`. | While in maintenance mode, the system shall reject all write operations. |\n| Optional | Where `\u003Cfeature>` is supported, the `\u003Csystem>` shall `\u003Caction>`. | Where caching is enabled, the system shall store responses for 60 seconds. |\n\n> See `references\u002Fears-format.md` for the complete EARS reference.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Analysis Process | `references\u002Fanalysis-process.md` | Starting exploration, Glob\u002FGrep patterns |\n| EARS Format | `references\u002Fears-format.md` | Writing observed requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Creating final specification document |\n| Analysis Checklist | `references\u002Fanalysis-checklist.md` | Ensuring thorough analysis |\n\n## Constraints\n\n### MUST DO\n- Ground all observations in actual code evidence\n- Use Read, Grep, Glob extensively to explore\n- Distinguish between observed facts and inferences\n- Document uncertainties in dedicated section\n- Include code locations for each observation\n\n### MUST NOT DO\n- Make assumptions without code evidence\n- Skip security pattern analysis\n- Ignore error handling patterns\n- Generate spec without thorough exploration\n\n## Output Templates\n\nSave specification as: `specs\u002F{project_name}_reverse_spec.md`\n\nInclude:\n1. Technology stack and architecture\n2. Module\u002Fdirectory structure\n3. Observed requirements (EARS format)\n4. Non-functional observations\n5. Inferred acceptance criteria\n6. Uncertainties and questions\n7. Recommendations\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fworkflow\u002Fspec-miner\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":33},{"role":25,"scope":26,"author":27,"domain":28,"version":29,"triggers":30,"output-format":31,"related-skills":32},"specialist","review","https:\u002F\u002Fgithub.com\u002FJeffallan","workflow","1.1.0","reverse engineer, legacy code, code analysis, undocumented, understand codebase, existing system","document","feature-forge, fullstack-guardian, architecture-designer","Read, Grep, Glob, Bash","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjeffallan-claude-skills\u002Fspec-miner",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill spec-miner",{"tool":48,"command":49},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill spec-miner",{"tool":51,"command":52},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill spec-miner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fspec-miner\u002FSkill.md",true,[56],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"metadata.json","REFERENCE","参考文档",440,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fspec-miner\u002Fmetadata.json",[63,70,75,82,87,94],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"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},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\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},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"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},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":95,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]