agentleFS
Sign inStart free
toonoobytoonooby/ste100-plugin/skills/ste-rewrite/SKILL.md

ste-rewrite

Skill0 starsChanged 41 days agoMITView on GitHub

Rewrite a text, or your previous reply, in ASD-STE100 Simplified Technical English at a given compliance level (10-100). Use when the user asks to rewrite, simplify, or convert text into STE or STE100.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Use the ste100 skill for the rules of each level.

    line 11
  2. Distinctive:

    Keep every fact, caveat, uncertainty, and edge case.

    line 12
  3. Distinctive:

    After the rewrite, give a short table: rule broken in the original, count, and an example fix.

    line 13

≈ “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

Rewrite text in ASD-STE100 Simplified Technical English.

  1. The level is the first number (10-100) the user gives. If there is none, use the active level from the ste100 context in this turn, or 70 if there is none.
  2. The text to rewrite is the rest of the request. If there is no text, rewrite your previous reply.
  3. Use the ste100 skill for the rules of each level.
  4. Keep every fact, caveat, uncertainty, and edge case. Accuracy has priority over compliance. Mark each rule you break with ‡ and explain it in a "STE deviations:" list at the end.
  5. After the rewrite, give a short table: rule broken in the original, count, and an example fix.

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