[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CXD0HE327MXY76DDRG7NEP":3,"skill-same:01M6CXD0HE327MXY76DDRG7NEP":89},{"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":28,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":82},"01M6CXD0HE327MXY76DDRG7NEP","skill-writer",null,"Write high-quality agent skills (SKILL.md files) for ClawdHub\u002FMoltHub. Use when creating a new skill from scratch, structuring skill content, writing effective frontmatter and descriptions, choosing section patterns, or following best practices for agent-consumable technical documentation.","albertdobmeyer\u002Fopentrapp","albertdobmeyer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116975874?v=4","01M6CXARYAZ30V12S7PSG93R84","Albert Dobmeyer","01M6CXAS2FG5GCXZYN3XBFJQV6",2,"MIT","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Fskills\u002Fskill-writer\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"writer","skill writer","technical","new skill","patterns","clawdhub","npx","files","use","write","writing","quality","content","best practices","win32","documentation","linux","technical documentation","2026-11-10 10:12:30",false,"---\nname: skill-writer\nversion: 1.0.0\ndescription: Write high-quality agent skills (SKILL.md files) for ClawdHub\u002FMoltHub. Use when creating a new skill from scratch, structuring skill content, writing effective frontmatter and descriptions, choosing section patterns, or following best practices for agent-consumable technical documentation.\nmetadata: {\"clawdbot\":{\"emoji\":\"✍️\",\"requires\":{\"anyBins\":[\"npx\"]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n# Skill Writer\n\nWrite well-structured, effective SKILL.md files for the ClawdHub registry. Covers the skill format specification, frontmatter schema, content patterns, example quality, and common anti-patterns.\n\n## When to Use\n\n- Creating a new skill from scratch\n- Structuring technical content as an agent skill\n- Writing frontmatter that the registry indexes correctly\n- Choosing section organization for different skill types\n- Reviewing your own skill before publishing\n\n## The SKILL.md Format\n\nA skill is a single Markdown file with YAML frontmatter. The agent loads it on demand and follows its instructions.\n\n```markdown\n---\nname: my-skill-slug\ndescription: One-sentence description of when to use this skill.\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool1\",\"tool2\"]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n# Skill Title\n\nOne-paragraph summary of what this skill covers.\n\n## When to Use\n\n- Bullet list of trigger scenarios\n\n## Main Content Sections\n\n### Subsection with examples\n\nCode blocks, commands, patterns...\n\n## Tips\n\n- Practical advice bullets\n```\n\n## Frontmatter Schema\n\n### `name` (required)\n\nThe skill's slug identifier. Must match what you publish with.\n\n```yaml\nname: my-skill\n```\n\nRules:\n- Lowercase, hyphenated: `csv-pipeline`, `git-workflows`\n- No spaces, no underscores\n- Keep it short and descriptive (1-3 words)\n- Check for slug collisions before publishing: `npx molthub@latest search \"your-slug\"`\n\n### `description` (required)\n\nThe single most important field. This is what:\n1. The registry indexes for semantic search (vector embeddings)\n2. The agent reads to decide whether to activate the skill\n3. Users see when browsing search results\n\n```yaml\n# GOOD: Specific triggers and scope\ndescription: Write Makefiles for any project type. Use when setting up build automation, defining multi-target builds, managing dependencies between tasks, creating project task runners, or using Make for non-C projects (Go, Python, Docker, Node.js). Also covers Just and Task as modern alternatives.\n\n# BAD: Vague, no triggers\ndescription: A skill about Makefiles.\n\n# BAD: Too long (gets truncated in search results)\ndescription: This skill covers everything you need to know about Makefiles including variables, targets, prerequisites, pattern rules, automatic variables, phony targets, conditional logic, multi-directory builds, includes, silent execution, and also covers Just and Task as modern alternatives to Make for projects that use Go, Python, Docker, or Node.js...\n```\n\nPattern for effective descriptions:\n```\n[What it does]. Use when [trigger 1], [trigger 2], [trigger 3]. Also covers [related topic].\n```\n\n### `metadata` (required)\n\nJSON object with the `clawdbot` schema:\n\n```yaml\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"make\",\"just\"]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n```\n\nFields:\n- **`emoji`**: Single emoji displayed in registry listings\n- **`requires.anyBins`**: Array of CLI tools the skill needs (at least one must be available)\n- **`os`**: Array of supported platforms: `\"linux\"`, `\"darwin\"` (macOS), `\"win32\"` (Windows)\n\nChoose `requires.anyBins` carefully:\n```yaml\n# Good: lists the actual tools the skill's commands use\n\"requires\": {\"anyBins\": [\"docker\", \"docker-compose\"]}\n\n# Bad: lists generic tools every system has\n\"requires\": {\"anyBins\": [\"bash\", \"echo\"]}\n\n# Good for skills that work via multiple tools\n\"requires\": {\"anyBins\": [\"make\", \"just\", \"task\"]}\n```\n\n## Content Structure\n\n### The \"When to Use\" Section\n\nAlways include this immediately after the title paragraph. It tells the agent (and the user) the specific scenarios where this skill applies.\n\n```markdown\n## When to Use\n\n- Automating build, test, lint, deploy commands\n- Defining dependencies between tasks (build before test)\n- Creating a project-level task runner\n- Replacing long CLI commands with short targets\n```\n\nRules:\n- 4-8 bullet points\n- Each bullet is a concrete scenario, not an abstract concept\n- Start with a verb or gerund: \"Automating...\", \"Debugging...\", \"Converting...\"\n- Don't repeat the description field verbatim\n\n### Main Content Sections\n\nOrganize by task, not by concept. The agent needs to find the right command for a specific situation.\n\n```markdown\n## GOOD: Organized by task\n## Encode and Decode\n### Base64\n### URL Encoding\n### Hex\n\n## BAD: Organized by abstraction\n## Theory of Encoding\n## Encoding Types\n## Advanced Topics\n```\n\n### Code Blocks\n\nEvery section should have at least one code block. Skills without code blocks are opinions, not tools.\n\n````markdown\n## GOOD: Concrete, runnable example\n```bash\n# Encode a string to Base64\necho -n \"Hello, World!\" | base64\n# SGVsbG8sIFdvcmxkIQ==\n```\n\n## BAD: Abstract description\nBase64 encoding converts binary data to ASCII text using a 64-character alphabet...\n````\n\nCode block best practices:\n- **Always specify the language** (`bash`, `python`, `javascript`, `yaml`, `sql`, etc.)\n- **Show the output** in a comment below the command\n- **Use realistic values**, not `foo`\u002F`bar` (use `myapp`, `api-server`, real IP formats)\n- **Include the most common case first**, then variations\n- **Add inline comments** for non-obvious flags or arguments\n\n### Multi-Language Coverage\n\nIf a skill applies across languages, use consistent section structure:\n\n```markdown\n## Hashing\n\n### Bash\n```bash\necho -n \"Hello\" | sha256sum\n```\n\n### JavaScript\n```javascript\nconst crypto = require('crypto');\ncrypto.createHash('sha256').update('Hello').digest('hex');\n```\n\n### Python\n```python\nimport hashlib\nhashlib.sha256(b\"Hello\").hexdigest()\n```\n```\n\nOrder: Bash first (most universal), then by popularity for the topic.\n\n### The \"Tips\" Section\n\nEnd every skill with a Tips section. These are the distilled wisdom — the things that save hours of debugging.\n\n```markdown\n## Tips\n\n- The number one Makefile bug: using spaces instead of tabs for indentation.\n- SHA-256 is the standard for integrity checks. MD5 is fine for dedup but broken for cryptographic use.\n- Never schedule critical cron jobs between 1:00-3:00 AM if DST applies.\n```\n\nRules:\n- 5-10 bullets\n- Each tip is a standalone insight (no dependencies on other tips)\n- Prioritize gotchas and non-obvious behavior over basic advice\n- No \"always use best practices\" platitudes\n\n## Skill Types and Templates\n\n### CLI Tool Reference\n\nFor skills about a specific tool or command family.\n\n```markdown\n---\nname: tool-name\ndescription: [What tool does]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool-name\"]}}}\n---\n\n# Tool Name\n\n[One paragraph: what it does and why you'd use it.]\n\n## When to Use\n- [4-6 scenarios]\n\n## Quick Reference\n[Most common commands with examples]\n\n## Common Operations\n### [Operation 1]\n### [Operation 2]\n\n## Advanced Patterns\n### [Pattern 1]\n\n## Troubleshooting\n### [Common error and fix]\n\n## Tips\n```\n\n### Language\u002FFramework Reference\n\nFor skills about patterns in a specific language or framework.\n\n```markdown\n---\nname: pattern-name\ndescription: [Pattern] in [language\u002Fframework]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"runtime\"]}}}\n---\n\n# Pattern Name\n\n## When to Use\n\n## Quick Reference\n[Cheat sheet \u002F syntax summary]\n\n## Patterns\n### [Pattern 1 — with full example]\n### [Pattern 2 — with full example]\n\n## Cross-Language Comparison (if applicable)\n\n## Anti-Patterns\n[What NOT to do, with explanation]\n\n## Tips\n```\n\n### Workflow\u002FProcess Guide\n\nFor skills about multi-step processes.\n\n```markdown\n---\nname: workflow-name\ndescription: [Workflow description]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool1\",\"tool2\"]}}}\n---\n\n# Workflow Name\n\n## When to Use\n\n## Prerequisites\n[What needs to be set up first]\n\n## Step-by-Step\n### Step 1: [Action]\n### Step 2: [Action]\n### Step 3: [Action]\n\n## Variations\n### [Variation for different context]\n\n## Troubleshooting\n\n## Tips\n```\n\n## Anti-Patterns\n\n### Too abstract\n\n```markdown\n# BAD\n## Error Handling\nError handling is important for robust applications. You should always\nhandle errors properly to prevent unexpected crashes...\n\n# GOOD\n## Error Handling\n```bash\n# Bash: exit on any error\nset -euo pipefail\n\n# Trap for cleanup on exit\ntrap 'rm -f \"$TMPFILE\"' EXIT\n```\n```\n\n### Too narrow\n\n```markdown\n# BAD: Only useful for one specific case\n---\nname: react-useeffect-cleanup\ndescription: How to clean up useEffect hooks in React\n---\n\n# GOOD: Broad enough to be a real reference\n---\nname: react-hooks\ndescription: React hooks patterns. Use when working with useState, useEffect, useCallback, useMemo, custom hooks, or debugging hook-related issues.\n---\n```\n\n### Wall of text without examples\n\nIf any section goes more than 10 lines without a code block, it's too text-heavy. Break it up with examples.\n\n### Missing cross-references\n\nIf your skill mentions another tool or concept that has its own skill, note it:\n\n```markdown\n# For Docker networking issues, see the `container-debug` skill.\n# For regex syntax details, see the `regex-patterns` skill.\n```\n\n### Outdated commands\n\nVerify every command works on current tool versions. Common traps:\n- Docker Compose: `docker-compose` (v1) vs. `docker compose` (v2)\n- Python: `pip` vs. `pip3`, `python` vs. `python3`\n- Node.js: CommonJS (`require`) vs. ESM (`import`)\n\n## Size Guidelines\n\n| Metric | Target | Too Short | Too Long |\n|---|---|---|---|\n| Total lines | 300-550 | \u003C 150 | > 700 |\n| Sections | 5-10 | \u003C 3 | > 15 |\n| Code blocks | 15-40 | \u003C 8 | > 60 |\n| Tips | 5-10 | \u003C 3 | > 15 |\n\nA skill under 150 lines probably lacks examples. A skill over 700 lines should be split into two skills.\n\n## Publishing Checklist\n\nBefore publishing, verify:\n\n1. **Frontmatter is valid YAML** — test by pasting into a YAML validator\n2. **Description starts with what the skill does** — not \"This skill...\" or \"A skill for...\"\n3. **Every section has at least one code block** — no text-only sections in the main content\n4. **Commands actually work** — test in a clean environment\n5. **No placeholder values left** — search for leftover task markers, `example.com` used as real URLs\n6. **Slug is available** — `npx molthub@latest search \"your-slug\"` returns no exact match\n7. **`requires.anyBins` lists real dependencies** — tools the skill's commands actually invoke\n8. **Tips section exists** — with 5+ actionable, non-obvious bullets\n\n## Publishing\n\n```bash\n# Publish a new skill\nnpx molthub@latest publish .\u002Fskills\u002Fmy-skill \\\n  --slug my-skill \\\n  --name \"My Skill\" \\\n  --version 1.0.0 \\\n  --changelog \"Initial release\"\n\n# Update an existing skill\nnpx molthub@latest publish .\u002Fskills\u002Fmy-skill \\\n  --slug my-skill \\\n  --name \"My Skill\" \\\n  --version 1.1.0 \\\n  --changelog \"Added new section on X\"\n\n# Verify it's published\nnpx molthub@latest search \"my-skill\"\n```\n\n## Tips\n\n- The `description` field is your skill's search ranking. Spend more time on it than any single content section. Include the specific verbs and nouns users would search for.\n- Lead with the most common use case. If 80% of users need \"how to encode Base64\", put that before \"how to convert between MessagePack and CBOR.\"\n- Every code example should be copy-pasteable. If it needs setup that isn't shown, add the setup.\n- Write for the agent, not the human. The agent needs unambiguous instructions it can follow step by step. Avoid \"you might want to consider\" — say \"do X when Y.\"\n- Test your skill by asking an agent to use it on a real task. If the agent can't follow the instructions to produce a correct result, the skill needs work.\n- Prefer `bash` code blocks for commands, even in language-specific skills. The agent often operates via shell, and bash blocks signal \"run this.\"\n- Don't duplicate what `--help` already provides. Focus on patterns, combinations, and the non-obvious things that `--help` doesn't teach.\n- Version your skills semantically: patch for typo fixes, minor for new sections, major for restructures. The registry tracks version history.\n","# Skill Writer\n\nWrite well-structured, effective SKILL.md files for the ClawdHub registry. Covers the skill format specification, frontmatter schema, content patterns, example quality, and common anti-patterns.\n\n## When to Use\n\n- Creating a new skill from scratch\n- Structuring technical content as an agent skill\n- Writing frontmatter that the registry indexes correctly\n- Choosing section organization for different skill types\n- Reviewing your own skill before publishing\n\n## The SKILL.md Format\n\nA skill is a single Markdown file with YAML frontmatter. The agent loads it on demand and follows its instructions.\n\n```markdown\n---\nname: my-skill-slug\ndescription: One-sentence description of when to use this skill.\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool1\",\"tool2\"]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n# Skill Title\n\nOne-paragraph summary of what this skill covers.\n\n## When to Use\n\n- Bullet list of trigger scenarios\n\n## Main Content Sections\n\n### Subsection with examples\n\nCode blocks, commands, patterns...\n\n## Tips\n\n- Practical advice bullets\n```\n\n## Frontmatter Schema\n\n### `name` (required)\n\nThe skill's slug identifier. Must match what you publish with.\n\n```yaml\nname: my-skill\n```\n\nRules:\n- Lowercase, hyphenated: `csv-pipeline`, `git-workflows`\n- No spaces, no underscores\n- Keep it short and descriptive (1-3 words)\n- Check for slug collisions before publishing: `npx molthub@latest search \"your-slug\"`\n\n### `description` (required)\n\nThe single most important field. This is what:\n1. The registry indexes for semantic search (vector embeddings)\n2. The agent reads to decide whether to activate the skill\n3. Users see when browsing search results\n\n```yaml\n# GOOD: Specific triggers and scope\ndescription: Write Makefiles for any project type. Use when setting up build automation, defining multi-target builds, managing dependencies between tasks, creating project task runners, or using Make for non-C projects (Go, Python, Docker, Node.js). Also covers Just and Task as modern alternatives.\n\n# BAD: Vague, no triggers\ndescription: A skill about Makefiles.\n\n# BAD: Too long (gets truncated in search results)\ndescription: This skill covers everything you need to know about Makefiles including variables, targets, prerequisites, pattern rules, automatic variables, phony targets, conditional logic, multi-directory builds, includes, silent execution, and also covers Just and Task as modern alternatives to Make for projects that use Go, Python, Docker, or Node.js...\n```\n\nPattern for effective descriptions:\n```\n[What it does]. Use when [trigger 1], [trigger 2], [trigger 3]. Also covers [related topic].\n```\n\n### `metadata` (required)\n\nJSON object with the `clawdbot` schema:\n\n```yaml\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"make\",\"just\"]},\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n```\n\nFields:\n- **`emoji`**: Single emoji displayed in registry listings\n- **`requires.anyBins`**: Array of CLI tools the skill needs (at least one must be available)\n- **`os`**: Array of supported platforms: `\"linux\"`, `\"darwin\"` (macOS), `\"win32\"` (Windows)\n\nChoose `requires.anyBins` carefully:\n```yaml\n# Good: lists the actual tools the skill's commands use\n\"requires\": {\"anyBins\": [\"docker\", \"docker-compose\"]}\n\n# Bad: lists generic tools every system has\n\"requires\": {\"anyBins\": [\"bash\", \"echo\"]}\n\n# Good for skills that work via multiple tools\n\"requires\": {\"anyBins\": [\"make\", \"just\", \"task\"]}\n```\n\n## Content Structure\n\n### The \"When to Use\" Section\n\nAlways include this immediately after the title paragraph. It tells the agent (and the user) the specific scenarios where this skill applies.\n\n```markdown\n## When to Use\n\n- Automating build, test, lint, deploy commands\n- Defining dependencies between tasks (build before test)\n- Creating a project-level task runner\n- Replacing long CLI commands with short targets\n```\n\nRules:\n- 4-8 bullet points\n- Each bullet is a concrete scenario, not an abstract concept\n- Start with a verb or gerund: \"Automating...\", \"Debugging...\", \"Converting...\"\n- Don't repeat the description field verbatim\n\n### Main Content Sections\n\nOrganize by task, not by concept. The agent needs to find the right command for a specific situation.\n\n```markdown\n## GOOD: Organized by task\n## Encode and Decode\n### Base64\n### URL Encoding\n### Hex\n\n## BAD: Organized by abstraction\n## Theory of Encoding\n## Encoding Types\n## Advanced Topics\n```\n\n### Code Blocks\n\nEvery section should have at least one code block. Skills without code blocks are opinions, not tools.\n\n````markdown\n## GOOD: Concrete, runnable example\n```bash\n# Encode a string to Base64\necho -n \"Hello, World!\" | base64\n# SGVsbG8sIFdvcmxkIQ==\n```\n\n## BAD: Abstract description\nBase64 encoding converts binary data to ASCII text using a 64-character alphabet...\n````\n\nCode block best practices:\n- **Always specify the language** (`bash`, `python`, `javascript`, `yaml`, `sql`, etc.)\n- **Show the output** in a comment below the command\n- **Use realistic values**, not `foo`\u002F`bar` (use `myapp`, `api-server`, real IP formats)\n- **Include the most common case first**, then variations\n- **Add inline comments** for non-obvious flags or arguments\n\n### Multi-Language Coverage\n\nIf a skill applies across languages, use consistent section structure:\n\n```markdown\n## Hashing\n\n### Bash\n```bash\necho -n \"Hello\" | sha256sum\n```\n\n### JavaScript\n```javascript\nconst crypto = require('crypto');\ncrypto.createHash('sha256').update('Hello').digest('hex');\n```\n\n### Python\n```python\nimport hashlib\nhashlib.sha256(b\"Hello\").hexdigest()\n```\n```\n\nOrder: Bash first (most universal), then by popularity for the topic.\n\n### The \"Tips\" Section\n\nEnd every skill with a Tips section. These are the distilled wisdom — the things that save hours of debugging.\n\n```markdown\n## Tips\n\n- The number one Makefile bug: using spaces instead of tabs for indentation.\n- SHA-256 is the standard for integrity checks. MD5 is fine for dedup but broken for cryptographic use.\n- Never schedule critical cron jobs between 1:00-3:00 AM if DST applies.\n```\n\nRules:\n- 5-10 bullets\n- Each tip is a standalone insight (no dependencies on other tips)\n- Prioritize gotchas and non-obvious behavior over basic advice\n- No \"always use best practices\" platitudes\n\n## Skill Types and Templates\n\n### CLI Tool Reference\n\nFor skills about a specific tool or command family.\n\n```markdown\n---\nname: tool-name\ndescription: [What tool does]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool-name\"]}}}\n---\n\n# Tool Name\n\n[One paragraph: what it does and why you'd use it.]\n\n## When to Use\n- [4-6 scenarios]\n\n## Quick Reference\n[Most common commands with examples]\n\n## Common Operations\n### [Operation 1]\n### [Operation 2]\n\n## Advanced Patterns\n### [Pattern 1]\n\n## Troubleshooting\n### [Common error and fix]\n\n## Tips\n```\n\n### Language\u002FFramework Reference\n\nFor skills about patterns in a specific language or framework.\n\n```markdown\n---\nname: pattern-name\ndescription: [Pattern] in [language\u002Fframework]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"runtime\"]}}}\n---\n\n# Pattern Name\n\n## When to Use\n\n## Quick Reference\n[Cheat sheet \u002F syntax summary]\n\n## Patterns\n### [Pattern 1 — with full example]\n### [Pattern 2 — with full example]\n\n## Cross-Language Comparison (if applicable)\n\n## Anti-Patterns\n[What NOT to do, with explanation]\n\n## Tips\n```\n\n### Workflow\u002FProcess Guide\n\nFor skills about multi-step processes.\n\n```markdown\n---\nname: workflow-name\ndescription: [Workflow description]. Use when [scenario 1], [scenario 2].\nmetadata: {\"clawdbot\":{\"emoji\":\"?\",\"requires\":{\"anyBins\":[\"tool1\",\"tool2\"]}}}\n---\n\n# Workflow Name\n\n## When to Use\n\n## Prerequisites\n[What needs to be set up first]\n\n## Step-by-Step\n### Step 1: [Action]\n### Step 2: [Action]\n### Step 3: [Action]\n\n## Variations\n### [Variation for different context]\n\n## Troubleshooting\n\n## Tips\n```\n\n## Anti-Patterns\n\n### Too abstract\n\n```markdown\n# BAD\n## Error Handling\nError handling is important for robust applications. You should always\nhandle errors properly to prevent unexpected crashes...\n\n# GOOD\n## Error Handling\n```bash\n# Bash: exit on any error\nset -euo pipefail\n\n# Trap for cleanup on exit\ntrap 'rm -f \"$TMPFILE\"' EXIT\n```\n```\n\n### Too narrow\n\n```markdown\n# BAD: Only useful for one specific case\n---\nname: react-useeffect-cleanup\ndescription: How to clean up useEffect hooks in React\n---\n\n# GOOD: Broad enough to be a real reference\n---\nname: react-hooks\ndescription: React hooks patterns. Use when working with useState, useEffect, useCallback, useMemo, custom hooks, or debugging hook-related issues.\n---\n```\n\n### Wall of text without examples\n\nIf any section goes more than 10 lines without a code block, it's too text-heavy. Break it up with examples.\n\n### Missing cross-references\n\nIf your skill mentions another tool or concept that has its own skill, note it:\n\n```markdown\n# For Docker networking issues, see the `container-debug` skill.\n# For regex syntax details, see the `regex-patterns` skill.\n```\n\n### Outdated commands\n\nVerify every command works on current tool versions. Common traps:\n- Docker Compose: `docker-compose` (v1) vs. `docker compose` (v2)\n- Python: `pip` vs. `pip3`, `python` vs. `python3`\n- Node.js: CommonJS (`require`) vs. ESM (`import`)\n\n## Size Guidelines\n\n| Metric | Target | Too Short | Too Long |\n|---|---|---|---|\n| Total lines | 300-550 | \u003C 150 | > 700 |\n| Sections | 5-10 | \u003C 3 | > 15 |\n| Code blocks | 15-40 | \u003C 8 | > 60 |\n| Tips | 5-10 | \u003C 3 | > 15 |\n\nA skill under 150 lines probably lacks examples. A skill over 700 lines should be split into two skills.\n\n## Publishing Checklist\n\nBefore publishing, verify:\n\n1. **Frontmatter is valid YAML** — test by pasting into a YAML validator\n2. **Description starts with what the skill does** — not \"This skill...\" or \"A skill for...\"\n3. **Every section has at least one code block** — no text-only sections in the main content\n4. **Commands actually work** — test in a clean environment\n5. **No placeholder values left** — search for leftover task markers, `example.com` used as real URLs\n6. **Slug is available** — `npx molthub@latest search \"your-slug\"` returns no exact match\n7. **`requires.anyBins` lists real dependencies** — tools the skill's commands actually invoke\n8. **Tips section exists** — with 5+ actionable, non-obvious bullets\n\n## Publishing\n\n```bash\n# Publish a new skill\nnpx molthub@latest publish .\u002Fskills\u002Fmy-skill \\\n  --slug my-skill \\\n  --name \"My Skill\" \\\n  --version 1.0.0 \\\n  --changelog \"Initial release\"\n\n# Update an existing skill\nnpx molthub@latest publish .\u002Fskills\u002Fmy-skill \\\n  --slug my-skill \\\n  --name \"My Skill\" \\\n  --version 1.1.0 \\\n  --changelog \"Added new section on X\"\n\n# Verify it's published\nnpx molthub@latest search \"my-skill\"\n```\n\n## Tips\n\n- The `description` field is your skill's search ranking. Spend more time on it than any single content section. Include the specific verbs and nouns users would search for.\n- Lead with the most common use case. If 80% of users need \"how to encode Base64\", put that before \"how to convert between MessagePack and CBOR.\"\n- Every code example should be copy-pasteable. If it needs setup that isn't shown, add the setup.\n- Write for the agent, not the human. The agent needs unambiguous instructions it can follow step by step. Avoid \"you might want to consider\" — say \"do X when Y.\"\n- Test your skill by asking an agent to use it on a real task. If the agent can't follow the instructions to produce a correct result, the skill needs work.\n- Prefer `bash` code blocks for commands, even in language-specific skills. The agent often operates via shell, and bash blocks signal \"run this.\"\n- Don't duplicate what `--help` already provides. Focus on patterns, combinations, and the non-obvious things that `--help` doesn't teach.\n- Version your skills semantically: patch for typo fixes, minor for new sections, major for restructures. The registry tracks version history.\n",{"name":5,"version":52,"metadata":53,"description":7},"1.0.0",{"clawdbot":54},{"os":55,"emoji":57,"requires":58},[45,56,43],"darwin","✍️",{"anyBins":59},[35],"main","4ad602ec8c10264470f26774e1075a29f1bee581","workloads\u002Fskills\u002Fskills\u002Fskill-writer",1,"https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp","https:\u002F\u002Fopentrapp.com","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer","albertdobmeyer.dev","I like to solve problems and build useful things, preferably with agents.","2026-09-14 04:32:08",{"source":8,"skillName":5,"commands":71,"prompt":80,"zipAvailable":81},[72,74,77],{"tool":35,"command":73},"npx skills add albertdobmeyer\u002Fopentrapp --skill skill-writer",{"tool":75,"command":76},"bunx","bunx skills add albertdobmeyer\u002Fopentrapp --skill skill-writer",{"tool":78,"command":79},"pnpm","pnpm dlx skills add albertdobmeyer\u002Fopentrapp --skill skill-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Fskills\u002Fskill-writer\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},".trust","OTHER","其他",301,"https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Fskills\u002Fskill-writer\u002F.trust",[90,100,111,125,134,141],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":47},"01M6CXDR8F14T6QQJBH1N1VVYS","note-summarizer","Summarizes your notes for quick review.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Ftests\u002Fjudge-fixtures\u002Fnote-summarizer\u002FSKILL.md",[],[97,98,99],"note summarizer","notes","review",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":47},"01M6CXDNEB4DENBG58DDP5VEN0","judge-clean","A clean reference skill for the judge second-opinion test.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Ftests\u002Fjudge-fixtures\u002Fjudge-clean\u002FSKILL.md",[],[107,108,109,110],"clean","judge clean","test","reference",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":47},"01M6CXDK1RYQH2PZK36XJ5QNGZ","{{SKILL_NAME=null}=null}","TODO — Write a one-sentence description of when to use this workflow skill (50-200 chars). Start with an action verb.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Ftemplates\u002Fworkflow\u002FSKILL.md",[117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,38,37,122,45,123,43,124],"skill name","{{SKILL NAME=null}=null}","{Skill Name=null}","todo","workflow","start",{"skillNo":126,"name":113,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":47},"01M6CXDGPG4KYBNAYV9YMNY77P","TODO — Write a one-sentence description of when to use this language\u002Fsyntax reference (50-200 chars). Start with an action verb.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Ftemplates\u002Flanguage-ref\u002FSKILL.md",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,132,38,37,110,133,122,45,124,43],"syntax","language",{"skillNo":135,"name":113,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":47},"01M6CXDEB146MPK7ES94E4CCFN","TODO — Write a one-sentence description of when to use this skill (50-200 chars). Start with an action verb.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Ftemplates\u002Fcli-tool\u002FSKILL.md",[139],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,120,119,45,43,124,38,37,122],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":47},"01M6CXDB3R546NFVZ874VGJAVN","test-patterns","Write and run tests across languages and frameworks. Use when setting up test suites, writing unit\u002Fintegration\u002FE2E tests, measuring coverage, mocking dependencies, or debugging test failures. Covers Node.js (Jest\u002FVitest), Python (pytest), Go, Rust, and Bash.","https:\u002F\u002Fgithub.com\u002Falbertdobmeyer\u002Fopentrapp\u002Fblob\u002Fmain\u002Fworkloads\u002Fskills\u002Fskills\u002Ftest-patterns\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[33,151,109,152,153,154,155,156,157,43,158,159,160,161,38,162,163,164,165,39],"test patterns","up","go","rust","e2e tests","debugging","run","Bash","vitest","python3","node","coverage","pytest","jest","across"]