agentleFS
Sign inStart free
kyoo-147kyoo-147/MinimalShip/skills/productivity/writing-for-agents/SKILL.md

writing-for-agents

Skill0 starsChanged 25 days agoMITView on GitHub

Write skills and agent-facing documents that are discoverable, bounded, composable, and safe to follow.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-for-humans, setup-ts-deep-modules and 7 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.
  • J03Fr0stSkill

    writing-for-humans

    Write and revise human-facing prose so it is clear, specific, natural, and faithful to the author's intent and genre. Use for emails, chat messages, articles, reports, documentation, announcements, talks, and other prose when the user asks to draft, diagnose, edit, rewrite, make writing less formulaic or less AI-like, sound more natural or direct, or match a supplied voice. Do not use for agent instructions such as skills or AGENTS.md, code-only work, verbatim transcription, or translation without editorial changes.

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 34 projects that use this

  • openchamberSkill

    clack-cli-patterns

    Use when creating or modifying OpenChamber CLI commands, prompts, terminal output, non-TTY behavior, `--quiet`, or `--json` behavior.

    Also in 3 projects that use this

  • MicrosoftSkill

    cloud-architecture-diagram

    Create, edit, or review Azure and Microsoft ecosystem architecture, GitHub CI/CD, and auth/API diagrams as editable draw.io files; resolve Microsoft and GitHub icons. Use for architecture visualization, diagram critique, or missing icons. Azure DevOps only when explicitly requested. Not for competing-cloud architecture, deployment, live discovery, security certification, or unrelated charts.

    Also in 3 projects that use this

  • openchamberSkill

    drag-to-reorder

    Use when implementing or modifying OpenChamber sortable or drag-to-reorder behavior, especially `@dnd-kit`, touch/mobile interactions, variable-width items, or wrapping layouts.

    Also in 3 projects that use this

  • +4 more from openchamber

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Put trigger conditions in frontmatter descriptions.

    line 8
  2. Very specific:

    Keep SKILL.md focused and under a practical context budget.

    line 9
  3. Distinctive:

    Use imperative steps, but explain the reason behind important constraints.

    line 10
  4. Distinctive:

    Prefer explicit skill calls over brittle relative-file dependencies between skills.

    line 12
  5. Distinctive:

    Never include secrets, copied third-party text, or surprising side effects.

    line 14
  6. Distinctive:

    After editing a skill, validate its metadata, links, examples, and behavior against a few realistic prompts.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 177 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 for Agents

  • Put trigger conditions in frontmatter descriptions.
  • Keep SKILL.md focused and under a practical context budget.
  • Use imperative steps, but explain the reason behind important constraints.
  • Separate user-invoked orchestration from model-invoked reusable discipline.
  • Prefer explicit skill calls over brittle relative-file dependencies between skills.
  • Give every generated artifact a path, schema, and verification rule.
  • Never include secrets, copied third-party text, or surprising side effects.

After editing a skill, validate its metadata, links, examples, and behavior against a few realistic prompts.

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.

Check your setup, free