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.
33
0%
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
0%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 essentially a placeholder with no substantive content. It names the skill and its category but provides zero information about what actions it performs, what inputs/outputs it handles, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a list of alternatives.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Updates data catalog entries with schema changes, adds new dataset metadata, syncs table definitions from pipeline outputs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to update catalog metadata, register new datasets, sync schema changes, or manage data dictionary entries.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users might actually use, such as 'catalog', 'metadata', 'schema registry', 'data dictionary', 'dataset registration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Data Catalog Updater') and mentions it's part of 'Data Pipelines' but never describes what it actually does—no verbs like 'updates', 'syncs', 'registers', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a mechanical 'Triggers on' line with a repeated skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data catalog updater' repeated twice. These are not natural keywords a user would say; a user might say 'update the catalog', 'add dataset metadata', 'register a new table', etc. The terms are generic and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic. 'Data Catalog Updater' in the 'Data Pipelines' category could overlap with any data management, ETL, metadata, or pipeline skill. There are no distinct triggers or specific scope boundaries to differentiate it. | 1 / 3 |
Total | 4 / 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 an empty template with no actual instructional content. It repeatedly restates the skill name ('data catalog updater') without providing any concrete guidance, code, commands, or domain-specific knowledge about updating data catalogs. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples showing how to update a data catalog (e.g., using tools like Apache Atlas, AWS Glue Data Catalog, or OpenMetadata APIs with specific Python/CLI commands).
Define a clear multi-step workflow for catalog updates, including validation steps such as verifying schema changes, checking metadata consistency, and confirming catalog entries post-update.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that merely restate the skill name, and replace them with actual technical content covering common catalog update patterns (schema evolution, lineage tracking, metadata refresh).
Add specific examples with input/output, such as a before/after of a catalog entry being updated when a new column is added to a data pipeline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about data catalog updating. Every section restates the skill name without adding substance. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no specific steps, and no examples of actual data catalog updating. The content only describes what the skill claims to do in abstract terms without any executable or instructive content. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just vague claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no meaningful content. There are no references to detailed files, no navigation structure, and no actual information to disclose progressively. | 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
3e83543
- 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.