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 ./kiro-power-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.

A highly actionable, validation-rich workflow whose retrieval core is excellent, undercut by verbosity: repeated reuse/empty-result rules, an inline runtime-update policy wall, and scattered section ordering. Bundle references are genuinely well structured and conditionally loaded.

Suggestions

State the reuse and empty-result-is-valid rule once (e.g., in Preflight) and remove the restatements in Instructions, Search and merge, Error Handling, and Guardrails.

Move the conditional upgrade-route policy (channel selection, latest-2 recovery, checksum-pinned installer detail) into a references/runtime-updates.md file, keeping only the unadorned version probe and stop condition inline — mirroring how windows-shells.md is already handled.

Consolidate time-sensitive version stamps ("2.0.0 or newer", "--skill-version 1.1.8 --distribution kiro-power") into a single variables note so they can be maintained in one place instead of being woven into prose and commands.

DimensionReasoningScore

Conciseness

The core retrieval workflow (queries, search, merge, output) is efficient and free of known-concept padding, but the ~25-line "Runtime compatibility gate" is dense conditional policy, the empty-result rule is restated at least three times ("An empty result is valid", "an empty result is valid", "An empty merged list is a valid outcome"), and pinned versions ("2.0.0 or newer", "--skill-version 1.1.8") sit outside any deprecated/old-patterns section. Mostly efficient but clearly tighten-able — fits anchor 3 better than 2 (no generic explanations) or 4 (several padded/redundant passages).

3 / 5

Actionability

The Quick start block is copy-paste ready ("qodo read rules search --query … --top-k 20 --scopes "/owner/repo/" --json"), the query template is exact with a literal JWT example, and fallbacks give concrete commands ("${QODO_HOME:-$HOME/.qodo}/bin/qodo"). Not 5 because the MCP path gets argument names but no example call, and the upgrade-authorization prose ("Choose one deployment-approved upgrade route, explain it…") is directional rather than executable.

4 / 5

Workflow Clarity

The pipeline (reuse check → preflight auth/scope → two queries → search/merge → output/apply) is sequenced with explicit validation checkpoints (unadorned version probe first, "Check isError", one catalog refresh and retry, low-return fallback re-run once) and feedback loops. Not 5 because section order diverges from execution order (Quick start appears before Preflight, the update-notice and gate sections interrupt the mainline) and the gate's run-on policy sentences make the happy path harder to follow. Read-only search, so no destructive-operation cap applies.

4 / 5

Progressive Disclosure

All three referenced files (references/skill-updates.md, windows-shells.md, windows-launcher.md) exist, are one level deep, and are clearly signaled with conditions ("read shell guidance… before the first call; launcher recovery… only if invocation fails"). Not 5 because the long inline "Runtime compatibility gate" policy is content that could live in a reference file — the bundle already demonstrates that pattern — leaving a minor organization gap; not 3 because references are well signaled and most content is appropriately placed.

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 answers what and when explicitly, uses third-person imperative voice, and includes literal trigger phrases a user would naturally say. Its only weaknesses are a slightly thin synonym set for triggers and one broad trigger clause ("when starting a concrete coding task") that could over-fire.

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 several concrete actions (retrieve, apply, reuse, refresh) across named task contexts. Not 5 because it never says what applying rules concretely involves; not 3 because it lists more than the 1-2 actions that anchor requires.

4 / 5

Completeness

The "what" is explicit ("Retrieve and apply Qodo coding rules…") and the "when" is explicit with concrete trigger phrases ("Use on 'get rules', 'load qodo rules', or 'relevant standards' and when starting a concrete coding task"), matching the anchor-5 pattern of both halves plus literal triggers. The reuse/refresh scoping sentence adds behavioral guidance on top.

5 / 5

Trigger Term Quality

Explicit natural phrases — "get rules", "load qodo rules", "relevant standards", "when starting a concrete coding task" — read like things a user would actually say. Not 5 because common synonyms such as "coding standards", "conventions", or "style guide" are missing alongside "rules".

4 / 5

Distinctiveness Conflict Risk

The "Qodo" brand and rules-specific triggers carve a clear niche with minimal wrong-skill risk. Not 5 because "when starting a concrete coding task" is a broad trigger that could fire on nearly any coding request and overlap with general code-review or linting-standards skills; not 3 because the brand scoping keeps it mostly distinct.

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

kiro-power-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.