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.

Operationally excellent: concrete, executable commands on both MCP and CLI paths, tightly validated workflows with dry-run/read-back feedback loops, and correctly structured one-level-deep references. The main liability is token efficiency — heavy repetition of the same approval, idempotency, and refresh gates across many sections makes the body noticeably verbose.

Suggestions

Consolidate the approval/dry-run/idempotency rules, currently restated in Instructions, Preflight, Guardrails, 'Build one reviewable proposal', and 'Preview and apply', into a single 'Write gates' section referenced once from each flow.

Move the runtime compatibility gate's upgrade-recovery detail (QODO_UPDATE_BASE_URL checks, latest-2 route, checksum-pinned installer fallback) into a reference file like the Windows guides, keeping only the unadorned version probe and minimum-version statement in SKILL.md.

Trim repeated caveats ('do not switch to a different CLI identity or tenant', 'refresh once and recheck') to a single statement each, and tighten long multi-clause sentences such as the sandbox auth diagnostic paragraph.

DimensionReasoningScore

Conciseness

At ~475 lines the body restates the same operational gates across sections — approval-reuse rules appear in Instructions, Preflight, Guardrails, 'Build one reviewable proposal', and 'Preview and apply'; catalog-refresh-once and never-switch-identity rules each repeat three or more times — and the runtime compatibility gate is ~25 lines of tangled conditional prose. This is 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient 3 anchor, and time-sensitive version pins ('2.0.0 or newer', '--skill-version 1.0.9') sit outside any deprecated section.

2 / 5

Actionability

The skill provides copy-paste-ready commands for both paths — 'qodo rules create --name "..." --category "..." --severity warning ... --scopes "/owner/repo/" --json', 'qodo review-skills bulk --args '{"operation":"set_scope",...,"dry_run":true}'' — plus the exact fallback invocation '"${QODO_HOME:-$HOME/.qodo}/bin/qodo"', specific error codes ('MT-RATE-LIMITED'), and operation tables. Examples cover the common cases across create, edit, scope, triage, discovery, and configuration, matching the fully-executable 5 anchor.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced (preflight → resolve target → dry-run preview → confirm → mutate once → read back and report) with validation checkpoints throughout: dry-run matched-count inspection before every bulk write, read-back comparison of every affected id, and a bounded retry loop for uncertain outcomes ('read back the target before retrying... Retry at most once'). The destructive/batch cap does not apply because irreversible operations like 'reject' require dry-run, a matched-count display, and a summary of what will be permanently lost.

5 / 5

Progressive Disclosure

All three bundle files (references/skill-updates.md, references/windows-shells.md, references/windows-launcher.md) are real, well-signaled, conditionally loaded ('Read only when...'), and exactly one level deep. It misses the 5 anchor because the SKILL.md body itself inlines substantial flows — the runtime upgrade recovery detail and the multi-page source-repository discovery procedure — that would belong in reference files like the Windows guides.

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: it states concrete capabilities across the full admin surface, gives explicit 'Use to...' trigger guidance, and actively disambiguates sibling skills. The only weakness is modest synonym coverage of natural user phrasings.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'capture a convention as a rule, edit or deactivate rules, or triage suggestions', 'map review skills to target repositories', 'change skill scope or rules/steering mode' — and names both mechanisms (MCP or CLI), comprehensively covering the admin domain. It exceeds the 4 anchor because coverage spans discovery, configuration, rule lifecycle, and triage with no significant gaps.

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, map review skills to target repositories, capture a convention as a rule, edit or deactivate rules, or triage suggestions'). Both are concrete with explicit trigger phrases, matching the 5 anchor rather than the merely-present 'when' of the 4 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'capture a convention as a rule', 'edit or deactivate rules', 'triage suggestions', 'set up a skills/plugin repository for reviews' mirror phrasings users would actually say. It falls short of the 5 anchor because common variations like 'turn off that rule', 'pending suggestions', or 'make this a rule' are absent.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear write/admin niche and explicitly routes the two nearest conflicts elsewhere: 'For reading and applying rules use qodo-get-rules; installing local coding-agent skills uses qodo-setup.' This is a distinct trigger set with minimal conflict risk, matching the 5 anchor.

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

codex-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.