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.
83
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/qodo-get-rules/SKILL.mdQuality
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, includes explicit trigger conditions with a 'Use when' clause, and is distinctive enough to avoid conflicts with other skills. The main area for improvement is that the specificity of capabilities could be slightly more detailed about what kinds of rules or what happens after they're loaded, but the description is effective and concise overall.
| 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/searching rules) described with some detail about the mechanism. | 2 / 3 |
Completeness | Clearly answers both 'what' (loads coding rules from Qodo by generating a semantic search query) and 'when' (explicit 'Use when' clause covering Qodo configuration, code tasks, and implementation planning, plus a 'Skip if' condition). This is a well-structured description with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'write', 'edit', 'refactor', 'review code', 'implementation planning', and 'Qodo'. These cover the common variations of when a user would need coding rules loaded. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Qodo' as the source and the narrow scope of loading coding rules via semantic search. The 'Skip if rules are already loaded' clause further reduces conflict risk. Unlikely to be confused with general coding or code review skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with excellent workflow clarity, strong actionability through executable code examples, and good progressive disclosure via reference files. However, it is significantly too verbose — the inline bash scripts for git URL parsing and config reading are things Claude can derive from brief instructions, and several points are repeated across sections. The token cost is high relative to the unique information conveyed.
Suggestions
Drastically reduce the bash scripts in Steps 2 and 3 — replace with concise pseudocode or a brief description (e.g., 'Parse git remote URL to extract org/repo path; detect module scope from cwd relative to repo root') since Claude can generate the implementation.
Remove redundant mentions of the skip-if-loaded check (appears in description, Step 1, and Common Mistakes) — state it once prominently.
Trim the config parsing section to just list the config keys and precedence rules without the full bash example, which Claude can easily generate from a specification.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose at ~180 lines. It explains concepts Claude already knows (how to parse git URLs, how to read JSON config files), includes lengthy bash scripts for straightforward operations, and repeats information across sections (e.g., the skip-if-loaded check is mentioned in the description, Step 1, and Common Mistakes). | 1 / 3 |
Actionability | The skill provides fully executable bash code for git repo detection, config parsing, and URL construction. The query format is precisely specified with exact structure, and the severity enforcement table gives concrete, unambiguous guidance. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit validation checkpoints (check if loaded, verify git repo, verify config, generate queries, call API, format output, apply rules, report). Error handling and graceful degradation paths are specified at each step. | 3 / 3 |
Progressive Disclosure | The skill maintains a clear overview structure while delegating detailed content to one-level-deep references (references/repository-scope.md, references/query-generation.md, references/search-endpoint.md, references/output-format.md). Navigation is well-signaled with descriptive link text. | 3 / 3 |
Total | 10 / 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
8fb6b55
- 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.