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

86%

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

75%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.

A highly actionable, well-validated administrative skill: exact commands, dry-run/preview gates, read-back verification, and explicit error-handling cover the destructive and batch operations thoroughly. Its weaknesses are redundancy — approval, dry-run, and idempotency rules restated across multiple sections — and a monolithic 490-line body that keeps specialized material (runtime recovery, Windows details) inline instead of in its otherwise well-managed references.

Suggestions

Consolidate the approval-reuse, dry-run-first, and idempotency rules (currently restated in Instructions, the review-skills sections, and Guardrails) into the single Guardrails section and cross-reference it once, cutting significant length without losing any rule.

Move the runtime compatibility gate's 1.x-to-2.x recovery-route detail into a dedicated reference file (parallel to references/skill-updates.md), keeping only the unadorned version probe, the minimum-version requirement, and the stop conditions in the body.

Restructure the runtime-gate prose into a short numbered decision checklist (probe → needs update? → source override set? → select verified route → re-probe) so the nested conditions are scannable instead of buried in a single paragraph.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but it states the same rules repeatedly: approval-reuse appears in Instructions, "Build one reviewable proposal", "Preview and apply", and Guardrails; dry-run-first appears in the rules jobs, the review-skills sections, and Guardrails; idempotency rules appear in both the MCP section and discovery step 4. The runtime compatibility gate is a long tangled prose paragraph that could be substantially tightened. This fits "mostly efficient but includes some unnecessary explanation or could be tightened" rather than anchor 4's minor instances.

3 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste-ready quick-start command block, exact `--args` JSON payloads with realistic values (rule-id 123, /owner/repo/ scopes), dry-run/apply command pairs for bulk operations, concrete rule-drafting defaults (severity tiers, category fallback list), and specific error responses per failure type. Specific examples cover the common cases, matching the fully executable anchor.

5 / 5

Workflow Clarity

Each sub-flow is clearly sequenced with explicit validation checkpoints and feedback loops (numbered Preflight, six-step discovery with polling and read-back, preview → approve → apply → read-back, "If the preview differs from the proposal, resolve it before writing", retry-at-most-once rules) — well above the destructive/batch validation cap. It falls short of anchor 5 because the runtime compatibility gate packs nested conditionals into impenetrable prose, and a full task sequence must be assembled from several interleaved sections (MCP/CLI path, preflight, per-job flows).

4 / 5

Progressive Disclosure

All three references exist, are clearly signaled inline ([manual-update procedure](references/skill-updates.md), [shell guidance](references/windows-shells.md), [launcher recovery](references/windows-launcher.md)), and are one level deep — they point back to SKILL.md rather than to further files. However, the 490-line body keeps substantial specialized material inline (the ~25-line runtime recovery matrix, Windows specifics, the full discovery route) that could live in references, so content is not split as cleanly as anchor 5 requires.

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.

A strong description that comprehensively and specifically enumerates the skill's administrative capabilities, gives explicit "Use to..." trigger guidance, and cleanly differentiates itself from sibling Qodo skills. The only gap is modest synonym coverage of natural user phrasings for rule creation and suggestion triage.

DimensionReasoningScore

Specificity

The description enumerates concrete actions covering every job the skill performs: "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". The generic opener "Discover, configure, and manage" is immediately grounded by this comprehensive, specific list, matching the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

It explicitly answers both questions: what ("Discover, configure, and manage Qodo Review Standards using managed tools through MCP or the CLI") and when ("Use to set up a skills/plugin repository for reviews, ... capture a convention as a rule, edit or deactivate rules, or triage suggestions") with concrete trigger phrases. This matches the anchor for clearly and explicitly answering both what and when.

5 / 5

Trigger Term Quality

Natural phrases are present ("capture a convention as a rule", "edit or deactivate rules", "triage suggestions", "map review skills to target repositories") but a few common user phrasings are missing, such as "add a rule", "enforce a convention", or "approve pending suggestions". This is good keyword coverage with a few natural terms missing — above anchor 3's partial coverage, below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (administering Qodo Review Standards) and it explicitly routes neighboring use cases to sibling skills: "For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup". Clear niche with distinct triggers and minimal conflict 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

kiro-power-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.