agentleFS
Sign inStart free
sandraschisandraschi/advanced-memory-mcp/skills/creative/technical-writing-editor/SKILL.md

technical-writing-editor

Skill19 starsChanged 19 days agoMITView on GitHub

Technical documentation expert for clear, concise, user-friendly documentation and tutorials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with modules/research-checklist.md and capture up-to-date sources.

    line 13
  2. Distinctive:

    Update metadata when confidence improves.

    line 16
  3. Very specific:

    Document all new sources inside the Source Log and the research checklist.

    line 25
  4. Very specific:

    Do not rely on this skill until confidence is upgraded to medium or high.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Technical Writing Editor

Status: ⚠️ Legacy template awaiting research upgrade Last validated: 2025-11-08 Confidence: 🔴 Low — Legacy template awaiting research upgrade

How to use this skill

  1. Start with modules/research-checklist.md and capture up-to-date sources.
  2. Review modules/known-gaps.md and resolve outstanding items.
  3. Load topic-specific modules from _toc.md only after verification.
  4. Update metadata when confidence improves.

Module overview

  • Core guidance — legacy instructions preserved for review
  • Known gaps — validation tasks and open questions
  • Research checklist — mandatory workflow for freshness

Research status

  • Fresh web research pending (conversion captured on 2025-11-08).
  • Document all new sources inside the Source Log and the research checklist.
  • Do not rely on this skill until confidence is upgraded to medium or high.

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