agentleFS
noelcetanoelceta/content-engine/.claude/skills/write/SKILL.md

write

Skill9 starsChanged 6 days agoMITView on GitHub

Write the article for a slug from its brief and my notes, then run the editor agent on it. Use when I type /write.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use read, hunt 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.
  • MicrosoftSkill

    read

    Read pages from a document. Returns MinerU markdown (preferred) or PyPDF text, with optional page screenshots and sub-image fetching. When markdown is available, a figure_images_meta catalog is included — use the figures parameter to fetch specific sub-image pixels. Triggers include "read page 5", "what does page 12 say", "show me the chart on page 3", "extract pages 3-5".

    Also in 6 projects that use this

  • ninehillsSkill

    hunt

    Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

    Also in 4 projects that use this

  • vltingSkill

    think

    Lightweight plan-to-execution pipeline. Explores codebase, runs council deliberation, presents plan for approval, then executes via /run.

    Also in 7 projects that use this

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 5 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 6 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read briefs/$ARGUMENTS.md, briefs/$ARGUMENTS.data.md, notes/$ARGUMENTS.md (if it exists), site/site.md and site/voice.md.

    line 11
  2. Very specific:

    Write drafts/$ARGUMENTS.md.

    line 12
  3. Very specific:

    When the draft is done, give it to the editor agent: "Review drafts/$ARGUMENTS.md against briefs/$ARGUMENTS.md".

    line 25
  4. Distinctive:

    If the editor suggests new quotes or numbers, check them against the source page before you use them.

    line 26

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

Slug: $ARGUMENTS

  1. Read briefs/$ARGUMENTS.md, briefs/$ARGUMENTS.data.md, notes/$ARGUMENTS.md (if it exists), site/site.md and site/voice.md.
  2. Write drafts/$ARGUMENTS.md. Start with this frontmatter:

    ---
    title: <best title from the brief>
    slug: $ARGUMENTS
    keyword: <main keyword>
    meta_description: <from the brief>
    excerpt: <one or two sentences>
    ---
  3. Follow the outline in the brief, one section at a time. My notes are the most valuable part of the article: use them in my voice, as first-hand experience. Where a question in my notes has no answer, put [ADD: ...] there instead of filling the gap.
  4. When the draft is done, give it to the editor agent: "Review drafts/$ARGUMENTS.md against briefs/$ARGUMENTS.md". Apply every fix it lists unless it would make the article worse; say which ones you skipped and why. If the editor suggests new quotes or numbers, check them against the source page before you use them. Don't trust a quote just because the editor wrote it.
  5. Tell me: word count, how many [ADD and [NEED SOURCE markers are left, and the editor's top 3 problems.

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.