CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-get-rules

Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review. Use on "get rules", "load qodo rules", or "relevant standards" and when starting a concrete coding task. Reuse rules already retrieved for the same workspace, repository, and task scope; refresh when that scope changes.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/qodo-get-rules/SKILL.md
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.

A dense, highly actionable procedural skill with real commands, a worked example query, explicit error-recovery loops, and well-managed one-level references. Its main weakness is verbosity: the runtime-compatibility and update-policy prose is tortuous conditional text that would be tighter and better placed in a reference file.

Suggestions

Move the deployment-approved 1.x→2.x upgrade-route policy (the long 'Runtime compatibility gate' paragraphs) into a dedicated reference file like references/runtime-updates.md, keeping only the version-probe command and the stop conditions inline.

Convert the run-on conditional sentences in Preflight step 2 and the update-notice section into short bulleted decision rules (condition → action) to cut token cost without losing constraints.

Add one worked example of the MCP `rules-search` call with its JSON arguments, since the Quick start currently illustrates only the CLI path.

DimensionReasoningScore

Conciseness

Every sentence carries a distinct constraint and it assumes Claude's competence, but sections like "Runtime compatibility gate" are noticeably verbose run-on policy prose ("This exception covers only deployment-approved 1.x to stable 2.x; it does not authorize other major migrations...") that could be tightened or moved to a reference file. Mostly efficient with clear room to trim, matching the 3 anchor better than the padded 2 or the lean 5.

3 / 5

Actionability

The Quick start gives copy-paste-ready commands (`qodo --version`, `qodo read whoami --json --skill ...`, a fully worked multi-line `rules search` query with `--top-k 20 --json`), plus concrete scope-parsing examples (`git@host:a/b` → `a/b`). Minor gaps keep it below 5: the MCP path has no worked example call, and some guidance (severity table application, output pattern) is instructive rather than executable.

4 / 5

Workflow Clarity

A clear sequence exists — Preflight (reuse → auth/catalog → repo scope) → write queries → search and merge → output and apply — with explicit checkpoints (unadorned version probe first, check `isError`, `No tool catalog cached` refresh-once-and-retry) and feedback loops (broadened low-return re-query, re-probe after update). Below 5 because the steps are spread across many interleaved sections with forward/backward cross-references that make the overall order harder to follow.

4 / 5

Progressive Disclosure

All three bundle files (references/skill-updates.md, windows-shells.md, windows-launcher.md) are real, one level deep, and clearly signaled with conditional load triggers ("only if invocation fails", "before the first call"). Good structure overall, though the long inline runtime-update policy in the main body is content that arguably belongs in a reference, matching the 4 anchor's "minor organization gaps".

4 / 5

Total

15

/

20

Passed

Description

83%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 actions, explicit reuse/refresh scope behavior, and naturally phrased quoted triggers that answer both what and when. Its only weaknesses are a broad coding-task trigger clause and a few missing synonymous trigger terms.

DimensionReasoningScore

Specificity

Names the domain ("Qodo coding rules") and several concrete actions — "Retrieve and apply" plus "Reuse rules already retrieved... refresh when that scope changes" — across four stated task contexts (implementation, planning, refactoring, code review). Not a comprehensive multi-action list like the 5 anchor, but clearly more than the 1-2 minimal actions of the 3 anchor.

4 / 5

Completeness

Explicitly answers both: what ("Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review") and when ("Use on 'get rules', 'load qodo rules', or 'relevant standards' and when starting a concrete coding task") with concrete trigger phrases — a direct match for the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would say — "get rules", "load qodo rules", "relevant standards" — plus "when starting a concrete coding task". Good coverage, but common variations like "coding standards" or "qodo standards" are missing, so it falls short of the comprehensive-synonyms 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Qodo" and "load qodo rules" carve out a clear niche with distinct triggers, but the broad "when starting a concrete coding task" clause overlaps with general coding-workflow skills, keeping it at "mostly distinct; minor overlap risk" rather than the minimal-conflict 5 anchor.

4 / 5

Total

17

/

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-get-rules/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.