emend
Skill1 starsChanged 24 days agoApache-2.0View on GitHub
Revise or review prose for clarity and factual precision, using ASD-STE100 for technical text.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-testSkill
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- circleci-job-resultsSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- code-cleanupSkill
- deep-code-cleanupSkill
- doc-updateSkill
- fix-issueSkill
- git-github-workflowSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 23
Do not invent evidence or replace domain terms merely to satisfy a word list.
≈ “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.
Files
Emend
Accept $emend with prose or file targets. Without a target, use changed
prose first, then a document with a concrete clarity problem.
Preserve meaning, evidence, attribution, and domain terms. Remove filler, vague claims, unnecessary intensifiers, and dramatic headings. Use plain verbs and concrete nouns. Do not infer authorship from writing style.
For technical documents, read ASD-STE100 guidance. Apply that standard to technical communication. Preserve a requested creative or nontechnical style. For a full prose review, also use editing patterns.
Preserve quotations, names, titles, identifiers, code, commands, and mandatory legal or regulatory wording unless the task authorizes changing them. Do not invent evidence or replace domain terms merely to satisfy a word list.
For edited files, run the bundled checker from this skill directory:
uv run python scripts/check_asd_ste100.py --document-type procedural PATH
uv run python scripts/check_asd_ste100.py --document-type descriptive PATHChoose the document type for the text. Correct deterministic findings and review advisories in context. Use the manual checklist for technical wording. The checker does not establish formal compliance.
Report the main changes, verification limits, and any claim that still needs evidence. Keep short edits and their responses short.
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
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.