incremental-load-setup
Incremental Load Setup - Auto-activating skill for Data Pipelines. Triggers on: incremental load setup, incremental load setup Part of the Data Pipelines skill category.
36
3%
Does it follow best practices?
Impact
96%
1.04xAverage 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/incremental-load-setup/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 thin and auto-generated, providing no meaningful information about what the skill actually does or when it should be selected. It merely restates the skill name and category without listing concrete actions, natural trigger terms, or explicit usage guidance. It would be nearly indistinguishable from other data pipeline skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures incremental data loading pipelines including change detection, watermark columns, merge/upsert strategies, and partition-based loading.'
Add a 'Use when...' clause with natural trigger terms like 'incremental load', 'delta load', 'CDC', 'change data capture', 'upsert', 'only load new data', 'avoid full refresh'.
Remove the duplicate trigger term and replace with varied, natural language phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Incremental Load Setup' without describing any concrete actions. There are no specific capabilities listed such as configuring change detection, setting up watermark columns, or defining merge strategies. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is just a redundant repetition of the title rather than explicit trigger guidance. There is no meaningful 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'incremental load setup' repeated twice. There are no natural variations a user might say such as 'CDC', 'change data capture', 'upsert', 'delta load', 'incremental refresh', or 'watermark column'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'incremental load setup' is somewhat specific to a data engineering niche, which provides some distinctiveness. However, the lack of concrete details means it could overlap with other data pipeline skills covering ETL, data loading, or pipeline configuration. | 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 essentially a placeholder or template with no substantive content. It contains no actionable instructions, no code examples, no workflow steps, and no domain-specific knowledge about incremental load setup. Every section describes the skill's intent rather than providing actual guidance Claude could use.
Suggestions
Add concrete, executable code examples for common incremental load patterns (e.g., watermark-based extraction in Spark/Airflow, CDC with merge/upsert SQL, timestamp-based filtering).
Define a clear multi-step workflow: identify watermark column → query source with filter → transform → merge into target → update watermark → validate row counts, with explicit validation checkpoints.
Remove the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace them with actual technical content—patterns, anti-patterns, and configuration snippets.
If the topic is large, create bundle files (e.g., AIRFLOW_EXAMPLE.md, SPARK_EXAMPLE.md, CDC_PATTERNS.md) and reference them from a concise overview in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The 'Example Triggers' section restates the trigger phrase three times with trivial variations. No actual incremental load setup knowledge is conveyed. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no configuration examples, no schema designs. The skill describes what it claims to do rather than actually instructing Claude how to do it. It is entirely abstract. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Incremental load setup is inherently a multi-step process (e.g., watermark tracking, change detection, merge/upsert logic, validation) and none of these steps are mentioned, let alone sequenced with validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured sections with real content, and no bundle files to point to. There is nothing to navigate to or discover. | 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
ba8561d
- 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.