document-quality-review
Skill0 starsChanged 9 months agoNo licenceView on GitHub
Review documents for structural clarity, logical flow, vocabulary consistency, and argumentative rigour. Use when asked to check document structure, improve flow, trace vocabulary, audit section transitions, or critique how a document is written (as opposed to whether the solution it proposes is sound). Also use when iteratively drafting a proposal — checking each revision for structural improvements, clearer argumentation, and tighter flow as the document evolves. Triggers include "check the flow," "improve the structure," "is this well-written," "critique the document quality," "review my draft," or when a user shares a multi-section document and asks specifically about clarity, readability, or structural issues. Do NOT use when the user wants to evaluate whether a proposed solution actually solves a business problem — use the proposal-review skill for that.
In this repository5 other files it gives its agents.
- experiment-readoutSkill
- leadership-communicationSkill
- mbr-reviewSkill
- proposal-reviewSkill
- thesis-writingSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.