Set up, configure, and troubleshoot the Snowflake Kafka Connector V4 (Snowpipe Streaming high-performance architecture). Covers fresh installations, connector property configuration for default pipe and user-defined pipe modes, server-side and client-side validation, JMX monitoring, migration from V3, and common error diagnosis. Triggers: kafka connector v4, kafka connector setup, kafka connector config, kafka connector troubleshoot, snowflake kafka connector, configure kafka connector, kafka connector help, kafka streaming connector.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 excellent skill description that clearly defines the scope (Snowflake Kafka Connector V4), lists specific capabilities (installation, configuration, validation, monitoring, migration, error diagnosis), and provides explicit trigger terms. It is highly distinctive and would be easy for Claude to correctly select from a large pool of skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: set up, configure, troubleshoot, fresh installations, connector property configuration for default pipe and user-defined pipe modes, server-side and client-side validation, JMX monitoring, migration from V3, and common error diagnosis. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (set up, configure, troubleshoot Snowflake Kafka Connector V4 with specific sub-capabilities) and 'when should Claude use it' via the explicit 'Triggers:' clause listing specific trigger terms. | 3 / 3 |
Trigger Term Quality | Includes a comprehensive set of natural trigger terms that users would actually say, covering variations like 'kafka connector v4', 'kafka connector setup', 'kafka connector config', 'kafka connector troubleshoot', 'snowflake kafka connector', 'configure kafka connector', and 'kafka streaming connector'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Snowflake Kafka Connector V4 with Snowpipe Streaming architecture, making it very unlikely to conflict with other skills. The combination of 'Snowflake', 'Kafka', 'Connector V4', and 'Snowpipe Streaming' creates a clear, distinct niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill covering a complex multi-workflow topic (fresh setup, configuration, troubleshooting, migration). Its greatest strengths are executable code/SQL throughout, clear workflow sequencing with validation steps, and comprehensive troubleshooting with symptom-based branching. Its main weakness is length — at 600+ lines in a single file with no bundle support, it consumes significant context window and has some content redundancy between instructional steps and templates.
Suggestions
Extract the Templates section (Templates 1-12) into a separate TEMPLATES.md file referenced from the main skill to reduce token consumption and improve progressive disclosure.
Remove the 'What this skill provides' section as it largely duplicates the 'When to use' section — the step headers themselves serve as sufficient navigation.
Consolidate the grants SQL that appears in both Step 2 and Template 4 — keep it only in the template and reference it from Step 2 to eliminate redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly efficient for its scope, but it's quite long (~600+ lines) with some redundancy between the Instructions steps and the Templates section (e.g., the grants SQL appears in both Step 2 and Template 4). The 'What this skill provides' section largely duplicates the 'When to use' section. However, it avoids explaining basic concepts Claude already knows and most content earns its place given the complexity of the topic. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes executable SQL, bash commands, or complete JSON/properties configuration templates with clear placeholders. The troubleshooting section provides specific diagnostic commands and targeted fixes. Templates are copy-paste ready with well-named placeholders. | 3 / 3 |
Workflow Clarity | The multi-step workflows are clearly sequenced with numbered steps, explicit goals per step, validation checkpoints (Step 5 verification), error handling branches, and feedback loops (e.g., troubleshooting symptom-based branching, migration procedure with verification). Step 0 provides clear intent detection and routing. The migration procedure includes a critical time-bound constraint (7-day offset retention). | 3 / 3 |
Progressive Disclosure | The skill is a monolithic document with no bundle files to reference. While internally well-organized with clear sections and headers, the Templates section alone is ~250 lines that could be split into separate reference files. The troubleshooting section is extensive and could benefit from being a separate file referenced from the main skill. However, the internal structure with clear step numbering and section headers provides reasonable navigation within the single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (866 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
25dfdc4
Table of Contents
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.