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.
89
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
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 skill description that clearly communicates its purpose, trigger conditions, and scope. It excels in completeness with explicit 'use when' and 'skip if' clauses, and the Qodo-specific focus makes it highly distinctive. The only minor weakness is that the capability description is somewhat singular (loading rules) rather than listing multiple concrete actions.
| 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. Unlikely to conflict with general coding skills or other rule-loading mechanisms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 clear multi-step workflow, explicit validation checkpoints, and good progressive disclosure through reference files. The main weakness is moderate verbosity — the scope detection script and config parsing could be more concise, and some explanatory sentences don't add value for Claude. Overall it's a strong skill that effectively guides complex API integration behavior.
Suggestions
Tighten the scope detection bash script — Claude can infer SSH vs HTTPS parsing logic from a shorter example or a single-line comment rather than the full annotated script.
Remove explanatory sentences that state the obvious to Claude, such as 'Query quality directly determines retrieval quality' and 'Scope narrows results to rules relevant to this specific repository.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and includes useful executable code, but there's some verbosity — particularly the lengthy bash script for scope detection and the config parsing section. Some explanatory text could be trimmed (e.g., 'Query quality directly determines retrieval quality' is unnecessary for Claude). | 2 / 3 |
Actionability | The skill provides fully executable bash code for git detection, scope parsing, config reading, and UUID generation. The query format is precisely specified with exact structure. The API call instructions and severity enforcement table are concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit checkpoints: checking if rules are already loaded (Step 1), verifying git repo (Step 2), verifying config (Step 3), and graceful exit paths at multiple points. Error handling and degradation behavior are specified throughout. | 3 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to separate detailed content: references/repository-scope.md, references/query-generation.md, references/search-endpoint.md, and references/output-format.md. The main file serves as a clear overview with well-signaled links to detailed materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
f73fc26
- 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.