CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate-connector

Validate an existing knowledge base connector against its service's API docs

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/validate-connector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is an exceptionally actionable, well-sequenced audit procedure with concrete verification steps and almost no filler — the only meaningful weakness is that everything lives inline in one long file. Splitting the per-domain checklists and the severity issue catalog into reference files would bring progressive disclosure in line with the rest of the quality.

Suggestions

Split the per-domain checklists (Steps 3-10) or the Step 11 severity-grouped issue catalog into references/ files (e.g., references/endpoint-checks.md, references/oauth-checks.md, references/issue-severity.md), keeping SKILL.md as a shorter overview that links to them.

Deduplicate the repeated close-out guidance: the Step 11 severity lists restate per-step checklist items and the final "Checklist Summary" section repeats the validation output a third time — consolidate into one location.

DimensionReasoningScore

Conciseness

Nearly every line is project-specific knowledge Claude cannot know (file paths, registry conventions, `listingCapped` semantics, `contentDeferred` patterns), so there is no padding or explanation of known concepts. It falls short of 5 because the Step 11 severity lists substantially restate the per-step checklists and the final "Checklist Summary" repeats the close-out a third time — minor duplication that could be trimmed.

4 / 5

Actionability

The guidance is fully concrete: exact file paths to read, exact function and module names (`safeUrlPathSegment`, `fetchWithRetry`, `computeContentHash`, `parseTagDate`), concrete escaping patterns (`externalId.replace(/'/g, "''")`), and runnable verification commands (`bun run lint`, type-check). This is copy-paste-ready, executable guidance for every step of the audit.

5 / 5

Workflow Clarity

An explicit 11-step sequence (gather files → pull docs → endpoints → OAuth → pagination → transformation → tags → config → getDocument → quality → report/fix) with a hard no-guessing rule and a validation feedback loop: fix all issues, then confirm `bun run lint`, clean TypeScript compilation, and re-read modified files before reporting. Checkpoints are explicit, satisfying the batch/destructive-operation validation requirement.

5 / 5

Progressive Disclosure

The body is well-organized into 11 clearly headed steps, but it is a 350-line monolithic file with no bundle structure at all (no references/, scripts/, or assets/ exist). Content that plausibly belongs in separate reference files — the per-category endpoint/pagination/tag checklists and the severity-grouped issue lists — is fully inlined, matching the anchor 'some structure but content that should be separate is inline' rather than the well-split anchor at 4.

3 / 5

Total

17

/

20

Passed

Description

53%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.

The description is concise and names a clear, specific niche, but it is a single action verb with no trigger guidance and no synonyms. Adding a 'Use when' clause and a few natural trigger phrases (audit/check/review a connector) would materially improve trigger matching and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to validate, audit, check, or review an existing knowledge base connector against its service's API documentation."

Include natural trigger synonyms users would actually say ("audit", "check", "review", "connector validation") so the skill surfaces for phrasings other than "validate".

Enumerate 2-3 of the key validation actions (e.g., cross-references endpoints, OAuth scopes, and pagination; reports issues by severity and fixes them) to improve specificity from one generic action to concrete coverage.

DimensionReasoningScore

Specificity

The description names the domain ("knowledge base connector") and one concrete action ("Validate ... against its service's API docs"), matching the anchor for domain plus 1-2 actions. It does not list the several specific actions the skill actually performs (endpoint/OAuth/pagination/tag validation, report and fix), so it is not comprehensive enough for 4.

3 / 5

Completeness

The 'what' is clear (validate an existing connector against its service's API docs) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is specific and unambiguous.

3 / 5

Trigger Term Quality

Relevant keywords are present ("validate", "connector", "knowledge base", "API docs") but common variations a user would naturally say — "audit", "check", "review connector" — are missing. This matches the anchor 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

"Validate an existing knowledge base connector" carves a fairly distinct niche (validating existing connectors rather than creating them), with only minor overlap risk against a closely related connector-creation or connector-debugging skill. It lacks the explicit distinct trigger phrasing needed for a 5.

4 / 5

Total

13

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/validate-connector/SKILL.md

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.