add-tools

Create tool configurations for a Sim integration by reading API docs

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-tools/SKILL.md

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 skill body is highly actionable with strong, executable templates and a well-validated workflow, but it is a monolithic single-file document where large subsections could be moved into reference files. Splitting block-wiring and provenance guidance into one-level-deep references would improve progressive disclosure.

Suggestions

Move the long 'Wiring Tools into the Block' and 'Resolved Secrets and Provenance Boundaries' sections into separate reference files (e.g., BLOCK_WIRING.md, PROVENANCE.md) linked from a concise overview.

Add clearly signaled one-level-deep references for the tool-config and types-file patterns so the core SKILL.md reads as an overview with navigable detail.

Trim a few of the inline comment lines inside the code templates to push conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is detailed but largely lean and assumes Claude's competence, with only minor over-explanation that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully lean 5.	4 / 5
Actionability	It provides complete, copy-paste-ready TypeScript templates, exact file paths, concrete commands like `bun run tool-metadata:generate`, and full block-wiring examples covering common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced with explicit validation in 'Final Validation (Required)' requiring cross-reference against API docs, plus checklists before finishing and a hard 'stop short of guessing' feedback loop.	5 / 5
Progressive Disclosure	Everything is inlined in a single SKILL.md with no bundle-file references to split out the large block-wiring and provenance sections; structure exists but content that should be separate is inline and references are not clearly signaled.	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 reasonably specific and distinct but stops short of explicit trigger guidance, capping completeness and trigger quality at the midpoint. Adding a 'Use when...' clause with natural user phrasing would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when creating or updating Sim integration tool configs from API docs') to satisfy the completeness trigger requirement.

Include natural user-facing synonyms such as 'Sim tools', 'integration tools', or 'tool definitions' alongside 'tool configurations' to improve trigger-term coverage.

Optionally name a second concrete action (e.g., 'and wiring them into blocks') to push specificity toward the higher anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain ('tool configurations for a Sim integration') and one concrete action ('by reading API docs'), matching the anchor that names a domain plus 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It gives a clear 'what' but no explicit 'Use when...' clause, so per the guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'tool configurations' and 'API docs' are relevant keywords, but the phrase lacks common natural synonyms users would say and omits trigger phrasing, placing it at 'some relevant keywords but missing variations'.	3 / 5
Distinctiveness Conflict Risk	Scoping to 'a Sim integration' makes it mostly distinct from other skills with only minor overlap risk against closely related tool-authoring skills.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (506 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: 1 missing	Warning

	Total	13 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-tools/SKILL.md
Commit: 0b232eb

Reviewed: 2 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.