add-block

Create or update a Sim integration block with correct subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring. Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools.

Quality

81%

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

Quality

Content

77%

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

A highly actionable, well-sequenced skill body with strong validation feedback loops and copy-paste-ready examples. Its weaknesses are conciseness (a very long inline reference with some redundancy) and progressive disclosure (no reference files; reference-grade content is monolithically inline).

Suggestions

Move the large reference sections (SubBlock Types, Condition Syntax, Outputs Definition, BlockMeta) into separate reference files and keep SKILL.md as a lean overview with one-level-deep links.

De-duplicate the canonicalParamId constraints, which are restated across the File Input, canonicalParamId Pattern, and Complete Example sections.

Dimension	Reasoning	Score
Conciseness	The body is a ~950-line inline reference that is dense and accurate rather than padded with concepts Claude already knows, but it is verbose for a SKILL.md and repeats some material (canonicalParamId constraints restated across multiple sections) that could be tightened or offloaded to reference files.	2 / 3
Actionability	It provides concrete, copy-paste-ready TypeScript snippets, exact file paths, complete subblock templates, a fully worked example, and explicit naming conventions — fully executable guidance with specific examples.	3 / 3
Workflow Clarity	The task is sequenced (Your Task steps) and the 'Hard Rule: No Guessed Tool Outputs' plus 'Final Validation' section form an explicit validate-against-tools feedback loop with checkpoints and a checklist, matching the level-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and all content is inline in one large monolithic SKILL.md; well-organized headings help, but substantial reference material (SubBlock Types, Conditions, Outputs, BlockMeta) that would be better split into separate files is inline rather than one level deep.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 specific, complete description with an explicit trigger tied to a concrete file path and clear distinctiveness. Its main weakness is trigger-term quality, since the keywords mix strong file-path cues with internal jargon and miss common user-facing phrasings.

Suggestions

Add natural-language trigger terms a user would actually say (e.g., 'when adding or editing a Sim integration block') alongside the file-path trigger.

Soften the jargon in the trigger clause so non-experts searching for a block skill still match it.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete actions — 'subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring' — matching the level-3 anchor that lists multiple specific concrete actions rather than a vague domain mention.	3 / 3
Completeness	It explicitly answers both what (create or update a block with the listed parts) and when ('Use when working on ... or aligning a block with its tools'), matching the level-3 anchor with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	It includes a strong file-path trigger ('Use when working on `apps/sim/blocks/blocks/{service}.ts`') and terms like 'block' and 'tool wiring', but leans on internal jargon (canonicalParamId, dependsOn, subBlocks) and omits common user-facing phrasings like 'add a Sim block' or 'create an integration block'.	2 / 3
Distinctiveness Conflict Risk	'Sim integration block' scoped to a specific file path is a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (958 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

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

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