agentleFS
iadr-deviadr-dev/colab/skills/writing-skills/SKILL.md

writing-skills

Skill2 starsChanged 7 months agoMITView on GitHub

Meta-skill for creating new skills in oh-my-colab format. Use when RETRO identifies a pattern worth formalizing. Ensures correct folder structure, 200-line discipline, proper frontmatter, and token-efficient design.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • aaddrickSkill

    writing-agents

    Use when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool

    Also in 3 projects that use this

  • frankxaiSkill

    defense-in-depth

    Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after RETRO identifies a pattern worth formalizing as a reusable skill.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 180 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing Skills

Use after RETRO identifies a pattern worth formalizing as a reusable skill.

Skill Folder Structure

skills/{skill-name}/
├── SKILL.md              ← core instructions, ≤200 lines
├── references/           ← detailed docs, loaded on demand
│   └── *.md
├── scripts/              ← executable tools, only output enters context
│   └── *.sh / *.py
└── assets/               ← templates, blank forms
    └── *.md

Required SKILL.md Frontmatter

---
name: skill-name              # kebab-case, ≤64 chars, becomes /skill-name
description: >                # ≤200 chars — ONLY thing read before triggering
  When this skill activates. What it produces. Key trigger words or contexts.
  Make this searchable. Be specific about when to use vs not use.
allowed-tools: Read Write Bash  # optional — restrict available tools
---

The 200-Line Rule

SKILL.md must stay under 200 lines. If content exceeds it:

  1. Identify the long section (usually examples or detailed reference)
  2. Move it to references/{descriptive-name}.md
  3. Replace with: See references/{name}.md for [brief description]

What stays in SKILL.md: the protocol (what to do, in what order) What goes to references/: examples, full checklists, edge cases, templates What goes to scripts/: validation, detection, generation logic What goes to assets/: blank templates the user copies

Writing Good Descriptions

The description is ALL the agent reads before deciding to load this skill.

Bad: "A skill for debugging code." Good: "Hypothesis-driven debugging. Triggers on debug, error, broken, failing. Forces explicit hypothesis before fix. Prevents guess-and-check debugging."

Promoting from Draft

Draft skills go to .ohc/skills/{name}.md (single file, informal). Promoted skills go to skills/{name}/SKILL.md (full folder structure).

ohc skill draft {name}    # scaffold folder + template
ohc skill promote {name}  # move draft to skills/ folder

See references/skill-spec.md for the complete Anthropic skill specification. See references/frontmatter-guide.md for all frontmatter fields.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.