CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate-integration

Validate an existing Sim integration (tools, block, registry, and resolved-secret/model-input boundaries) against the service's API docs and Sim execution conventions

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

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

This is a highly actionable, superbly sequenced validation workflow with concrete commands, exact paths, and genuine feedback loops — the operational core is excellent. Its weaknesses are token efficiency and organization: a monolithic 533-line body with a redundant summary checklist and no progressive disclosure into reference files, loading specialized provenance/selector rules into every invocation that needs them.

Suggestions

Move the specialized rule sets (resolved-secret/model-input provenance, dynamic selectors, memory-load safety) into reference files under references/ and link them from the relevant steps, shortening the always-loaded SKILL.md footprint.

Remove or drastically trim the trailing Checklist Summary, which restates the step checklists almost line for line.

Convert the provenance section's dense prose paragraphs into terse checklist items matching the style of the rest of the document.

DimensionReasoningScore

Conciseness

The body is dense with genuinely project-specific checks and avoids explaining concepts Claude already knows, but the ~35-line trailing "Checklist Summary" duplicates the step checklists almost entirely, and the provenance section's prose is wordy. It is above level 2 because most content earns its place, and below level 4 because the duplicated summary section and verbose prose could clearly be tightened.

3 / 5

Actionability

Guidance is fully executable throughout: exact file paths, copy-paste commands ("bun run generate:tool-metadata", "bun run apps/sim/scripts/check-block-registry.ts origin/staging"), exact condition syntax examples, and concrete API patterns like "Authorization: Bearer ${params.accessToken}". As an instruction-only skill with no pseudocode, it matches the top anchor.

5 / 5

Workflow Clarity

Ten clearly sequenced steps (gather files → pull docs → validate tools/block/OAuth/deployment → report and fix) with explicit validation checkpoints and feedback loops: regenerate artifacts, re-run every check, verify tests fail without their fix ("revert it once and watch it go red"), and re-read modified files. Checklists are pervasive, satisfying the top anchor despite batch fix operations.

5 / 5

Progressive Disclosure

The skill has good section structure and clearly signals sibling-skill references (.agents/skills/memory-load-check/SKILL.md, add-integration, validate-selector), but there are no bundle files at all — the entire 533-line body, including specialized rule sets (resolved-secret/model-input provenance ~50 lines, dynamic selectors, memory-load safety) that belong in separately loaded reference files, is inlined. That matches level 3: structure present, but content that should be separate is inline.

3 / 5

Total

16

/

20

Passed

Description

66%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 specific and clearly scoped to a distinct niche, with good natural trigger terms like "validate" and "integration". Its main weakness is the complete absence of a "when to use" clause, which both caps completeness and limits trigger discoverability. Adding an explicit trigger sentence with a few synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to validate, audit, or check an existing Sim integration's tools, block, registry, or OAuth configuration."

Include natural synonyms users might say ("audit", "check", "review") alongside "validate" to broaden trigger matching.

Mention that the skill also reports and fixes the issues it finds, since that outcome coverage is currently missing from the what.

DimensionReasoningScore

Specificity

Enumerates concrete validation targets ("tools, block, registry, and resolved-secret/model-input boundaries") and two reference standards ("the service's API docs and Sim execution conventions"), going beyond the 1-2 actions of the level-3 anchor. It stays below level 5 because it uses a single action verb and omits coverage of the reporting, fixing, and artifact-regeneration work the body actually performs.

4 / 5

Completeness

The "what" is clear — validate an existing Sim integration against API docs and conventions — but there is no "Use when..." clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3. Level 4 requires both what and when, and the when is entirely absent here.

3 / 5

Trigger Term Quality

"Validate", "integration", and "API docs" are natural phrases a user would say when requesting this skill. It falls short of level 5 because common synonyms such as "audit", "check", or "review" are absent, leaving a few natural trigger terms missing.

4 / 5

Distinctiveness Conflict Risk

"Validate an existing Sim integration" carves a clear niche with specific enumerated boundaries, making it mostly distinct. It is not level 5 because the body reveals closely related sibling skills (add-integration, validate-selector) whose triggers (e.g., validating a integration's selectors) present minor overlap risk that the description does not differentiate.

4 / 5

Total

15

/

20

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 — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (533 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/validate-integration/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.