[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N1BH5WDFFA11CZDFVRVZ1T":3,"skill-same:01M6N1BH5WDFFA11CZDFVRVZ1T":74},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6N1BH5WDFFA11CZDFVRVZ1T","openspec",null,"Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when \u002Fopsx commands are mentioned.","Kernel8901\u002Fai-agent-skills-classification","Kernel8901","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72647553?v=4","01M6KV388J2H5PNC8D8P940BJD","01M6KV38CS5B3AY63RKZB410YM",7,"MIT","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F人工智能与大型语言模型\u002Fopenspec\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"custom","design","features","spec-driven","feature planning","proposal","trigger","feature","commands","spec writing","change management","work","planning","development","tasks","change","workflows","cli","writing","2026-11-10 10:12:30",false,"---\nname: openspec\ndescription: Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when \u002Fopsx commands are mentioned.\n---\n\n# OpenSpec — Spec-Driven Development\n\nOpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation.\n\n## Setup\n\n```bash\n# Install globally\nnpm install -g @fission-ai\u002Fopenspec@latest\n\n# Initialize in a project\ncd \u002Fpath\u002Fto\u002Fproject\nopenspec init --tools claude\n\n# Update after CLI upgrade\nopenspec update\n```\n\n## Core Workflow\n\nEach change follows: **new → plan → apply → verify → archive**\n\n### 1. Start a Change\n\n```bash\n# Create change folder with default schema\nopenspec new change \u003Cname>\n\n# With specific schema\nopenspec new change \u003Cname> --schema tdd-driven\n```\n\n### 2. Plan (Create Artifacts)\n\nUse the CLI `instructions` command to get enriched prompts for each artifact:\n\n```bash\n# Get instructions for next artifact\nopenspec instructions --change \u003Cname> --json\n\n# Check progress\nopenspec status --change \u003Cname> --json\n```\n\n**Artifact sequence (spec-driven schema):**\n1. `proposal.md` — Why and what (intent, scope, approach)\n2. `specs\u002F` — Requirements + scenarios (Given\u002FWhen\u002FThen)\n3. `design.md` — Technical approach and architecture decisions\n4. `tasks.md` — Implementation checklist with checkboxes\n\n### 3. Implement\n\nRead `tasks.md` and work through items, marking `[x]` as complete.\n\n### 4. Verify\n\n```bash\nopenspec validate --change \u003Cname> --json\n```\n\nChecks completeness, correctness, and coherence.\n\n### 5. Archive\n\n```bash\nopenspec archive \u003Cname> --yes\n```\n\nMerges delta specs into main `openspec\u002Fspecs\u002F` and moves change to archive.\n\n## Agent Workflow (How to Use as an AI Agent)\n\nWhen the user asks to build\u002Fmigrate\u002Frefactor something with OpenSpec:\n\n1. **Check project state:**\n   ```bash\n   openspec list --json           # Active changes\n   openspec list --specs --json   # Current specs\n   openspec schemas --json        # Available schemas\n   ```\n\n2. **Create the change:**\n   ```bash\n   openspec new change \u003Cname> [--schema \u003Cschema>]\n   ```\n\n3. **For each artifact**, get instructions and create the file:\n   ```bash\n   openspec instructions \u003Cartifact> --change \u003Cname> --json\n   openspec status --change \u003Cname> --json\n   ```\n   Then write the artifact file to `openspec\u002Fchanges\u002F\u003Cname>\u002F`.\n\n4. **Implement** tasks from `tasks.md`.\n\n5. **Validate and archive:**\n   ```bash\n   openspec validate \u003Cname> --json\n   openspec archive \u003Cname> --yes\n   ```\n\n## CLI Quick Reference\n\n| Command | Purpose |\n|---------|---------|\n| `openspec list [--specs] [--json]` | List changes or specs |\n| `openspec show \u003Cname> [--json]` | Show change\u002Fspec details |\n| `openspec status --change \u003Cname> [--json]` | Artifact completion status |\n| `openspec instructions [artifact] --change \u003Cname> [--json]` | Get enriched creation instructions |\n| `openspec validate [name] [--all] [--json]` | Validate changes\u002Fspecs |\n| `openspec archive \u003Cname> [--yes]` | Archive completed change |\n| `openspec schemas [--json]` | List available schemas |\n| `openspec templates [--json]` | Show template paths |\n| `openspec config` | View\u002Fmodify settings |\n\nAlways use `--json` for programmatic\u002Fagent use.\n\n## Custom Schemas\n\nSchemas define artifact sequences. Create custom ones for different workflows:\n\n```bash\n# Fork built-in schema\nopenspec schema fork spec-driven my-workflow\n\n# Create from scratch\nopenspec schema init my-workflow\n\n# Validate\nopenspec schema validate my-workflow\n```\n\nSchema files live in `openspec\u002Fschemas\u002F\u003Cname>\u002Fschema.yaml` with templates in `templates\u002F`.\n\nFor schema structure details, see [references\u002Fschemas.md](references\u002Fschemas.md).\n\n## Project Structure\n\n```\nproject\u002F\n├── openspec\u002F\n│   ├── config.yaml          # Project config (default schema, context, rules)\n│   ├── specs\u002F               # Source of truth — current system behavior\n│   ├── changes\u002F             # Active changes (one folder each)\n│   │   └── \u003Cchange-name>\u002F\n│   │       ├── .openspec.yaml\n│   │       ├── proposal.md\n│   │       ├── specs\u002F       # Delta specs (what's changing)\n│   │       ├── design.md\n│   │       └── tasks.md\n│   └── schemas\u002F             # Custom schemas\n└── .claude\u002Fskills\u002F          # Auto-generated Claude integration\n```\n\n## Spec Format\n\nSpecs use RFC 2119 keywords (SHALL\u002FMUST\u002FSHOULD\u002FMAY) with Given\u002FWhen\u002FThen scenarios:\n\n```markdown\n### Requirement: User Authentication\nThe system SHALL issue a JWT token upon successful login.\n\n#### Scenario: Valid credentials\n- GIVEN a user with valid credentials\n- WHEN the user submits login form\n- THEN a JWT token is returned\n```\n\n## Delta Specs\n\nChanges don't rewrite specs — they describe deltas (ADDED\u002FMODIFIED\u002FREMOVED) that merge into main specs on archive.\n\n## Config\n\n`openspec\u002Fconfig.yaml` sets defaults:\n\n```yaml\nschema: spec-driven      # or tdd-driven, rapid, custom\ncontext: |\n  Tech stack: TypeScript, React, Node.js\n  Testing: Jest\nrules:\n  proposal:\n    - Include rollback plan\n  specs:\n    - Use Given\u002FWhen\u002FThen format\n```\n","# OpenSpec — Spec-Driven Development\n\nOpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation.\n\n## Setup\n\n```bash\n# Install globally\nnpm install -g @fission-ai\u002Fopenspec@latest\n\n# Initialize in a project\ncd \u002Fpath\u002Fto\u002Fproject\nopenspec init --tools claude\n\n# Update after CLI upgrade\nopenspec update\n```\n\n## Core Workflow\n\nEach change follows: **new → plan → apply → verify → archive**\n\n### 1. Start a Change\n\n```bash\n# Create change folder with default schema\nopenspec new change \u003Cname>\n\n# With specific schema\nopenspec new change \u003Cname> --schema tdd-driven\n```\n\n### 2. Plan (Create Artifacts)\n\nUse the CLI `instructions` command to get enriched prompts for each artifact:\n\n```bash\n# Get instructions for next artifact\nopenspec instructions --change \u003Cname> --json\n\n# Check progress\nopenspec status --change \u003Cname> --json\n```\n\n**Artifact sequence (spec-driven schema):**\n1. `proposal.md` — Why and what (intent, scope, approach)\n2. `specs\u002F` — Requirements + scenarios (Given\u002FWhen\u002FThen)\n3. `design.md` — Technical approach and architecture decisions\n4. `tasks.md` — Implementation checklist with checkboxes\n\n### 3. Implement\n\nRead `tasks.md` and work through items, marking `[x]` as complete.\n\n### 4. Verify\n\n```bash\nopenspec validate --change \u003Cname> --json\n```\n\nChecks completeness, correctness, and coherence.\n\n### 5. Archive\n\n```bash\nopenspec archive \u003Cname> --yes\n```\n\nMerges delta specs into main `openspec\u002Fspecs\u002F` and moves change to archive.\n\n## Agent Workflow (How to Use as an AI Agent)\n\nWhen the user asks to build\u002Fmigrate\u002Frefactor something with OpenSpec:\n\n1. **Check project state:**\n   ```bash\n   openspec list --json           # Active changes\n   openspec list --specs --json   # Current specs\n   openspec schemas --json        # Available schemas\n   ```\n\n2. **Create the change:**\n   ```bash\n   openspec new change \u003Cname> [--schema \u003Cschema>]\n   ```\n\n3. **For each artifact**, get instructions and create the file:\n   ```bash\n   openspec instructions \u003Cartifact> --change \u003Cname> --json\n   openspec status --change \u003Cname> --json\n   ```\n   Then write the artifact file to `openspec\u002Fchanges\u002F\u003Cname>\u002F`.\n\n4. **Implement** tasks from `tasks.md`.\n\n5. **Validate and archive:**\n   ```bash\n   openspec validate \u003Cname> --json\n   openspec archive \u003Cname> --yes\n   ```\n\n## CLI Quick Reference\n\n| Command | Purpose |\n|---------|---------|\n| `openspec list [--specs] [--json]` | List changes or specs |\n| `openspec show \u003Cname> [--json]` | Show change\u002Fspec details |\n| `openspec status --change \u003Cname> [--json]` | Artifact completion status |\n| `openspec instructions [artifact] --change \u003Cname> [--json]` | Get enriched creation instructions |\n| `openspec validate [name] [--all] [--json]` | Validate changes\u002Fspecs |\n| `openspec archive \u003Cname> [--yes]` | Archive completed change |\n| `openspec schemas [--json]` | List available schemas |\n| `openspec templates [--json]` | Show template paths |\n| `openspec config` | View\u002Fmodify settings |\n\nAlways use `--json` for programmatic\u002Fagent use.\n\n## Custom Schemas\n\nSchemas define artifact sequences. Create custom ones for different workflows:\n\n```bash\n# Fork built-in schema\nopenspec schema fork spec-driven my-workflow\n\n# Create from scratch\nopenspec schema init my-workflow\n\n# Validate\nopenspec schema validate my-workflow\n```\n\nSchema files live in `openspec\u002Fschemas\u002F\u003Cname>\u002Fschema.yaml` with templates in `templates\u002F`.\n\nFor schema structure details, see [references\u002Fschemas.md](references\u002Fschemas.md).\n\n## Project Structure\n\n```\nproject\u002F\n├── openspec\u002F\n│   ├── config.yaml          # Project config (default schema, context, rules)\n│   ├── specs\u002F               # Source of truth — current system behavior\n│   ├── changes\u002F             # Active changes (one folder each)\n│   │   └── \u003Cchange-name>\u002F\n│   │       ├── .openspec.yaml\n│   │       ├── proposal.md\n│   │       ├── specs\u002F       # Delta specs (what's changing)\n│   │       ├── design.md\n│   │       └── tasks.md\n│   └── schemas\u002F             # Custom schemas\n└── .claude\u002Fskills\u002F          # Auto-generated Claude integration\n```\n\n## Spec Format\n\nSpecs use RFC 2119 keywords (SHALL\u002FMUST\u002FSHOULD\u002FMAY) with Given\u002FWhen\u002FThen scenarios:\n\n```markdown\n### Requirement: User Authentication\nThe system SHALL issue a JWT token upon successful login.\n\n#### Scenario: Valid credentials\n- GIVEN a user with valid credentials\n- WHEN the user submits login form\n- THEN a JWT token is returned\n```\n\n## Delta Specs\n\nChanges don't rewrite specs — they describe deltas (ADDED\u002FMODIFIED\u002FREMOVED) that merge into main specs on archive.\n\n## Config\n\n`openspec\u002Fconfig.yaml` sets defaults:\n\n```yaml\nschema: spec-driven      # or tdd-driven, rapid, custom\ncontext: |\n  Tech stack: TypeScript, React, Node.js\n  Testing: Jest\nrules:\n  proposal:\n    - Include rollback plan\n  specs:\n    - Use Given\u002FWhen\u002FThen format\n```\n",{"name":5,"description":7},"main","f4cb2d49f7667e79ef7804f50396d5aaffdf1f56","人工智能与大型语言模型\u002Fopenspec",1,"https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification","https:\u002F\u002Fgithub.com\u002FKernel8901","a little little little dobe in life but science geek","2026-04-05 16:43:56",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Kernel8901\u002Fai-agent-skills-classification --skill openspec",{"tool":56,"command":57},"bunx","bunx skills add Kernel8901\u002Fai-agent-skills-classification --skill openspec",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Kernel8901\u002Fai-agent-skills-classification --skill openspec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F人工智能与大型语言模型\u002Fopenspec\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"_meta.json","REFERENCE","参考文档",270,"https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F人工智能与大型语言模型\u002Fopenspec\u002F_meta.json",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fschemas.md",3256,"https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F人工智能与大型语言模型\u002Fopenspec\u002Freferences\u002Fschemas.md",[75,99,135,146,156,186],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":37},"01M6Q5R6WZ06RRB9RQTW54B34B","zyfai","Earn yield on any Ethereum wallet on Base, Arbitrum, and Plasma. Use when a user wants passive DeFi yield on their funds. Deploys a non-custodial subaccount (Safe) linked to their EOA, enables automated yield optimization, and lets them deposit\u002Fwithdraw anytime.","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fzyfai-sdk\u002FSKILL.md",[],[77,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"safe","ethereum","defi","Optimization","user","use","Wallet","base","deposit","withdraw","yield","arbitrum","non-custodial","passive","defi yield","earn","yield optimization",{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":117,"publishedAt":37},"01M6Q5R337B5JSNER4P4YS03TN","zerion-api","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fzerion-api\u002FSKILL.md",[104,109,112],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[118,119,120,121,122,123,124,84,125,88,126,127,128,129,130,131,132,133,134],"api","zerion api","zerion","MCP","mcp server","server","blockchain","transactions","crypto wallet","crypto","evm","solana","query","across","positions","token","prices",{"skillNo":136,"name":137,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":37},"01M6Q5QZFYTDAZMZ27BN5VZXAR","zerion-api-skill","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fzerion-api-skill\u002FSKILL.md",[140,141,142],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[118,144,145,119,120,121,122,123,124,84,125,88,127,128,129,130,131,132,133,134],"api skill","zerion api skill",{"skillNo":147,"name":148,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":37},"01M6Q5QW17QW98RA3FE45E4RD8","zerion-api-mcp","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fzerion-api-mcp\u002FSKILL.md",[151,152,153],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[121,118,155,119,120,122,123,84,125,88,126,127,128,129,130,131,132,133,134],"zerion api mcp",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":165,"publishedAt":37},"01M6Q5QQYZB7A501BDEQWKGSJT","yahoo-finance-forex","Fetches real-time FOREX news and market data from Yahoo Finance for major currency pairs (EUR\u002FUSD, GBP\u002FUSD, USD\u002FJPY, etc.). Analyzes sentiment and provides trading context.","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fyahoo-finance-forex\u002FSKILL.md",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000040","财务",[166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185],"finance","yahoo finance","forex","yahoo","yahoo finance forex","github","https","sentiment","real-time","python3","install","Market","usd","news","time","currency","gbp","pip","market data","for",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":37},"01M6Q5QM6VS84WZVM7BKXXPF32","yahoo-finance","This skill should be used when the user asks to \"get stock prices\", \"check stock quotes\", \"look up earnings\", \"get financial data\", \"find trending stocks\", or needs stock market data from Yahoo Finance.","https:\u002F\u002Fgithub.com\u002FKernel8901\u002Fai-agent-skills-classification\u002Fblob\u002Fmain\u002F金融\u002Fyahoo-finance-cli\u002FSKILL.md",[192],{"categoryNo":163,"categoryName":164,"taxonomyType":115,"taxonomyTypeDesc":116},[166,167,169,35,194,195,196,197,198,177,199,200,201,202,203,204,205,206,134,184],"homebrew","find","check","brew","up","local","get","stock","link","trending","sf","quotes","ln"]