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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill data-catalog-updaterOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or use cases. It lacks any concrete actions, meaningful trigger terms, or guidance on when Claude should select this skill. The redundant trigger term ('data catalog updater' listed twice) suggests auto-generation without human review.
Suggestions
Add specific actions the skill performs, e.g., 'Registers new datasets, updates metadata fields, syncs schema changes, validates catalog entries against data sources.'
Include a 'Use when...' clause with natural trigger terms like 'update catalog', 'register dataset', 'sync metadata', 'add to data catalog', 'catalog entry'.
Remove the redundant trigger term and expand with variations users might actually say when needing this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions - it only names itself ('Data Catalog Updater') without explaining what updating a data catalog actually involves (e.g., adding entries, syncing metadata, validating schemas). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('data catalog updater, data catalog updater'), which is redundant and unlikely to match natural user language like 'update catalog entries', 'sync metadata', or 'register dataset'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Data Catalog Updater' is somewhat specific to a domain, the lack of detail about what operations it performs could cause confusion with other data-related skills. The category mention ('Data Pipelines') provides some context but isn't sufficient. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes a capability ('data catalog updater') without providing any actual instructions, code examples, or concrete guidance on how to update data catalogs. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add concrete, executable code examples showing how to update data catalogs (e.g., using tools like Apache Atlas, AWS Glue Data Catalog, or similar)
Define a clear workflow with specific steps: discover schema changes, validate metadata, update catalog entries, verify updates
Include specific commands or API calls for common data catalog operations (add table, update column metadata, register lineage)
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actionable technical content
| 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 or API documentation, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.