[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XCB4GT950CW6F23ZTXA6FZ":3,"skill-same:01M6XCB4GT950CW6F23ZTXA6FZ":68},{"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":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6XCB4GT950CW6F23ZTXA6FZ","skill-template-generator",null,"Generate properly-formatted SKILL.md files from extracted architectural patterns. Turns raw pattern descriptions into reusable skills that OpenSpace can discover, select, and evolve.","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fskill-template-generator\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"template","skill template","generator","skill template generator","generate","select","evolve","files","reusable","patterns","pattern","discover","can","openspace","2026-11-10 10:12:30",false,"---\nname: skill-template-generator\ndescription: Generate properly-formatted SKILL.md files from extracted architectural patterns. Turns raw pattern descriptions into reusable skills that OpenSpace can discover, select, and evolve.\n---\n\n# Skill Template Generator\n\nGiven a structured pattern description (from `codebase-pattern-analyzer` or manual analysis), generate a valid SKILL.md file that OpenSpace can register, select for tasks, and evolve over time.\n\n## When to Use\n\n- After extracting a pattern from a reference codebase, you need to package it as a reusable skill\n- You want to create a new skill that teaches an agent how to perform a specific kind of task\n- You are converting informal documentation or code examples into the SKILL.md format\n\n## SKILL.md Format\n\nEvery skill is a directory containing at minimum a `SKILL.md` file:\n\n```\nmy-skill-name\u002F\n├── SKILL.md            # Required — the skill definition\n├── scripts\u002F            # Optional — helper scripts\n├── references\u002F         # Optional — reference data files\n└── assets\u002F             # Optional — images, templates\n```\n\n### Frontmatter (Required)\n\nThe file MUST start with YAML frontmatter containing exactly two fields:\n\n```yaml\n---\nname: my-skill-name\ndescription: One-sentence description of what this skill teaches. Must be specific enough for LLM skill selection to match it to relevant tasks.\n---\n```\n\n**Rules:**\n- `name` must match the directory name (kebab-case, lowercase)\n- `description` should be 15-40 words, include key terms an LLM would search for\n- No other frontmatter fields — everything else goes in the markdown body\n\n### Body Structure\n\nThe markdown body follows this template:\n\n```markdown\n# [Skill Title]\n\n[1-2 sentence summary of what this skill enables]\n\n## When to Use\n\n- [Trigger condition 1]\n- [Trigger condition 2]\n- [Trigger condition 3]\n\n## [Core Content Sections]\n\n[Step-by-step instructions, code templates, API references, etc.]\n\n## Key Patterns\n\n1. [Convention or best practice 1]\n2. [Convention or best practice 2]\n...\n```\n\n## Step 1: Determine Skill Category\n\nMatch the pattern to one of three OpenSpace categories:\n\n| Category | Use When | Example |\n|----------|----------|---------|\n| `tool_guide` | The skill teaches how to use a specific tool or technique | \"How to analyze a codebase\", \"How to use Finnhub API\" |\n| `workflow` | The skill prescribes an end-to-end procedure with ordered steps | \"Create a panel component\", \"Set up API proxy endpoint\" |\n| `reference` | The skill provides knowledge that informs decisions | \"WorldMonitor architecture index\", \"News API comparison\" |\n\nThe category affects how OpenSpace judges the skill during execution analysis:\n- **workflow**: Was the agent able to follow the prescribed steps?\n- **tool_guide**: Did the agent use the described tool\u002Fapproach?\n- **reference**: Did the knowledge influence agent decisions?\n\n## Step 2: Write the Description\n\nThe `description` field is the **most critical line** — it determines whether OpenSpace selects this skill for a given task.\n\n**Good descriptions** (specific, searchable):\n- \"Create a dashboard panel component using vanilla TypeScript DOM API, following the worldmonitor Panel architecture.\"\n- \"Integrate with Finnhub Stock API for real-time and historical stock market data.\"\n- \"CSS grid layout system for a responsive panel dashboard with dark theme.\"\n\n**Bad descriptions** (vague, generic):\n- \"A useful skill for building things.\"\n- \"TypeScript patterns.\"\n- \"How to make a panel.\"\n\n**Formula**: `[Action verb] + [specific subject] + [key technology\u002Fapproach] + [context\u002Fproject reference]`\n\n## Step 3: Write Actionable Instructions\n\nThe body must be concrete enough that an AI agent can follow it without guessing.\n\n### For Workflow Skills\n\nInclude:\n1. **File paths** — exact paths where files should be created (`src\u002Fcomponents\u002FMyPanel.ts`)\n2. **Code templates** — complete, runnable code blocks (not pseudocode)\n3. **Import statements** — every import the code needs\n4. **Interface definitions** — typed data shapes\n5. **Integration points** — how this connects to other parts of the project\n\nUse `{baseDir}` for paths relative to the skill directory:\n```\nRead the reference file at {baseDir}\u002Freferences\u002Fexample.json\n```\n\n### For Tool Guide Skills\n\nInclude:\n1. **API endpoints** — full URLs with parameter documentation\n2. **Auth mechanism** — how to authenticate (query param, header, etc.)\n3. **Response shapes** — JSON examples with field descriptions\n4. **Rate limits** — free tier limitations\n5. **Error handling** — common errors and how to handle them\n\n### For Reference Skills\n\nInclude:\n1. **Structured index** — tables, lists, or maps of the reference material\n2. **Key file paths** — where to find specific things in the reference codebase\n3. **Architecture decisions** — WHY certain patterns were chosen\n4. **Comparison tables** — alternatives and tradeoffs\n\n## Step 4: Add Dependency Hints\n\nIf the skill depends on patterns from other skills, mention them explicitly:\n\n```markdown\n## Prerequisites\n\nThis skill builds on:\n- `panel-component` — for the Panel base class\n- `data-service` — for the circuit breaker pattern\n- `api-proxy-endpoint` — for server-side API key isolation\n```\n\nThis helps OpenSpace understand skill composition when DERIVING new skills.\n\n## Step 5: Validate the Skill\n\nBefore saving, verify:\n\n1. **Frontmatter is valid YAML** — no tabs, proper indentation, quotes around special chars\n2. **Name matches directory** — `name: foo-bar` lives in `foo-bar\u002FSKILL.md`\n3. **Code blocks are complete** — every snippet can be copy-pasted and run\n4. **No broken references** — all file paths and URLs are valid\n5. **Description is specific** — would an LLM pick this skill for the right task?\n\n## Example: Converting a Pattern to a Skill\n\n**Input** (from codebase-pattern-analyzer):\n\n```\nPattern: Circuit Breaker Data Service\nSource: worldmonitor\u002Fsrc\u002Fservices\u002F*.ts\nCategory: service\nStructure: Module-level CircuitBreaker instance, async fetch functions, typed interfaces\nKey code: createCircuitBreaker({ name, cacheTtlMs }), breaker.execute(fn, default)\n```\n\n**Output** (`data-service\u002FSKILL.md`):\n\n```markdown\n---\nname: data-service\ndescription: Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components.\n---\n\n# Data Service Pattern\n\nEach panel's data comes from a dedicated service module in `src\u002Fservices\u002F`. ...\n\n## Circuit Breaker\n\n[Full implementation code]\n\n## Service Module Pattern\n\n[Template with typed interfaces, breaker usage, export functions]\n\n## Key Patterns\n\n1. One circuit breaker per API endpoint\n2. Export typed interfaces for data shapes\n3. Wrap fetch calls in breaker.execute(fn, defaultValue)\n...\n```\n\n## Evolution Hooks\n\nSkills generated by this workflow are designed to evolve:\n\n- **FIX**: When an API changes or code pattern breaks, OpenSpace updates the skill in-place\n- **DERIVED**: When a new panel needs a similar service, OpenSpace derives a specialized version\n- **CAPTURED**: When an agent discovers a novel pattern during execution, OpenSpace captures it as a new skill\n\nThe better the initial skill quality, the better the evolved descendants.\n\n","# Skill Template Generator\n\nGiven a structured pattern description (from `codebase-pattern-analyzer` or manual analysis), generate a valid SKILL.md file that OpenSpace can register, select for tasks, and evolve over time.\n\n## When to Use\n\n- After extracting a pattern from a reference codebase, you need to package it as a reusable skill\n- You want to create a new skill that teaches an agent how to perform a specific kind of task\n- You are converting informal documentation or code examples into the SKILL.md format\n\n## SKILL.md Format\n\nEvery skill is a directory containing at minimum a `SKILL.md` file:\n\n```\nmy-skill-name\u002F\n├── SKILL.md            # Required — the skill definition\n├── scripts\u002F            # Optional — helper scripts\n├── references\u002F         # Optional — reference data files\n└── assets\u002F             # Optional — images, templates\n```\n\n### Frontmatter (Required)\n\nThe file MUST start with YAML frontmatter containing exactly two fields:\n\n```yaml\n---\nname: my-skill-name\ndescription: One-sentence description of what this skill teaches. Must be specific enough for LLM skill selection to match it to relevant tasks.\n---\n```\n\n**Rules:**\n- `name` must match the directory name (kebab-case, lowercase)\n- `description` should be 15-40 words, include key terms an LLM would search for\n- No other frontmatter fields — everything else goes in the markdown body\n\n### Body Structure\n\nThe markdown body follows this template:\n\n```markdown\n# [Skill Title]\n\n[1-2 sentence summary of what this skill enables]\n\n## When to Use\n\n- [Trigger condition 1]\n- [Trigger condition 2]\n- [Trigger condition 3]\n\n## [Core Content Sections]\n\n[Step-by-step instructions, code templates, API references, etc.]\n\n## Key Patterns\n\n1. [Convention or best practice 1]\n2. [Convention or best practice 2]\n...\n```\n\n## Step 1: Determine Skill Category\n\nMatch the pattern to one of three OpenSpace categories:\n\n| Category | Use When | Example |\n|----------|----------|---------|\n| `tool_guide` | The skill teaches how to use a specific tool or technique | \"How to analyze a codebase\", \"How to use Finnhub API\" |\n| `workflow` | The skill prescribes an end-to-end procedure with ordered steps | \"Create a panel component\", \"Set up API proxy endpoint\" |\n| `reference` | The skill provides knowledge that informs decisions | \"WorldMonitor architecture index\", \"News API comparison\" |\n\nThe category affects how OpenSpace judges the skill during execution analysis:\n- **workflow**: Was the agent able to follow the prescribed steps?\n- **tool_guide**: Did the agent use the described tool\u002Fapproach?\n- **reference**: Did the knowledge influence agent decisions?\n\n## Step 2: Write the Description\n\nThe `description` field is the **most critical line** — it determines whether OpenSpace selects this skill for a given task.\n\n**Good descriptions** (specific, searchable):\n- \"Create a dashboard panel component using vanilla TypeScript DOM API, following the worldmonitor Panel architecture.\"\n- \"Integrate with Finnhub Stock API for real-time and historical stock market data.\"\n- \"CSS grid layout system for a responsive panel dashboard with dark theme.\"\n\n**Bad descriptions** (vague, generic):\n- \"A useful skill for building things.\"\n- \"TypeScript patterns.\"\n- \"How to make a panel.\"\n\n**Formula**: `[Action verb] + [specific subject] + [key technology\u002Fapproach] + [context\u002Fproject reference]`\n\n## Step 3: Write Actionable Instructions\n\nThe body must be concrete enough that an AI agent can follow it without guessing.\n\n### For Workflow Skills\n\nInclude:\n1. **File paths** — exact paths where files should be created (`src\u002Fcomponents\u002FMyPanel.ts`)\n2. **Code templates** — complete, runnable code blocks (not pseudocode)\n3. **Import statements** — every import the code needs\n4. **Interface definitions** — typed data shapes\n5. **Integration points** — how this connects to other parts of the project\n\nUse `{baseDir}` for paths relative to the skill directory:\n```\nRead the reference file at {baseDir}\u002Freferences\u002Fexample.json\n```\n\n### For Tool Guide Skills\n\nInclude:\n1. **API endpoints** — full URLs with parameter documentation\n2. **Auth mechanism** — how to authenticate (query param, header, etc.)\n3. **Response shapes** — JSON examples with field descriptions\n4. **Rate limits** — free tier limitations\n5. **Error handling** — common errors and how to handle them\n\n### For Reference Skills\n\nInclude:\n1. **Structured index** — tables, lists, or maps of the reference material\n2. **Key file paths** — where to find specific things in the reference codebase\n3. **Architecture decisions** — WHY certain patterns were chosen\n4. **Comparison tables** — alternatives and tradeoffs\n\n## Step 4: Add Dependency Hints\n\nIf the skill depends on patterns from other skills, mention them explicitly:\n\n```markdown\n## Prerequisites\n\nThis skill builds on:\n- `panel-component` — for the Panel base class\n- `data-service` — for the circuit breaker pattern\n- `api-proxy-endpoint` — for server-side API key isolation\n```\n\nThis helps OpenSpace understand skill composition when DERIVING new skills.\n\n## Step 5: Validate the Skill\n\nBefore saving, verify:\n\n1. **Frontmatter is valid YAML** — no tabs, proper indentation, quotes around special chars\n2. **Name matches directory** — `name: foo-bar` lives in `foo-bar\u002FSKILL.md`\n3. **Code blocks are complete** — every snippet can be copy-pasted and run\n4. **No broken references** — all file paths and URLs are valid\n5. **Description is specific** — would an LLM pick this skill for the right task?\n\n## Example: Converting a Pattern to a Skill\n\n**Input** (from codebase-pattern-analyzer):\n\n```\nPattern: Circuit Breaker Data Service\nSource: worldmonitor\u002Fsrc\u002Fservices\u002F*.ts\nCategory: service\nStructure: Module-level CircuitBreaker instance, async fetch functions, typed interfaces\nKey code: createCircuitBreaker({ name, cacheTtlMs }), breaker.execute(fn, default)\n```\n\n**Output** (`data-service\u002FSKILL.md`):\n\n```markdown\n---\nname: data-service\ndescription: Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components.\n---\n\n# Data Service Pattern\n\nEach panel's data comes from a dedicated service module in `src\u002Fservices\u002F`. ...\n\n## Circuit Breaker\n\n[Full implementation code]\n\n## Service Module Pattern\n\n[Template with typed interfaces, breaker usage, export functions]\n\n## Key Patterns\n\n1. One circuit breaker per API endpoint\n2. Export typed interfaces for data shapes\n3. Wrap fetch calls in breaker.execute(fn, defaultValue)\n...\n```\n\n## Evolution Hooks\n\nSkills generated by this workflow are designed to evolve:\n\n- **FIX**: When an API changes or code pattern breaks, OpenSpace updates the skill in-place\n- **DERIVED**: When a new panel needs a similar service, OpenSpace derives a specialized version\n- **CAPTURED**: When an agent discovers a novel pattern during execution, OpenSpace captures it as a new skill\n\nThe better the initial skill quality, the better the evolved descendants.\n\n",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","showcase\u002Fskills\u002Fskill-template-generator","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill skill-template-generator",{"tool":54,"command":55},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill skill-template-generator",{"tool":57,"command":58},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill skill-template-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fskill-template-generator\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},".skill_id","OTHER","其他",38,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fskill-template-generator\u002F.skill_id",[69,92,109,118,147,163],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[76,77,78,79,80,81,82,83,84,85,86,87,88,30,89,23,90,91],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","only","file","python",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":37},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[99,100,77,90,101,91,102,103,104,105,106,23,107,108,81,84,86],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"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":37},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[116,77,81,117,86,103,23,90,91,84],"write special chars heredoc","shell",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":37},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[130,131,132,133,134,79,135,136,137,138,139,84,140,141,32,142,143,144,145,146],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","edge functions","integrations","open","api","data",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":37},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[154,155,156,157,84,158,108,159,160,161,162],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":37},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[170,171,172,173,174,175,90,176,177,178],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]