data-catalog-updater
Data Catalog Updater - Auto-activating skill for Data Pipelines. Triggers on: data catalog updater, data catalog updater Part of the Data Pipelines skill category.
35
3%
Does it follow best practices?
Impact
94%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/data-catalog-updater/SKILL.mdQuality
Discovery
7%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 severely lacking in all key areas. It reads like auto-generated boilerplate with no actual content describing capabilities, use cases, or meaningful trigger terms. The repeated trigger term and absence of any concrete actions make it nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Updates data catalog entries, syncs metadata schemas, validates catalog consistency, registers new data sources'
Replace the redundant trigger terms with natural variations users would say: 'catalog update', 'metadata sync', 'register dataset', 'catalog entry', 'data dictionary'
Add an explicit 'Use when...' clause describing scenarios: 'Use when the user needs to update data catalog entries, sync metadata between systems, or register new data sources in the catalog'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions - it only names the skill ('Data Catalog Updater') without explaining what it actually does. There are no verbs describing capabilities like 'updates', 'syncs', 'validates', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no use cases or scenarios provided). The 'Triggers on' line is redundant and uninformative. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('data catalog updater, data catalog updater'). This provides no natural language variations users might actually say, such as 'update catalog', 'sync metadata', 'catalog entries', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Data Catalog Updater' is somewhat specific to a domain, the lack of detail about what distinguishes it from other data-related skills creates potential overlap. The category mention 'Data Pipelines' helps slightly but doesn't clarify boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 with no substantive content. It describes a capability ('data catalog updater') without providing any actual instructions, code examples, schemas, or workflows. The content consists entirely of generic marketing-style language that would be useless for guiding Claude to perform any real task.
Suggestions
Add concrete, executable code examples showing how to update a data catalog (e.g., using Apache Atlas, AWS Glue Catalog, or similar tools)
Define a clear workflow with steps: discover schema changes -> validate metadata -> update catalog -> verify updates
Include specific input/output examples showing what catalog entries look like before and after updates
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual data catalog operations. The entire skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for any data catalog update process. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, schemas, or API documentation. The 'Related Skills' section mentions a category but provides no navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
e9f9c93
- 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.