CtrlK
BlogDocsLog inGet started
Tessl Logo

data-throughput-accelerator

Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise instruction skill with a clear sequenced workflow and concrete accounting/verification gates. Its main weakness is actionability: the heuristics are principles rather than executable commands or code, even though the workflow and output template are specific.

Suggestions

Add one or two short executable snippets (e.g., a SQL/CLI idiom for manifest-based skip or a backlog-measurement query) so the Fast Path Heuristics move from principle to copy-paste guidance.

Show the accounting-output block as a fillable template with placeholders (e.g., '<source files>', '<raw rows>') alongside the worked example so Claude knows which fields to populate.

Make the 'safe catch-up or sample benchmark' step (workflow step 3) concrete by naming what a safe sample benchmark looks like (size, isolation, rollback).

DimensionReasoningScore

Conciseness

Lean bullet-driven body that assumes Claude's competence; it does not explain what ETL, manifests, or warehouses are, and every section earns its tokens.

3 / 3

Actionability

The workflow, measurement checklist, and accounting template are concrete and copy-paste ready, but the bulk ('Move compute to where the data already is', 'Prefer warehouse-native scans', 'Make writes idempotent') is heuristic principle rather than executable code or commands.

2 / 3

Workflow Clarity

A clear 7-step numbered sequence with explicit verification gates — the 'Correctness gate' accounting block, 'Promote only the fastest path that keeps counts and timestamps coherent', and 'Rerun final accounting' — plus guardrails that act as feedback constraints for batch operations.

3 / 3

Progressive Disclosure

Well-organized into clearly signaled sections (First Distinction, Fast Path Heuristics, Workflow, Accounting Output, Guardrails) with no external references needed and no nested indirection.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, concise description with an explicit 'Use when' trigger and a broad but specific list of natural scenarios, clearly scoping a distinct throughput-acceleration niche. Voice is appropriately imperative/third-person with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete scenarios — 'large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization' — each a specific action domain rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('become much faster while preserving data correctness') and when via a clear 'Use when...' clause listing concrete triggers.

3 / 3

Trigger Term Quality

Covers natural terms users say when needing this skill ('backfill', 'export', 'ETL', 'warehouse loading', 'table synchronization', 'manifest catch-up'), with good variation across common phrasings.

3 / 3

Distinctiveness Conflict Risk

The data-throughput/backfill/manifest niche is distinct and the triggers (ETL, warehouse loading, manifest catch-up) are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.