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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./codex-packages/qodo-standards/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.

The skill delivers a concrete, well-validated retrieval workflow with executable commands and a clean reference bundle, and it correctly treats empty results and error paths as first-class outcomes. Its main weaknesses are token efficiency — the runtime/update edge-case material is dense run-on prose that belongs in a reference file — and presentation of the sequence, which is scattered across sections that don't match execution order.

Suggestions

Move the Runtime compatibility gate's update/recovery detail (QODO_UPDATE_BASE_URL handling, 1.x-to-2.x migration routes, checksum-pinned installer) into a reference file like the Windows guides, keeping only the version probe and minimum-version statement in SKILL.md.

Rewrite the multi-clause run-on sentences (e.g., the runtime gate and update-notice paragraphs) as short imperative steps or a numbered checklist, matching the already-effective style of the Preflight section.

Reorder sections to match execution order (Preflight → Quick start → queries → search/merge → output/apply) with edge-case sections (update notice, sandbox diagnostic) after the main path, and add a one-line concrete MCP example call with query/top_k/scopes arguments.

DimensionReasoningScore

Conciseness

The core retrieval sections ("Write the queries", "Search and merge") are tight and operational with no padding of known concepts, but the ~20-line "Runtime compatibility gate" is run-on prose ("Only when the runtime needs an update, before any update check/change, test whether QODO_UPDATE_BASE_URL is set; never print its value...") that should be tightened or offloaded, and time-sensitive version stamps ("--skill-version 1.1.8", "2.0.0 or newer") are embedded in Quick start rather than isolated. Not 2 because almost every sentence carries operational instruction rather than unnecessary explanation.

3 / 5

Actionability

Quick start gives copy-paste CLI commands ("qodo read rules search --query ... --top-k 20 --scopes ... --json") with a full literal example query, the query block format is fully specified with a default cross-cutting query, and the severity table maps to concrete enforcement. Not 5 because the MCP path is described in prose without a concrete example call and the "$TOPIC_QUERY"/"$SCOPE" variables in the merge examples are never bound to values.

4 / 5

Workflow Clarity

A clear sequence exists (Preflight reuse check → auth/catalog → repo scope → queries → search/merge → output/apply) with explicit validation checkpoints and error-recovery loops: unadorned "--version" probe first, MCP "isError" check, whoami, catalog refresh-and-retry, low-return fallback ("< 3 rules → re-run it once with a broadened Content line"), empty-result and rate-limit handling. The operation is read-only, so the destructive-cap does not apply. Not 5 because section order diverges from execution order (update-notice and runtime gate appear before Preflight) and the dense prose makes the sequence harder to follow than a numbered checklist.

4 / 5

Progressive Disclosure

All three bundle files exist (references/skill-updates.md, windows-shells.md, windows-launcher.md), are one level deep with no nested doc references, and each is clearly signaled with a read condition ("read ... before the first call", "only if invocation fails", "For user-requested updates"). Not 5 because the runtime-update/recovery procedure is inlined in SKILL.md as dense prose when it parallels exactly the kind of edge-case content already offloaded to references, leaving the main file longer than an overview needs to be.

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: it explicitly states what the skill does and when to use it, with quoted natural trigger phrases and a clearly branded niche. The only weaknesses are a slightly generic "apply" action and a few missing synonyms for the trigger terms.

DimensionReasoningScore

Specificity

"Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review" plus "Reuse rules already retrieved... refresh when that scope changes" names the domain and several concrete actions with their objects. Not 5 because "apply" and "reuse" remain generic verbs without the concrete sub-actions (search, merge, explain) that full coverage would list; not 3 because more than 1-2 specific actions are given.

4 / 5

Completeness

Both questions are answered explicitly: what — "Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review"; when — "Use on 'get rules', 'load qodo rules', or 'relevant standards' and when starting a concrete coding task", with concrete trigger phrases exactly as the anchor-5 example does. Scope-reuse conditions add precision without diluting either answer.

5 / 5

Trigger Term Quality

Explicit natural trigger phrases "get rules", "load qodo rules", "relevant standards" alongside "when starting a concrete coding task" give good keyword coverage. Not 5 because common synonyms users would say ("coding standards", "team conventions", "show me the rules") are missing; not 3 because multiple natural phrases and task-type keywords (implementation, planning, refactoring, code review) are present.

4 / 5

Distinctiveness Conflict Risk

The Qodo brand name and tool-specific triggers ("load qodo rules") create a clear niche with distinct triggers. Not 5 because the broad trigger "when starting a concrete coding task" and the generic phrase "relevant standards" create minor overlap risk with general coding-standards or linting skills; not 3 because the overlap is confined to closely related skills, not many.

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

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