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

81%

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

71%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 workflow skill with excellent conditional referencing and strong validation gates for a read-only retrieval flow. Its main weaknesses are token efficiency — the runtime-update policy is run-on prose and several caveats are repeated — and the absence of a sample search-result JSON structure needed to execute the merge and output steps precisely.

Suggestions

Restructure the Runtime compatibility gate as a numbered decision procedure or table, or move the 1.x-to-2.x update-route detail into a reference file; sentences like "test whether QODO_UPDATE_BASE_URL is set; never print its value. If set, stop for the user to resolve the source override" force multiple re-reads.

Add a short example of the `qodo read rules search --json` output (rule `id`, `name`, `severity`, `reference`) so the dedup/merge and output steps can be executed without guessing field names.

State the Windows-shell and rules-reuse guidance once in their authoritative sections instead of repeating them across Execution, Runtime compatibility gate, Quick start, and Search and merge.

DimensionReasoningScore

Conciseness

No tokens are spent on concepts Claude already knows, but sections like the Runtime compatibility gate are run-on policy 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") and Windows-shell/reuse caveats are repeated across Execution, Runtime gate, Quick start, and Search and merge. This matches anchor 3 (mostly efficient but could be tightened) rather than 4, and is not 2 because nearly every sentence carries task-specific information rather than padding.

3 / 5

Actionability

Concrete, copy-paste-ready commands with a filled example query ("qodo read rules search --query "Name: JWT Authentication Endpoint Validation..." --top-k 20 --scopes "/owner/repo/" --json"), a three-line query template, a concrete launcher fallback ("${QODO_HOME:-$HOME/.qodo}/bin/qodo"), a numeric retry threshold ("< 3 rules → re-run it once with a broadened Content line"), and a severity enforcement table. It falls just short of anchor 5 because the returned JSON shape (rule id/name/severity/reference fields) that the merge, dedup, and output steps depend on is never shown.

4 / 5

Workflow Clarity

The sequence is explicitly stated ("First check the reuse condition in Preflight... go directly to Output") with real validation gates and recovery loops ("run `<qodo> --version`... run this FIRST", "Check `isError`, then read `structuredContent`", "Make one approved runtime attempt, then rerun the unadorned version probe"). Not anchor 5 because the step order is scattered across sections (Quick start precedes Preflight, which holds the first logical step) and the update-path loop is hard to track through dense prose; well above anchor 3's implicit checkpoints.

4 / 5

Progressive Disclosure

Three references, all verified to exist, one level deep, each with an explicit conditional read trigger: "read [shell guidance](references/windows-shells.md) before the first call; [launcher recovery](references/windows-launcher.md) only if invocation fails" and "follow the [manual-update procedure](references/skill-updates.md)". Platform-specific detail is appropriately externalized while the core workflow stays in SKILL.md — a clean match for anchor 5.

5 / 5

Total

16

/

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 that clearly and explicitly covers what the skill does, when to trigger it (with quoted natural phrases), and the reuse/refresh policy. Its only weaknesses are a broadly applicable coding-task trigger and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions with scope conditions — "Retrieve and apply Qodo coding rules", "Reuse rules already retrieved for the same workspace, repository, and task scope; refresh when that scope changes" — matching anchor 4 (several specific actions, minor gaps) rather than 5, since behaviors the skill also performs (query construction, merging ranked results, explaining constraints) are absent; clearly above anchor 3's 1-2 actions.

4 / 5

Completeness

Explicitly answers both questions: 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 an additional refresh condition ("refresh when that scope changes"). This matches anchor 5's clear what-and-when with concrete trigger phrases, not 4, because the when-clause is explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Includes natural quoted trigger phrases users would actually say — "get rules", "load qodo rules", "relevant standards" — plus "when starting a concrete coding task". This fits anchor 4 (good coverage, a few natural terms missing): synonyms like "coding standards", "team conventions", or "qodo standards" are absent, keeping it below 5, while the multiple genuine phrases put it above anchor 3.

4 / 5

Distinctiveness Conflict Risk

"Qodo coding rules" carves a clear niche with distinct triggers ("load qodo rules"), but "when starting a concrete coding task" and "relevant standards" are broad enough to overlap with general coding or code-review skills — anchor 4 (mostly distinct, minor overlap risk), not 5's minimal conflict risk; not 3 because the vendor branding keeps it well above generically specific.

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

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