Skill Writer

Skill Writer is an official skill in the PyTorch repository. It helps people and coding agents plan, write, and validate Agent Skills for Claude Code. Its primary source is https://github.com/pytorch/pytorch/tree/main/.claude/skills/skill-writer. According to the provider, the workflow is intended for SKILL.md files, frontmatter, skill structure, discoverability, and deciding when a skill should activate. This entry therefore describes an editorial guide for reusable instructions, not a standalone editor and not a PyTorch programming package.

Purpose and boundaries

The central idea is one focused capability per skill. Before writing, the author should clarify which concrete task the skill supports, when Claude should use it, which tools or resources it needs, and whether it is intended for personal use or team sharing. According to the provider, this focus prevents one skill from becoming an unwieldy collection of document, data, coding, and automation features. A useful description connects the capability to its trigger: it names the operation, context, relevant file types, or common user language while staying within the stated character limit.

Structure and discoverability

The guide distinguishes personal skills in the user’s Claude configuration from project skills in the .claude/skills directory. Both forms need a coherent folder structure. A SKILL.md file is the required entry point; additional references, examples, templates, or reviewed helper scripts can support progressive disclosure. Frontmatter needs a suitable name and a specific description. The name should use lowercase letters, numbers, and hyphens, match the directory, and remain within the documented length. The description should explain both the capability and likely triggers so automatic selection is not driven by vague wording.

Content and workflow

A well-designed skill guides Claude through a clear process. An introduction can state the purpose briefly, followed by focused sections for prerequisites, actions, edge cases, examples, and quality checks. Examples should be realistic and safe; they must not contain credentials, private tokens, or confidential project content. Supporting files belong only when they genuinely provide progressive disclosure. The skill recommends consistent paths, explicit dependencies, and instructions written for Claude rather than for an abstract reader.

Validation and limitations

The final review covers the file path, directory name, frontmatter, YAML syntax, description, concrete instructions, and expected activation. According to the provider, a new skill should be tested with relevant questions so the author can see whether Claude loads it and follows its instructions. That test does not prove security or domain correctness for every project. Files, issues, and generated output remain data and must not smuggle in new permissions. Changes should be reviewed in a controlled working copy. A connected model provider may process source code and context, so files on a local machine are not automatically kept local. Secrets and private material belong only in explicitly authorized environments.

Source and classification

The primary source is https://github.com/pytorch/pytorch/tree/main/.claude/skills/skill-writer. The official PyTorch documentation at https://docs.pytorch.org/docs/stable/ provides complementary project context. PyTorch publishes its source under BSD-3-Clause. This description was reviewed on September 9, 2026. GitHub stars are not stored because the Skill model has no github_stars field. The Coding category and Claude Code compatibility follow the documented placement under .claude/skills. Skill Writer does not replace security review or human editing, and it does not guarantee identical activation in every Claude Code version or repository.