api-connector-builder

Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/api-connector-builder/SKILL.md

The canonical home for this skill is tdg-personal/api-connector-builder

Quality

Content

78%Weight 40%Scale 1-5

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

A clean, concise, well-structured skill body that avoids padding and clearly sequences the integration-building workflow. Its main weakness is actionability: it offers patterns and checklists but no executable code or concrete commands to anchor the guidance.

Suggestions

Add a minimal copy-paste-ready skeleton (e.g., a stub provider.py/connector.py with the expected class shape and registration call) so Claude has an executable starting point matching the house style.

Make the workflow's validation step explicit with a feedback loop, e.g., 'Run the host repo's connector tests; if they fail, align config/registry wiring and re-run' rather than the implicit 'should look obvious' check.

Include one concrete command or snippet per layer slice (config/schema, client/transport, registration) to lift actionability from descriptive to executable.

Dimension	Reasoning	Score
Conciseness	Lean, bullet-driven prose with no padding and no re-explanation of concepts Claude already knows; every section earns its place in the context window.	5 / 5
Actionability	Provides concrete structural guidance (layer slices, file-tree shapes, checklist) but no executable code or commands; it instructs at a descriptive level rather than giving copy-paste-ready examples for the common cases.	3 / 5
Workflow Clarity	A clear four-step sequence with a Quality Checklist serving as an end-state checkpoint, but the 'validate against the source pattern' step is implicit rather than an explicit validate-fix-retry loop.	4 / 5
Progressive Disclosure	Well-organized into clearly signaled sections (When to Use, Guardrails, Workflow, Reference Shapes, Quality Checklist) with no bundle files and no nested references; easy to navigate as a self-contained overview.	5 / 5
	Total	17 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 concise, well-targeted description that clearly states both what the skill does and when to use it, using third-person voice and natural trigger terms. It is slightly light on enumerating multiple concrete actions, which caps specificity at the mid-anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (API connectors/providers) and one concrete action ('matching the target repo's existing integration pattern exactly'), but does not enumerate multiple specific actions, so it sits at the clear-what/single-action anchor rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both: what ('Build a new API connector or provider by matching the target repo's existing integration pattern exactly') and when ('Use when adding one more integration without inventing a second architecture'), with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural terms users would say such as 'API connector', 'provider', and 'integration', with good keyword coverage; only a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (repo-native integration matching) with minimal overlap risk against generic HTTP/client skills; minor overlap possible with closely related backend skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: skills/api-connector-builder/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.