DBA Admin Agent. 백업, 복구, 보안, 권한 관리를 담당합니다.
35
19%
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-admin/SKILL.mdQuality
Discovery
17%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 provides a basic overview of database administration responsibilities but lacks the detail needed for effective skill selection. It names broad capability categories without specific actions, omits natural trigger terms users would say, and critically lacks any 'Use when...' guidance. The Korean language may limit discoverability for English-speaking users.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about database backups, restoring databases, managing database users, or configuring database security'
Include natural trigger terms in both Korean and English: 'DB backup', 'database restore', 'SQL permissions', 'database security', 'user access', '데이터베이스'
List specific concrete actions instead of categories: 'Create and schedule database backups, restore databases from backups, manage user roles and permissions, configure security policies, audit database access'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DBA Admin) and lists some actions (백업/backup, 복구/recovery, 보안/security, 권한 관리/permission management), but these are high-level categories rather than concrete specific actions like 'create database backups' or 'restore from snapshots'. | 2 / 3 |
Completeness | Only answers 'what' at a high level (담당합니다/handles these tasks). Completely missing 'when' clause - no explicit triggers or 'Use when...' guidance for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical/administrative terms in Korean (백업, 복구, 보안, 권한 관리) but lacks natural user trigger terms. Missing common variations users might say like 'database backup', 'restore DB', 'user permissions', 'access control', or file extensions. | 1 / 3 |
Distinctiveness Conflict Risk | 'DBA Admin Agent' provides some specificity to database administration, but terms like '보안' (security) and '권한 관리' (permission management) are generic enough to potentially conflict with general security or access management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%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 placeholder that lists responsibilities without providing any actionable guidance. For critical DBA operations like backup/recovery and security management, the complete absence of concrete commands, scripts, validation steps, or workflows makes this skill ineffective. Claude would not know how to actually perform any of the listed tasks.
Suggestions
Add concrete backup/recovery scripts or commands with specific examples (e.g., pg_dump commands, cron job configurations, restore procedures)
Include step-by-step workflows with validation checkpoints for critical operations like backup verification and security audits
Provide specific security configuration examples (user creation, permission grants, audit logging setup) rather than just listing 'security settings'
Link to the referenced files (scripts/backup/, docs/database/security/) with brief descriptions of what each contains
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude knows, but it's so sparse that it lacks substance rather than being efficiently dense with useful information. | 2 / 3 |
Actionability | The skill provides only vague role descriptions and bullet points with no concrete commands, code examples, or executable guidance for any of the listed tasks (backup, recovery, security, permissions). | 1 / 3 |
Workflow Clarity | No workflows are defined for any of the critical DBA operations mentioned. Backup/recovery and security operations require clear step-by-step processes with validation, but none are provided. | 1 / 3 |
Progressive Disclosure | The skill references output locations (scripts/backup/, docs/database/security/) suggesting external files exist, but provides no actual links or guidance on what those files contain or how to navigate them. | 2 / 3 |
Total | 6 / 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 | |
9242c58
Table of Contents
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.