Skill Writer: guide your agent through creating well-structured Agent Skills (short listing)
Create well-structured Agent Skills for Claude Code — scope, location, structure, frontmatter, effective descriptions, supporting files, validation, testing and troubleshooting
- What
- Create well-structured Agent Skills for Claude Code — scope, location, structure, frontmatter, effective descriptions, supporting files, validation, testing and troubleshooting
- Cost
- Free
- Needs
- a new Agent Skill to author for Claude Code (the skill is guidance the agent follows, not software to install)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @pytorch's skill-writer, a meta-skill that guides an agent through creating well-structured Agent Skills for Claude Code. A 10-step process: determine skill scope (ask clarifying questions, keep one skill to one capability), choose the location (personal `~/.claude/skills/` vs project `.claude/skills/`), create the directory structure, write the SKILL.md frontmatter (name rules — lowercase, hyphens, max 64 chars, must match directory; description formula — what it does plus when to use it, max 1024 chars, with trigger words), write effective descriptions (good vs too-vague examples), structure the content (overview, quick start, instructions, examples, best practices, requirements, advanced usage), add optional supporting files (reference.md, examples.md, scripts/, templates/) with progressive disclosure, validate (file structure, frontmatter, content quality), test (restart Claude Code, ask relevant questions, verify activation), and debug (make descriptions more specific, check location, validate YAML, `claude --debug`). Includes common patterns (read-only skill with allowed-tools, script-based skill, multi-file skill), best practices for authors (one skill one purpose, specific descriptions, concrete examples, list dependencies, test, version, progressive disclosure), and a validation checklist plus troubleshooting section. Honest caveats: written for Claude Code specifically (paths, restart behavior, debug flags) — adapt paths to your own agent harness; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a new Agent Skill to author for Claude Code (the skill is guidance the agent follows, not software to install) Install "Skill Writer: guide your agent through creating well-structured Agent Skills" for me. It gives my agent @pytorch's 10-step skill-authoring process: scope the skill, choose personal vs project location, create the structure, write valid frontmatter (naming rules, effective description formula), structure content, add supporting files with progressive disclosure, validate, test activation, and debug. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/pytorch/pytorch/blob/main/.claude/skills/skill-writer/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "skill-writer". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. describe the new skill's capability so the agent can scope it; adapt paths if your harness is not Claude Code). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.