CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-manage-standards

Discover, configure, and manage Qodo Review Standards using managed tools through MCP or the CLI. Use to set up a skills/plugin repository for reviews, map review skills to target repositories, change skill scope or rules/steering mode, capture a convention as a rule, edit or deactivate rules, or triage suggestions. For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a thorough, actionable administration guide with strong validation culture (dry-runs, read-backs, idempotency keys, explicit approval gates) and a well-structured reference bundle. Its main costs are length and repetition — the same safety rules are restated in multiple sections and niche recovery detail is inlined — which hurt token efficiency and keep the overall flow from being trivially navigable.

Suggestions

Consolidate the approval/dry-run/idempotency rules, currently restated in Instructions, Preflight, Preview-and-apply, and Guardrails, into one canonical section that the other sections reference.

Move the runtime compatibility gate (niche 1.x-recovery detail) and possibly the multi-step review-skills discovery flow into references/ files, matching the existing windows-*.md offload pattern.

Rewrite dense multi-clause paragraphs (e.g. the runtime gate and preflight auth steps) as short imperative bullets to reduce token cost and improve scanability.

DimensionReasoningScore

Conciseness

The ~4,800-word body avoids beginner-concept padding, but approval/dry-run/idempotency rules are restated across Instructions, Preflight, Preview-and-apply, and Guardrails, and the runtime compatibility gate is dense compound-sentence prose that could be significantly tightened. This is more than the 'minor instances' of the level-4 anchor, though not the unnecessary concept explanations of level 2.

3 / 5

Actionability

Concrete, mostly executable guidance throughout: a quick-start CLI block, exact JSON argument examples, a bulk-operation reversibility table, and catalog-verification commands. Minor gaps remain — '"…"' placeholders for user data and commands the skill itself flags as 'illustrative, not guaranteed current'.

4 / 5

Workflow Clarity

An explicit master sequence ('preserve update notices, verify the live schema, resolve the target, preview destructive or bulk work, obtain confirmation, mutate once, and verify the result') is present with real validation checkpoints and feedback loops (dry-run → matched counts → confirm; read-back before retry; correct-once on validation error), so the destructive/batch cap does not apply. Held below 5 because no consolidated numbered flow exists for the common path — the reader must assemble it from Instructions, Preflight, the four jobs, and Guardrails across heavy MCP/CLI branching.

4 / 5

Progressive Disclosure

Three real, well-signaled, one-level-deep references (skill-updates.md, windows-shells.md, windows-launcher.md) each carry a clear 'read when' trigger and correctly offload niche detail. However, long niche sections — the runtime compatibility gate and the review-skills discovery flow — are inlined in SKILL.md where they could be separate reference files, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-disambiguated: it enumerates concrete administrative actions, gives an explicit 'Use to…' trigger clause, and cleanly separates itself from sibling Qodo skills. Its only weakness is trigger-term coverage that misses a few natural phrasings users might use.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'set up a skills/plugin repository for reviews, map review skills to target repositories, change skill scope or rules/steering mode, capture a convention as a rule, edit or deactivate rules, or triage suggestions' — covering the full admin lifecycle (create, edit, lifecycle/scope, triage) rather than several actions with gaps.

5 / 5

Completeness

Both 'what' (administer Review Standards: capture conventions as rules, edit, re-scope, triage, configure review skills) and 'when' (explicit 'Use to…' clause enumerating concrete triggers) are clearly and explicitly answered, with additional boundary routing to sibling skills for reading and installing.

5 / 5

Trigger Term Quality

Natural trigger phrasings users would actually say are present ('capture a convention as a rule', 'edit or deactivate rules', 'triage suggestions', 'map review skills to target repositories'), but a few natural synonyms are missing (e.g. 'approve suggestions', 'make this a rule', 'disable a rule'). Coverage is good but not comprehensive, fitting the 'a few natural terms missing' anchor rather than the synonym-complete anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche — write-side administration of Qodo Review Standards — with explicit disambiguation ('For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup'), giving minimal conflict risk with related skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

qodo-ai/qodo-skills

Path

skills/qodo-manage-standards/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.