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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cdc-pipeline-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It only states the skill name, repeats it as triggers, and mentions a category. Without any explanation of capabilities, concrete actions, or natural trigger terms, Claude would have no basis for selecting this skill appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Creates change data capture pipelines to replicate database changes, configures source and target connections, generates CDC SQL statements'
Include a 'Use when...' clause with natural trigger terms like 'change data capture', 'database replication', 'sync tables', 'track changes', 'streaming updates', 'Debezium', 'Kafka Connect'
Specify what technologies or databases are supported to help distinguish from other 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' guidance is just the skill name repeated. There is no explicit trigger guidance or use case explanation. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cdc pipeline creator' repeated twice, which is the skill name itself rather than natural user language. Missing natural terms users would say like 'change data capture', 'database replication', 'streaming data', 'sync tables', etc. | 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 database skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains no CDC-specific knowledge, no executable code, no workflow guidance, and no concrete examples. The content fails to teach Claude anything about creating CDC pipelines.
Suggestions
Add concrete, executable 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 with validation checkpoints: source database setup → CDC connector configuration → transformation logic → sink configuration → validation
Include specific examples of CDC patterns (log-based, trigger-based, timestamp-based) with when to use each
Remove all generic boilerplate text and replace with actionable CDC-specific guidance including tool choices (Debezium, AWS DMS, Airbyte) and configuration snippets
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about CDC pipelines. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 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 rather than instructing 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 sink delivery, no steps or validation checkpoints are provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, examples, or related documentation. There's nothing to progressively disclose because there's no substantive content. | 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.