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

88%

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

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

Highly actionable content with exemplary validation checkpoints and feedback loops for destructive and bulk operations, supported by a clean one-level-deep reference bundle. Its main weakness is token efficiency: repeated guardrail statements, dense run-on conditionals, and version-sensitive detail in the main flow all inflate the budget.

Suggestions

Move the runtime-update and 1.x-to-2.x recovery detail out of the main flow into a reference file (like references/skill-updates.md), keeping only the unadorned version probe and minimum-version check inline.

State the approval, dry-run, idempotency, and read-back rules once in Guardrails and reference them from the individual sections instead of restating them in Instructions, Preflight, and each workflow.

Split the run-on paragraphs (especially 'Runtime compatibility gate' and the discovery-status step) into short numbered imperative steps so each condition is scannable.

DimensionReasoningScore

Conciseness

The body is domain-specific rather than tutorial padding, but is noticeably verbose and could be tightened: approval/dry-run/idempotency rules are restated across Instructions, Preflight, and Guardrails; the 'Runtime compatibility gate' is a single tangled run-on paragraph of nested conditionals; and version-sensitive detail (CLI 2.0.0, 1.x recovery routes) sits in the main flow instead of a reference or deprecated section.

3 / 5

Actionability

Fully executable guidance throughout: complete qodo commands with flags and JSON payloads in Quick start and the review-skills examples, with the use of placeholders and live-schema delegation explicitly justified ('The commands above are illustrative, not guaranteed current', 'Verify names and JSON arguments in the connected catalog').

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: dry-run → show matched count → confirm → apply → read back every affected id → reconcile bulk counts, plus 'If the preview differs from the proposal, resolve it before writing' and read-back-before-retry on uncertain mutations; destructive/bulk operations all carry validation, so no cap applies.

5 / 5

Progressive Disclosure

The three reference files (skill-updates.md, windows-shells.md, windows-launcher.md) are real, one level deep, and clearly signaled with conditional read triggers; however the main file inlines large advanced flows (the runtime gate, the full review-skills discovery/configuration route) that would be better split into references.

4 / 5

Total

17

/

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: concrete and comprehensive about capabilities, with an explicit 'Use to' trigger clause and clear boundary routing to sibling skills. The only weakness is that a few natural user phrasings and synonyms are not covered.

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' — comprehensively covering the skill's admin surface with no meaningful gaps.

5 / 5

Completeness

It explicitly answers both 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 trigger scenarios), matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('capture a convention as a rule', 'edit or deactivate rules', 'triage suggestions', 'skills/plugin repository'), but a few natural synonyms such as 'approve suggestions' or 'enforce a convention' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear write/admin niche and explicitly routes adjacent use cases away ('For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup'), minimizing wrong-skill triggering.

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

antigravity-plugins/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.