excellence
Skill2 starsChanged 9 months agoMITView on GitHub
Multi-agent document review (visual, pedagogy, proofreading, domain). Use for comprehensive quality check before milestones. Works with any supported file type.
In this repository23 other files it gives its agents.
- compileSkill
- context-statusSkill
- create-documentSkill
- deploySkill
- devils-advocateSkill
- diagramSkill
- doc-reviewSkill
- extract-diagramsSkill
- finishSkill
- google-tasksSkill
- image-searchSkill
- learnSkill
- mindmapSkill
- pedagogy-reviewSkill
- proofreadSkill
- qaSkill
- sec-edgarSkill
- translateSkill
- typstSkill
- validate-bibSkill
- verifySkill
- visual-auditSkill
- waybackSkill
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 12
Run a comprehensive multi-dimensional review.
≈ “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
Excellence Review
Run a comprehensive multi-dimensional review. Multiple agents analyze the file independently, then results are synthesized.
Format Detection
Determine file type from extension:
.tex→ Beamer LaTeX slides.qmd→ Quarto RevealJS slides.typ→ Typst document (slides, docs, guides, CVs).py→ Python script.md→ Markdown
For .typ files, also detect document type from content.
Agent Dispatch by File Type
For .tex files:
| Agent | What It Checks | Report |
| document-auditor | Overflow, font consistency, spacing, images | [FILE]_visual_audit.md |
| pedagogy-reviewer | 13 patterns, narrative, pacing, notation | [FILE]_pedagogy_report.md |
| proofreader | Grammar, typos, consistency, academic quality | [FILE]_report.md |
| diagram-reviewer | Label overlaps, geometric accuracy (only if TikZ present) | [FILE]_tikz_review.md |
| domain-reviewer | Field-specific substance (optional) | [FILE]_substance_review.md |
For .qmd files:
| Agent | What It Checks | Report |
| document-auditor | Overflow, font consistency, spacing, images | [FILE]_visual_audit.md |
| pedagogy-reviewer | 13 patterns, narrative, pacing | [FILE]_pedagogy_report.md |
| proofreader | Grammar, typos, consistency | [FILE]_report.md |
| writing-style-critic | AI tropes across 6 categories | [FILE]_tropes_review.md |
| quality-critic | Adversarial comparison vs .tex (only if sibling exists) | [FILE]_parity_report.md |
For .typ files:
| Agent | What It Checks | Report |
| typst-reviewer | Compilation, smart defaults, component usage, visual routing | [FILE]_typst_review.md |
| document-auditor | Overflow, typography, component fatigue, spacing | [FILE]_visual_audit.md |
| proofreader | Grammar, typos, consistency | [FILE]_report.md |
| writing-style-critic | AI tropes across 6 categories | [FILE]_tropes_review.md |
| pedagogy-reviewer | Narrative, pacing, notation (only if slides detected) | [FILE]_pedagogy_report.md |
For .md files:
| Agent | What It Checks | Report |
| proofreader | Grammar, typos, consistency | [FILE]_report.md |
| writing-style-critic | AI tropes across 6 categories | [FILE]_tropes_review.md |
For .py files:
| Agent | What It Checks | Report |
| general-purpose subagent (Python review brief) | Code quality, style, type safety, patterns | [FILE]_python_review.md |
| domain-reviewer | Field-specific correctness (optional) | [FILE]_substance_review.md |
Steps
- Parse
$ARGUMENTSfor the filename, resolve path - Detect format from extension
- Launch all applicable agents in parallel per dispatch table
- Save each agent's returned report to
quality_reports/at the path in the dispatch table (read-only agents return their report as text instead of writing it), then collect them - Synthesize combined summary
Combined Summary Format
# Excellence Review: [Filename]
## Overall Quality Score: [EXCELLENT / GOOD / NEEDS WORK / POOR]
| Dimension | Agent | Critical | Major | Minor |
|-----------|-------|----------|-------|-------|
| Visual/Layout | [auditor] | N | N | N |
| Content Quality | [reviewer] | N | N | N |
| Proofreading | proofreader | N | N | N |
| [Additional] | [agent] | N | N | N |
### Critical Issues (Immediate Action Required)
### Major Issues (Next Revision)
### Recommended Next StepsQuality Score Rubric
See typst/references/quality-gates.md for the authoritative score rubric and severity definitions.
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.

