auto-import-rules
Enforces dlt import conventions and ordering. Use when writing or modifying Python imports in dlt/ or tests/.
91
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 description is functional with clear 'what' and 'when' clauses and good distinctiveness for its specific niche. However, it could benefit from more specific action verbs and additional trigger terms that users might naturally use when dealing with import issues.
Suggestions
Add more specific actions like 'sorts imports', 'validates import groups', 'fixes import order violations' to improve specificity
Include additional trigger terms users might say such as 'import order', 'import sorting', 'organize imports', or 'import style'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (dlt import conventions) and one action (enforces ordering), but doesn't list multiple concrete actions like 'sort imports', 'validate import groups', or 'fix import violations'. | 2 / 3 |
Completeness | Clearly answers both what ('Enforces dlt import conventions and ordering') and when ('Use when writing or modifying Python imports in dlt/ or tests/') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Python imports', 'dlt/', and 'tests/' but misses common variations users might say like 'import order', 'import sorting', 'isort', or 'import style'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting dlt-specific import conventions in specific directories (dlt/ or tests/), unlikely to conflict with general Python or import-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill that exemplifies token efficiency while maintaining complete actionability. It provides specific import conventions with concrete examples, clear ordering rules, and appropriate delegation to a separate file for complex optional dependency handling. The content is perfectly scoped for its purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides specific, actionable guidance without explaining concepts Claude already knows. No padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, specific rules with exact import syntax examples. Clear patterns like `from dlt.common import logger` and `if TYPE_CHECKING:` blocks are copy-paste ready. | 3 / 3 |
Workflow Clarity | For a simple rule-based skill, the workflow is unambiguous. Import order is clearly numbered, exceptions are explicitly noted, and the single-task nature doesn't require multi-step validation. | 3 / 3 |
Progressive Disclosure | Appropriately structured with a clear reference to [common-libs.md] for optional dependencies. Content is well-organized into logical sections without unnecessary nesting. | 3 / 3 |
Total | 12 / 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 | |
- 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.