database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill database-design64
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
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (database design) and lists relevant subtopics, but reads more like a table of contents than actionable guidance. It lacks concrete actions Claude would perform and critically missing explicit trigger conditions for when to use this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about database schema design, choosing between SQL/NoSQL, optimizing queries, or selecting an ORM'
Convert topic areas into concrete actions: 'Designs database schemas, recommends indexing strategies, evaluates ORM options, advises on serverless database selection'
Expand trigger terms to include common variations: 'SQL', 'NoSQL', 'PostgreSQL', 'MongoDB', 'data modeling', 'query optimization', 'database performance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database design) and lists several specific areas (schema design, indexing strategy, ORM selection, serverless databases), but these are topic areas rather than concrete actions Claude would perform. | 2 / 3 |
Completeness | Describes the 'what' at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'schema design', 'indexing', 'ORM', 'serverless databases' that users might mention, but missing common variations like 'SQL', 'NoSQL', 'database optimization', 'table structure', or 'data modeling'. | 2 / 3 |
Distinctiveness Conflict Risk | Database-focused which provides some distinction, but 'decision-making' and 'design principles' are vague enough to potentially overlap with general architecture or backend development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels as a navigation hub with exceptional conciseness and progressive disclosure. The content map table is well-designed and the anti-patterns section adds value. However, the skill lacks concrete executable examples and could benefit from validation steps in the decision workflow to help Claude verify database/ORM choices are appropriate.
Suggestions
Add a brief concrete example showing how to apply the decision checklist (e.g., 'For a simple blog: SQLite + Drizzle because...')
Include validation criteria in the checklist - how does Claude know if the database choice is correct for the context?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what databases are or how they work. Every line serves a purpose - file map, checklist, anti-patterns. Assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides good structural guidance (checklists, anti-patterns, file references) but lacks concrete code examples or executable commands. The skill is more of a navigation hub than actionable instructions itself. | 2 / 3 |
Workflow Clarity | The decision checklist provides a sequence but lacks validation checkpoints or feedback loops. For database design decisions, there's no explicit 'verify your choice' step or criteria for when to reconsider decisions. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map table showing exactly which file to read for each topic. One-level-deep references with clear signaling. The main file serves as a concise overview pointing to detailed materials. | 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | 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.