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 is an extremely weak description that essentially only provides a name and category label with no substantive content. It lacks any concrete actions, meaningful trigger terms, explicit usage guidance, or distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of similar data-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Updates data catalog entries with schema changes, registers new datasets, syncs metadata from pipeline outputs, and manages table lineage information.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions updating catalog entries, registering datasets, syncing metadata, schema changes, table lineage, or data discovery.'
Remove the duplicate trigger term ('data catalog updater' is listed twice) and replace with varied natural language terms users would actually use, such as 'catalog update', 'metadata sync', 'register table', '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 or equivalent guidance. | 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 a dataset', 'register a table', 'metadata', etc. The terms are overly generic and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Data Pipelines' and 'data catalog updater' could overlap with many data-related skills. Without specific actions or triggers, there's nothing to distinguish this from other data pipeline or catalog skills. | 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/placeholder with no actual instructional content. It repeats the phrase 'data catalog updater' numerous times without ever defining what a data catalog updater does, how to implement one, or what tools/code to use. It provides zero actionable value to Claude.
Suggestions
Add concrete, executable code examples showing how to update a data catalog (e.g., using Apache Atlas, AWS Glue Catalog, or OpenMetadata APIs with specific Python/CLI commands).
Define a clear multi-step workflow for catalog updates: e.g., 1) discover schema changes, 2) validate metadata, 3) push updates to catalog, 4) verify the update succeeded—with specific commands at each step.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that just restate the skill name, and replace them with actual technical guidance and patterns.
Add references to related files or documentation for advanced topics like lineage tracking, schema evolution handling, or integration with specific orchestration tools like Airflow.
| 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 are no concrete steps, code examples, commands, configurations, or specific guidance. The content only vaguely describes what the skill could do ('provides step-by-step guidance') without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about capabilities like 'validates outputs against common standards' with no actual implementation. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no references to detailed materials, no links to related files, and no meaningful structure beyond repetitive section headers that all say the same thing. | 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
4dee593
- 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.