dba-architect
DBA Architect Agent. 스키마 설계, 정규화, 데이터 모델링을 담당합니다.
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dba-architect/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a role description rather than actionable guidance. While it's concise, it fails to provide any concrete instructions, examples, or workflows that would help Claude perform database architecture tasks. It reads more like a job description than a skill that teaches how to do something.
Suggestions
Add concrete examples of ERD notation standards and naming conventions to follow (e.g., table naming patterns, foreign key conventions)
Include a step-by-step workflow for schema design: requirements analysis → conceptual model → logical model → validation → physical DDL
Provide executable DDL templates or examples showing expected output format for migrations
Add references to detailed guides for normalization rules (1NF-3NF criteria) and when to denormalize
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean with no unnecessary explanations. Every line serves a purpose - role definition, responsibilities, and output locations are stated without padding. | 3 / 3 |
Actionability | The skill provides no concrete guidance, code examples, commands, or specific instructions. It only lists abstract responsibilities (ERD 설계, 정규화) without explaining how to perform them or what standards to follow. | 1 / 3 |
Workflow Clarity | No workflow or process is defined. The skill lists tasks but provides no sequence, steps, validation checkpoints, or guidance on how to approach database design tasks. | 1 / 3 |
Progressive Disclosure | The skill mentions output locations which implies some structure, but provides no references to detailed guides, templates, or examples. For a DBA architect role, references to naming conventions, normalization rules, or ERD templates would be expected. | 2 / 3 |
Total | 7 / 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 | |
- Repository
- shaul1991/shaul-agents-plugin
- Commit
9242c58
- 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.