Writing Skills
ed3dai/ed3d-plugins
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…
Methodology for creating effective skills using TDD principles.
Install Writing Skills
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TechDufus/oh-my-claude writing-skills --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .claude/skills/writing-skills && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .claude/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skillsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TechDufus/oh-my-claude writing-skills --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .agents/skills/writing-skills && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .agents/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TechDufus/oh-my-claude writing-skills --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .cursor/skills/writing-skills && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .cursor/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TechDufus/oh-my-claude.git --path plugins/oh-my-claude/skills/writing-skills--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TechDufus/oh-my-claude writing-skills --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .gemini/skills/writing-skills && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .gemini/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TechDufus/oh-my-claude writing-skillsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .github/skills/writing-skills && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .github/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TechDufus/oh-my-claude --skill writing-skills -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TechDufus/oh-my-claude writing-skills --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/oh-my-claude/skills/writing-skills .opencode/skills/writing-skills && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-skills" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/writing-skills into .opencode/skills/writing-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-skills", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-skills- GitHub stars
- 174
- Token cost
- ~1.3k tokens
- SKILL.md length
- 605 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Methodology for creating effective skills using TDD principles.
- Creating new skills
- SKILL.md covers Core Principle, When to Apply, TDD Mapping and RED-GREEN-REFACTOR for Skills, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Editing existing skills
What it does
Writing Skills is an agent skill from TechDufus/oh-my-claude. Methodology for creating effective skills using TDD principles. Use when creating new skills, editing existing skills, or authoring plugin components. Triggers on: 'create skill', 'write skill', 'new skill', 'skill authoring'.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Skill authoring and Test-driven development. The repository describes itself as: Add ultrawork to any prompt for maximum parallel execution. The licence is MIT.
When your agent uses it
- Creating new skills
- Editing existing skills
- Authoring plugin components
- Skill authoring
Example prompts
- “create skill”
- “write skill”
- “new skill”
- “/writing-skills”
What it can do on your machine
Read from SKILL.md and the folder at commit ede75db. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Skills loads about 1.3k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TechDufus/oh-my-claude at commit ede75db, republished under its MIT licence (© TechDufus). 605 words, ~1,308 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-skills/SKILL.md (or your agent's skills folder).- name
- writing-skills
- description
- Methodology for creating effective skills using TDD principles. Use when creating new skills, editing existing skills, or authoring plugin components. Triggers on: 'create skill', 'write skill', 'new skill', 'skill authoring'.
Writing Skills Skill
TDD applied to process documentation.
Core Principle
Writing skills IS TDD applied to process documentation. If you can't test it breaks without the skill, the skill isn't needed.
When to Apply
- Creating new skills
- Editing existing skills
- Reviewing skill quality
- Authoring plugin components
TDD Mapping
| TDD Concept | Skill Equivalent |
|---|---|
| Test case | Pressure scenario (situation where agent fails without skill) |
| Production code | SKILL.md content |
| Failing test | Agent demonstrably fails the scenario |
| Passing test | Agent handles scenario correctly with skill loaded |
| Refactor | Trim to minimum effective content |
RED-GREEN-REFACTOR for Skills
RED: Identify Failure Scenarios
Identify 3+ pressure scenarios where the agent fails without this skill. Document the failure mode. This is your test suite. If you can't find 3 scenarios, the skill probably isn't needed.
GREEN: Write Minimum Effective Content
Write SKILL.md that addresses every identified failure. Minimum content to pass -- no extras, no nice-to-haves, no "comprehensive guides." Every section must map to at least one pressure scenario.
REFACTOR: Trim Aggressively
Remove anything that doesn't directly address a pressure scenario. Target ~120 lines. If removing a line doesn't weaken any pressure scenario, remove it.
SKILL.md Structure Template
---
name: {short-name}
description: "{Role sentence}. Use when {triggers}. Triggers on: {keywords}."
---
# {Name} Skill
{Tagline}
## When to Apply
## Core Pattern / Framework
## Anti-Rationalization Table (if methodology skill)
## Common Mistakes
## The Bottom LineClaude Search Optimization (CSO)
The description field determines when Claude loads your skill. Get it wrong and the skill never fires.
- Description = "Use when..." triggers ONLY
- NEVER summarize the workflow in the description
- Include trigger keywords that match how users/agents naturally phrase the need
Good: "Use when receiving review comments from code-reviewer agent, PR reviews, or external feedback. Triggers on: 'review feedback', 'address review', 'fix review comments'."
Bad: "A comprehensive guide to handling code review feedback through a structured process"
The bad example describes what the skill contains. The good example describes when to load it.
Skill Types
| Type | Purpose | Example | Line Target |
|---|---|---|---|
| Technique | How to do X | debugger | ~120 lines |
| Pattern | When to use X | receiving-code-review | ~120 lines |
| Methodology | Discipline for X | tdd, verification | ~130 lines |
| Meta | How to create X | writing-skills | ~140 lines |
Anti-Rationalization for Skipping Tests
| Excuse | Counter |
|---|---|
| "The skill is obviously clear" | If it's obvious, you can write 3 failure scenarios in 2 minutes |
| "It's just a reference doc" | Reference docs that don't address failures are shelf-ware |
| "Testing documentation is overkill" | Testing docs IS identifying what problems they solve |
| "I'll test it in practice" | Without defined scenarios, you won't notice when it fails |
Show full SKILL.md (220 more words)Show less
When NOT to Create a Skill
Not everything deserves a skill:
- Information easily found in docs (link to docs instead)
- One-time procedures (just do them)
- Tool-specific configuration (use CLAUDE.md)
- Content under 30 lines (too simple -- put it in CLAUDE.md)
Token Efficiency
Every line must earn its place:
- Technique/pattern skills: ~120 lines
- Methodology skills: ~130 lines
- Meta skills: ~140 lines
The test: "If removing this line doesn't weaken any pressure scenario, remove it."
Avoid:
- Repetitive examples that demonstrate the same point
- "Nice to know" sections that don't prevent failures
- Long prose when a table communicates faster
- Headers with only 1-2 lines of content (merge them)
Frontmatter Rules
Skills use ONLY name and description in frontmatter:
---
name: my-skill
description: "What it does. Use when X. Triggers on: 'keyword1', 'keyword2'."
---No model, tools, or permissionMode. These are not agent definitions.
Common Mistakes
| Mistake | Why It's Wrong | Do This Instead |
|---|---|---|
| Writing without pressure scenarios | No way to verify the skill works | RED phase first -- always |
| Summarizing workflow in description | Claude can't match it to triggers | Use "Use when..." pattern |
| Including everything you know | Bloats context, dilutes signal | Only what prevents identified failures |
| Skipping refactor phase | Skills grow stale and verbose | Trim after every edit |
| Copying another skill's structure | Different types need different shapes | Match structure to skill type |
The Bottom Line
A skill without tested pressure scenarios is documentation. Documentation without a problem to solve is noise.
© TechDufus, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/oh-my-claude/skills/writing-skills of TechDufus/oh-my-claude.
Open the folder on GitHubat commit ede75db
Compare with similar skills
Writing Skills next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Skills this skillTechDufus/oh-my-claude | 174 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Writing Skillsed3dai/ed3d-plugins | 250 | 1 repos | ~1.3k | Automated safety check: Pass | None | |
| Writing SkillsjnMetaCode/superpowers-zh | 8.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Writing Skillssandgardenhq/sgai | 137 | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Skill Authoringathola/claude-night-market | 341 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Skillsfarm-fe/farm | 5.6k | 38 repos | ~5.6k | Automated safety check: Pass | MIT |
Similar skills
Writing Skills
jnMetaCode/superpowers-zh
当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用
Writing Skills
sandgardenhq/sgai
TDD for process documentation - test with subagents before writing, iterate until bulletproof.
Skill Authoring
athola/claude-night-market
Guide creating Claude Code skills with TDD and persuasion principles.
Writing Skills
farm-fe/farm
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment
Skill Writing
millionco/expect
Write and improve agent skills (SKILL.md files). An agent skill from millionco/expect.
More from TechDufus/oh-my-claude
All 12 skills in this repoDebugger
TechDufus/oh-my-claude
Systematic debugging methodology for diagnosing failures and root cause analysis.
Oh My Claude Runtime
TechDufus/oh-my-claude
A skill your agent uses when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration.
PR Creation
TechDufus/oh-my-claude
MUST be used when creating pull requests. An agent skill from TechDufus/oh-my-claude.
Ralph Loop Init
TechDufus/oh-my-claude
Transform approved plans into ralph loop infrastructure. An agent skill from TechDufus/oh-my-claude.
Ralph Plan
TechDufus/oh-my-claude
Structured PRD generation with interview, research, and approval workflow.
Init Deep
TechDufus/oh-my-claude
Initialize or migrate to nested CLAUDE.md structure for progressive disclosure.
Related
Categories
Questions about Writing Skills
What does Writing Skills do?
Methodology for creating effective skills using TDD principles. Writing Skills is an agent skill from TechDufus/oh-my-claude. Methodology for creating effective skills using TDD principles.
When should I use Writing Skills?
Writing Skills fits situations like: creating new skills; editing existing skills; authoring plugin components; skill authoring.
How do I install Writing Skills in Claude Code?
Run `npx skills add TechDufus/oh-my-claude --skill writing-skills -a claude-code`. Or copy the skill folder (plugins/oh-my-claude/skills/writing-skills in TechDufus/oh-my-claude) into .claude/skills/writing-skills in your project. Claude Code loads it when a task matches its description.
How do I install Writing Skills in Codex?
Run `npx skills add TechDufus/oh-my-claude --skill writing-skills -a codex`. Or copy the skill folder (plugins/oh-my-claude/skills/writing-skills in TechDufus/oh-my-claude) into .agents/skills/writing-skills in your project. Codex loads it when a task matches its description.
Can I use Writing Skills in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TechDufus/oh-my-claude --skill writing-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-skills, .gemini/skills/writing-skills, .github/skills/writing-skills and .opencode/skills/writing-skills in your project.
What does Writing Skills need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Skills is instructions for the agent only.
Does Writing Skills access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Skills safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Skills use?
Writing Skills is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Skills use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Skills?
Skills that share tags, products or a category with Writing Skills: Writing Skills (ed3dai/ed3d-plugins, 250 stars), Writing Skills (jnMetaCode/superpowers-zh, 8.3k stars), Writing Skills (sandgardenhq/sgai, 137 stars) and Skill Authoring (athola/claude-night-market, 341 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Skills?
TechDufus (a GitHub user) maintains it in TechDufus/oh-my-claude, which has 174 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 13, 2026.
Source: TechDufus/oh-my-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.