Readability review
Skill jsuvic/agent-profile/fixtures/tabnine-workflow-skills/expected/.agents/skills/readability-review
Review naming, decomposition, control flow, duplication, comments, error-handling clarity, and unnecessary abstraction.From its SKILL.md
npx -y skills add jsuvic/agent-profile --skill readability-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 157 tokens by cl100k_base, as published. Nobody here has run it
Readability Review
Focus
- Names that communicate intent and domain meaning.
- Decomposition, control flow, and error-handling clarity.
- Duplication and comments that obscure rather than explain.
- Unnecessary abstraction or indirection.
Output Discipline
- Lead with prioritized findings and concrete evidence.
- Cite the affected file, symbol, or contract when available.
- Distinguish confirmed defects from risks or missing evidence.
- Do not edit or rewrite the change unless the user asks.
Safety
- Review only; do not run scanners, install tools, or broaden permissions.
- Do not upload source code or read or print secrets.
- Do not contact production systems or external services.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most review quality skills give in 157 tokens
Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07
- Ask questions one at a timein 81 of 1048, across 64 files
- Provide a recommended answer for each questionin 73 of 1048, across 50 files
- Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
- Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
- Interview the user relentlessly about the planin 38 of 1048, across 13 files
- Order findings by severityin 31 of 1048
- Resolve each branch of the decision treein 27 of 1048, across 5 files
- Run a grilling sessionin 26 of 1048, across 5 files
- Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
- Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
- Create documentation files lazilyin 24 of 1048, across 5 files
- Assign severity to every findingin 24 of 1048
Said here and by no other author read
- lead with prioritized findings and concrete evidence
- Cite the affected file, symbol, or contract
- Distinguish confirmed defects from risks
- do not edit or rewrite the change unless the user asks
- review only without running scanners
- do not upload source code
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.