qodo-get-rules

Loads coding rules from Qodo most relevant to the current coding task by generating a semantic search query from the assignment. Use when Qodo is configured and the user asks to write, edit, refactor, or review code, or when starting implementation planning. Skip if rules are already loaded.

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable skill with a clear multi-step workflow, explicit error handling, and concrete executable code. Its main weakness is moderate verbosity — the scope detection and config parsing sections are thorough but could be tightened, and some explanatory text restates what's already clear from the code. The progressive disclosure structure references appropriate external files but the main file retains substantial inline detail that could be offloaded.

Suggestions

Move the full scope-detection bash script to references/repository-scope.md and keep only a summary + reference link in the main SKILL.md to reduce inline verbosity.

Remove the opening Description section which largely duplicates the frontmatter metadata and the workflow's Step 1.

Dimension	Reasoning	Score
Conciseness	The skill is moderately verbose — the bash scripts for scope detection and config parsing are detailed and useful, but there's some unnecessary explanation (e.g., describing what scope does, explaining graceful degradation repeatedly). The description section at the top restates the frontmatter. Some tightening is possible without losing clarity.	2 / 3
Actionability	The skill provides fully executable bash code for git repo detection, scope parsing, config reading, and API URL construction. The query format is precisely specified with exact structure. The severity enforcement table gives concrete, unambiguous guidance. Commands are copy-paste ready.	3 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with explicit checkpoints: check if already loaded (skip), verify git repo (exit gracefully if not), verify config (exit gracefully if missing), generate queries, call API, format output, apply rules by severity, and report. Error handling and graceful degradation are specified at each step.	3 / 3
Progressive Disclosure	The skill references multiple supporting files (references/repository-scope.md, references/query-generation.md, references/search-endpoint.md, references/output-format.md, ../../README.md) which is good structure, but no bundle files were provided to verify these exist. The main SKILL.md itself is quite long (~200 lines) and some content (like the full scope detection script) could arguably live in a reference file, while the core workflow stays lean.	2 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted description that clearly communicates its purpose, trigger conditions, and scope. It excels in completeness with explicit 'use when' and 'skip if' clauses, and is highly distinctive due to the Qodo-specific context. The only minor weakness is that the capability itself is a single action rather than multiple concrete actions, limiting the specificity score.

Dimension	Reasoning	Score
Specificity	The description names the domain (coding rules from Qodo) and describes the core action (loads rules via semantic search query), but it doesn't list multiple specific concrete actions—it's essentially one action (loading rules) with a method description.	2 / 3
Completeness	Clearly answers both 'what' (loads coding rules from Qodo via semantic search) and 'when' (when Qodo is configured and user asks to write/edit/refactor/review code or starts implementation planning), plus includes a 'skip when' condition for additional clarity.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'write', 'edit', 'refactor', 'review code', 'implementation planning', 'Qodo', and 'coding rules'. These cover the common variations of what a user would say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific mention of 'Qodo' as the source and the narrow purpose of loading coding rules via semantic search. The 'Skip if rules are already loaded' clause further reduces false triggers. Unlikely to conflict with general coding or code review skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: qodo-ai/qodo-skills
Commit: e7b6771

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.