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

80%

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

Fix and improve this skill with Tessl

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

A well-structured, highly actionable skill body with a clearly sequenced retrieval workflow, abundant validation checkpoints, error-recovery loops, and correctly resolvable one-level-deep references. The main cost is the convoluted, over-long runtime compatibility/update section, which drags conciseness down and would be better split into a reference file.

Suggestions

Move the runtime-update routes, channel policy, and checksum-pinned installer details out of the 'Runtime compatibility gate' section into a reference file (e.g., references/runtime-updates.md), keeping only the version probe and stop conditions inline — this would tighten the body substantially.

Add one concrete example rules-search call for the MCP path (JSON arguments with query/top_k/scopes) to mirror the copy-paste quality of the CLI Quick start.

Trim the update-policy prose (e.g., 'reuse covering runtime-update authorization or ask once before changing the installation') into shorter, imperative sentences; the current phrasing requires multiple re-reads.

DimensionReasoningScore

Conciseness

The body is dense with task-specific operational guidance and avoids teaching concepts Claude already knows, but sections like the ~25-line 'Runtime compatibility gate' ("Choose one deployment-approved upgrade route, explain it, and reuse covering runtime-update authorization or ask once before changing the installation") are convoluted and could be tightened or offloaded to a reference file. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, which requires only minor trims.

3 / 5

Actionability

The CLI path is copy-paste ready with exact flags ("qodo read rules search --query ... --top-k 20 --scopes /owner/repo/ --json"), a verbatim default cross-cutting query, and a concrete scope-parsing recipe. It stops short of 5 because the MCP path is described only abstractly ("query, top_k, optional scopes array") with no concrete example call, and the whoami command embeds skill-version stamps users cannot verify.

4 / 5

Workflow Clarity

The pipeline is explicitly sequenced (Preflight reuse check → auth/catalog → repo scope → write queries → search and merge → output, then apply) with explicit validation steps (unadorned "--version" probe first, "Check isError", whoami check) and feedback loops for error recovery (broaden the Content line and re-run on <3 results, one catalog refresh and schema recheck, rerun the version probe after an update attempt). This matches the top anchor including its recovery-loop requirements; the operation is read-only, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

All three referenced files (references/skill-updates.md, references/windows-shells.md, references/windows-launcher.md) exist, are one level deep with no nested references, and are clearly signaled with conditional load conditions ("only if invocation fails", "before the first call"). It does not reach 5 because the runtime-update policy prose is inlined in SKILL.md where the established pattern of a dedicated reference file would fit, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

78%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 explicitly covers what the skill does and when to use it, with natural quoted trigger phrases and a clear branded niche. Its main weaknesses are limited enumeration of concrete actions and a broad 'starting a concrete coding task' trigger that creates minor overlap with general coding skills.

DimensionReasoningScore

Specificity

"Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review" names the domain and two concrete actions (retrieve, apply), matching the 'names domain and 1-2 concrete actions' anchor. It does not reach 4 because the actions themselves are not enumerated (no mention of searching, merging, or how application works), and not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Clearly 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 concrete trigger phrases, matching the top anchor. It is not lower because both elements are explicit, and the reuse/refresh clause adds scope guidance.

5 / 5

Trigger Term Quality

Includes quoted natural phrases users would say — "get rules", "load qodo rules", "relevant standards" — plus task contexts ("implementation, planning, refactoring, or code review", "starting a concrete coding task"), giving good keyword coverage. It falls short of 5 because common variations like "coding standards" or "style guide" are not covered, and exceeds 3 because multiple natural trigger phrasings are explicitly present.

4 / 5

Distinctiveness Conflict Risk

The branded Qodo niche and distinct quoted triggers ("load qodo rules") create a clear niche with minimal conflict risk, but "when starting a concrete coding task" is a broad trigger that overlaps with general coding/review skills. This sits between 'mostly distinct; minor overlap risk' (4) and 'clear niche with minimal conflict' (5), closer to 4 given the broad coding-task trigger.

4 / 5

Total

16

/

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

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.