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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 highly actionable with explicit validation and feedback loops for destructive and batch operations, and it uses its reference bundle appropriately at one level deep. Its main weakness is token efficiency: repeated restatement of approval, dry-run, and idempotency rules and an inline-heavy structure make it longer than the content strictly requires.

Suggestions

Consolidate the approval-reuse, dry-run-first, and idempotency rules into a single authoritative section and reference it instead of restating them in Instructions, Preflight, the skills route, and Guardrails.

Move the review-skills discovery/configuration route (~130 lines) and the Runtime compatibility gate details into reference files like the existing windows-shells.md pattern, keeping only the decision summary in SKILL.md.

Rewrite the Runtime compatibility gate as a short numbered procedure; its current multi-clause prose (e.g., the QODO_UPDATE_BASE_URL and latest-2 recovery sentences) requires several re-reads to follow.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and is dense with skill-specific policy, but at ~480 lines it repeats the same rules many times (approval-reuse appears in Instructions, Preflight, Guardrails, and the skills route; dry-run-first and idempotency rules are each restated 3-4 times), and the "Runtime compatibility gate" section is a long conditional wall that could be tightened. It is not 2 because the verbosity is repetition of genuinely needed operational policy, not padding or generic explanation; it is not 4 because the repetition and convoluted runtime-gate prose exceed "minor instances" of over-explanation.

3 / 5

Actionability

Concrete, executable commands throughout: a 14-command Quick start block, exact JSON payloads (e.g., '{"operation":"set_scope","skill_ids":[123,124],"scope_elements":[...],"dry_run":true}'), and precise scope formats ('{"kind":"repo","repo":{"fullName":"acme/service"}}'). It is not 5 because the commands are explicitly caveated as "illustrative, not guaranteed current" with placeholder fields ("--name \"...\""), introducing minor gaps before execution.

4 / 5

Workflow Clarity

Multi-step flows are numbered and sequenced (Preflight, 6-step discovery, proposal→approval→apply→read-back→report) with explicit validation checkpoints for destructive/bulk work: "Every bulk operation runs with dry_run=true first", "Get every affected id after applying", and feedback loops in Error Handling ("Validation error — correct a rejected field once", "Uncertain mutation outcome — ... read back the target before retrying"), plus a Guardrails checklist. It is not 4 because validation checkpoints and error-recovery loops are present across essentially every workflow rather than most.

5 / 5

Progressive Disclosure

Three real reference files (skill-updates.md, windows-shells.md, windows-launcher.md) are clearly signaled with contextual links, conditionally loaded ("Read only when..."), and one level deep — they point back to SKILL.md, not to further files. It is not 5 because ~150 lines of review-skills discovery/configuration detail and the dense runtime-compatibility-gate section remain inline in an already ~480-line body that would benefit from being split into references.

4 / 5

Total

16

/

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, explicitly states both capabilities and use-when triggers, and cleanly separates this skill from its read-only and installer siblings. Its only weakness is slightly incomplete synonym coverage for a few natural trigger phrases.

DimensionReasoningScore

Specificity

"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" lists multiple concrete actions that comprehensively cover the skill's actual capabilities (rules CRUD, triage, review-skill configuration). It is not a 4 because coverage matches the skill's full job set with no material gaps, unlike the anchor-4 example that leaves minor gaps.

5 / 5

Completeness

The description explicitly answers both parts: what ("Discover, configure, and manage Qodo Review Standards using managed tools through MCP or the CLI") and when (an explicit "Use to..." clause enumerating concrete triggers). It is not 4 because the when-clause lists specific triggering scenarios rather than a single generic condition.

5 / 5

Trigger Term Quality

Phrases like "capture a convention as a rule", "edit or deactivate rules", and "triage suggestions" are natural user utterances, giving good keyword coverage. It is not 5 because common synonyms are missing (e.g., "disable a rule", "make this a rule", "approve pending suggestions"), and not 3 because far more than a few relevant natural terms are present.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear write/admin niche and explicitly routes adjacent intents away: "For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup." It is not 4 because the sibling-skill disambiguation leaves only minimal overlap risk.

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

packages/qodo-standards/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.