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
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 extremely weak, essentially just restating the skill name with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. The only slight positive is that 'CDC pipeline' is a somewhat distinctive domain term.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates change data capture (CDC) pipelines that replicate database changes in real-time, configure source/target connectors, and set up transformation logic.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about change data capture, CDC, database replication, real-time data sync, streaming pipelines, or incremental data loading.'
Remove the duplicate trigger term ('cdc pipeline creator' is listed twice) and expand with varied natural language terms users might actually say, such as 'CDC', 'change data capture', 'data replication pipeline', 'database sync'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is an 'auto-activating skill for Data Pipelines' without describing what it actually does—no verbs like 'creates', 'configures', 'transforms', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the 'what' is entirely absent beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cdc pipeline creator' repeated twice. There are no natural user keywords like 'change data capture', 'CDC', 'data replication', 'streaming pipeline', 'database sync', or similar terms users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'CDC pipeline' is somewhat niche and specific to change data capture scenarios, which provides some distinctiveness. However, the lack of detail about what specifically it does versus other data pipeline skills creates potential overlap within the 'Data Pipelines' category. | 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 an empty template with no substantive content. It repeatedly names 'cdc pipeline creator' without ever explaining what CDC (Change Data Capture) pipelines are, how to build them, what tools to use, or providing any executable guidance. It fails on every dimension as it contains zero actionable information.
Suggestions
Add concrete, executable code examples for setting up a CDC pipeline (e.g., using Debezium with Kafka, or AWS DMS, or a Python-based approach with specific connectors and configurations).
Define a clear multi-step workflow for creating a CDC pipeline: source database configuration, connector setup, topic/stream creation, sink configuration, and validation/testing steps with explicit checkpoints.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than providing actual technical guidance.
Add references to detailed sub-documents for specific CDC patterns (e.g., log-based vs. query-based CDC, schema evolution handling, exactly-once delivery guarantees).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cdc pipeline creator' excessively, and contains zero substantive information about how to actually create CDC pipelines. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific steps, no architecture patterns, no tool recommendations. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, no validation checkpoints, and no process to follow for creating a CDC pipeline. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of placeholder text with no references to detailed materials, no links to examples or configuration files, and no meaningful structural organization beyond generic section headers. | 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.