cdc-pipeline-creator
Cdc Pipeline Creator - Auto-activating skill for Data Pipelines. Triggers on: cdc pipeline creator, cdc pipeline creator Part of the Data Pipelines skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
1.16xAverage 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/cdc-pipeline-creator/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 essentially a placeholder with no substantive content. It only provides the skill name, a duplicate trigger term, and a category label. Claude would have no meaningful information to determine when to select this skill over others or what capabilities it provides.
Suggestions
Add specific actions the skill performs, e.g., 'Creates change data capture pipelines to replicate database changes, configure source/target connections, generate CDC SQL statements, and monitor replication status.'
Add a 'Use when...' clause with natural trigger terms like 'change data capture', 'database replication', 'sync tables', 'real-time data sync', 'track database changes', 'Debezium', 'Kafka Connect'.
Specify the technologies or platforms supported (e.g., specific databases, streaming platforms) to improve distinctiveness from generic data pipeline skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Cdc Pipeline Creator' and category 'Data Pipelines'. There is no explanation of what the skill actually does (e.g., creates change data capture pipelines, configures sources/sinks, generates SQL). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just the skill name repeated. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cdc pipeline creator' repeated twice, which is the skill name itself. Missing natural user terms like 'change data capture', 'database replication', 'streaming data', 'sync tables', or 'real-time data'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'CDC' is a specific domain term that provides some distinctiveness, the lack of detail about what kind of CDC pipelines or what actions are performed means it could overlap with other data pipeline or ETL skills. | 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 content is essentially a placeholder with no instructional value. It describes what a CDC pipeline creator skill would do but provides no actual guidance, code examples, or workflows for creating CDC pipelines. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete code examples for setting up CDC pipelines (e.g., Debezium configuration, Kafka Connect setup, or database trigger-based approaches)
Define a clear multi-step workflow: 1) Configure source database for CDC, 2) Set up change capture mechanism, 3) Define transformation logic, 4) Configure target sink, 5) Validate data consistency
Include specific tool configurations (e.g., Debezium connector JSON, Spark Structured Streaming code, or Airflow DAG examples)
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for creating CDC pipelines. The content only describes what the skill claims to do without actually teaching how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite CDC pipelines being multi-step processes involving source configuration, change capture, transformation, and target loading, no steps or validation checkpoints are provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure for learning. There are no references to detailed documentation, examples, or related materials that would help with actual implementation. | 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
0c08951
- 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.