add-tools

Create tool configurations for a Sim integration by reading API docs

Quality

63%

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

77%

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

The body is highly actionable with strong workflow sequencing and validation, but it is a long monolithic document with internal redundancy and no progressive disclosure into separate reference files.

Suggestions

Move the large block-wiring reference (the 7 steps) and the V2 tool pattern into a separate reference file (e.g., references/block-wiring.md), keeping SKILL.md as an overview with a clearly signaled link.

Collapse the redundant parameter/output rules: either rely on the inline comments in the template or keep the "Critical Rules" sections, not both, to remove the duplicated visibility/type/required explanations.

Merge the "Checklist Before Finishing" and "Final Validation" sections into a single checklist to eliminate overlap and reduce tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly valuable domain-specific guidance, but it repeats itself: the inline-commented tool structure is re-explained in the "Critical Rules for Parameters/Outputs" sections, the directory structure appears twice, and the "Checklist Before Finishing" overlaps with "Final Validation", fitting 'mostly efficient but could be tightened' rather than the every-token-earns-its-place anchor 3.	2 / 3
Actionability	It provides extensive copy-paste-ready TypeScript templates (full tool config, types.ts, barrel export, and a 7-step block-wiring guide each with complete code), matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	The process is clearly sequenced (read docs -> scaffold -> generate -> register -> wire block -> validate) with an explicit "Final Validation (Required)" feedback loop and multiple checklists, matching the anchor requiring clear sequence, validation steps, and error-recovery loops.	3 / 3
Progressive Disclosure	Headers are well-organized, but the ~460-line body is entirely inline with no bundle files and no content split into reference files; since it is far over 50 lines the simple-skill exemption does not apply, so 'content that should be separate is inline' (anchor 2) fits better than the one-level-deep-reference anchor 3.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 conveys a clear purpose but is a single clause with no usage triggers, limiting its completeness and distinctiveness. All four dimensions land at 2.

Suggestions

Add a "Use when..." clause naming the user requests that should trigger this skill (e.g., "Use when adding a new service's tools to the Sim app or wiring API-backed actions into a block").

Expand the action list beyond one verb to concrete operations (e.g., "generate typed tool configs, define OAuth and visibility rules, register tools, and wire them into blocks").

Include natural trigger variations users would actually say ("add a tool", "integrate an API", "wire up a new service") to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	"Create tool configurations for a Sim integration by reading API docs" names the domain and one action but does not list multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action anchor 3.	2 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent trigger guidance, so per the judging guideline a missing trigger caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	It includes some natural terms a user might say ("tool configurations", "API docs", "Sim integration") but lacks common variations and a trigger phrase, fitting 'some relevant keywords but missing common variations' rather than the broad coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	The Sim-integration niche gives it some specificity, but the absence of distinct trigger terms means it could still overlap with other API-integration skills, matching anchor 2 over the clearly-distinct anchor 3.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-tools/SKILL.md
Commit: 6f514c1

Reviewed: about 16 hours 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.