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

80%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

Highly actionable and well-validated content with excellent executable examples and a strong checklist, but it is a long monolithic reference that could benefit from splitting detailed material into bundle files and tightening prose-heavy sections.

Suggestions

Move the SubBlock Types Reference and Condition/DependsOn syntax into separate reference files under ./references/, keeping SKILL.md as a concise overview with one-level-deep links.

Tighten the 'OAuth deployment availability' and 'Option lists' prose into scannable bullet/checklist form to reduce token cost.

Surface external repo references (AGENTS.md → 'Canvas sentences', gmail.ts reference implementation) in a dedicated 'References' section with clear signaling rather than inline.

Dimension	Reasoning	Score
Conciseness	The ~1045-line body is mostly Sim-specific knowledge Claude lacks (so no penalty for explaining known concepts), but prose-heavy sections like 'OAuth deployment availability' and 'Option lists' could be tightened; it is not lean enough for a 4-5.	3 / 5
Actionability	Abundant copy-paste-ready TypeScript examples cover the common cases — full block config, every subBlock type, condition/dependsOn syntax, tools.config, outputs — fully executable guidance.	5 / 5
Workflow Clarity	A 'Your Task' sequence, a thorough pre-finish checklist, and a 'Final Validation (Required)' section with explicit verification steps and bun checks provide clear checkpoints; the main creation sequence is only loosely woven through the reference material, a minor gap below 5.	4 / 5
Progressive Disclosure	Good section headers give structure, but with no bundle files the entire reference (SubBlock types, condition syntax, detailed examples) is inlined in one 1000+ line file; references to repo files (AGENTS.md, gmail.ts) are buried in prose rather than presented as a clear navigation layer.	3 / 5
	Total	15 / 20 Passed

Description

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

A strong, specific description that clearly states both the capability and concrete trigger conditions, with comprehensive coverage of the block-config domain. Minor room to improve trigger synonyms and boundary clarity against sibling add-* skills.

Suggestions

Add natural synonyms to the trigger clause (e.g. 'integration', 'Sim integration') so users phrase the need more ways.

Clarify the boundary with sibling skills (e.g. 'Use for block files specifically; see /add-trigger, /add-tools, /add-selector for those concerns') to reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain (Sim integration block) and comprehensively enumerates concrete configuration aspects — 'subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('Create or update a Sim integration block with correct subBlocks...') and when ('Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools' gives good natural coverage ('block', 'tools', the file path) but misses common synonyms like 'integration' or 'Sim'; not quite the comprehensive synonym+extension level of a 5.	4 / 5
Distinctiveness Conflict Risk	The block-creation niche and concrete file path are mostly distinct, but the body references closely related skills (/add-trigger, add-tools, add-selector), indicating minor overlap risk with those sibling skills.	4 / 5
	Total	18 / 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 (1045 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/add-block/SKILL.md
Commit: 7945b29

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