[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CAYP848JR9T7S4AC5WE3R":3,"skill-same:01M73CAYP848JR9T7S4AC5WE3R":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M73CAYP848JR9T7S4AC5WE3R","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.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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":14,"metadata":23,"description":7,"allowed-tools":32},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"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","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fspec-miner",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add roohe\u002Fagentic-super-skills --skill spec-miner",{"tool":47,"command":48},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill spec-miner",{"tool":50,"command":51},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill spec-miner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fanalysis-checklist.md","REFERENCE","参考文档",2040,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002Freferences\u002Fanalysis-checklist.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fanalysis-process.md",1280,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002Freferences\u002Fanalysis-process.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fears-format.md",1835,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002Freferences\u002Fears-format.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fspecification-template.md",2475,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fspec-miner\u002Freferences\u002Fspecification-template.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]