iii-node-sdk

Node.js/TypeScript SDK for the iii engine. Use when building workers, registering functions, or invoking triggers in TypeScript or JavaScript.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/iii-node-sdk/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its domain (iii engine SDK), specifies the language context (Node.js/TypeScript/JavaScript), and provides explicit trigger guidance with a 'Use when' clause. The main weakness is that the specific actions (building workers, registering functions, invoking triggers) could be more concrete with additional detail about what those operations entail.

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js/TypeScript SDK for iii engine) and some actions (building workers, registering functions, invoking triggers), but these are somewhat abstract and not fully fleshed out with concrete operations.	2 / 3
Completeness	Clearly answers both what ('Node.js/TypeScript SDK for the iii engine') and when ('Use when building workers, registering functions, or invoking triggers in TypeScript or JavaScript') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'Node.js', 'TypeScript', 'JavaScript', 'SDK', 'workers', 'functions', 'triggers', and 'iii engine'. Good coverage of terms a developer would use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific combination of 'iii engine' SDK with TypeScript/JavaScript context. The mention of workers, functions, and triggers within the iii engine ecosystem creates a clear niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

57%

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

This is a solid API reference skill that effectively uses tables and concise descriptions to document the Node.js SDK surface area, with good progressive disclosure to related skills. Its main weaknesses are the lack of a complete executable example (even a minimal one) and the absence of a clear workflow showing the typical connect-register-invoke sequence. Adding a quick-start code block and tightening the meta-instruction sections would meaningfully improve it.

Suggestions

Add a complete, minimal executable example (e.g., 5-10 lines showing registerWorker → registerFunction → trigger) in a 'Quick Start' section at the top.

Add a brief numbered workflow showing the typical sequence: 1. registerWorker, 2. registerFunction, 3. trigger/registerTrigger, with notes on error handling checkpoints.

Remove or significantly trim the 'When to Use' and 'Boundaries' sections — these are meta-instructions Claude can infer and they consume tokens without adding actionable value.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good use of tables, but includes some unnecessary sections like 'When to Use' and 'Boundaries' that explain obvious meta-instructions Claude doesn't need. The 'Browser SDK' section is thin and could be folded into the pattern boundaries list. Some API descriptions are terse enough to be efficient.	2 / 3
Actionability	The skill provides API signatures and some inline usage patterns (e.g., registerFunction with handler signatures, channel usage), but lacks complete executable code examples. There's no copy-paste-ready 'hello world' or minimal working example showing registerWorker through to trigger invocation. The guidance is specific but sits between pseudocode and fully executable.	2 / 3
Workflow Clarity	There's no explicit multi-step workflow showing the sequence of connecting a worker, registering functions, and invoking triggers. The information is organized by API surface area rather than by task flow. For an SDK skill, a clear 'connect → register → invoke → handle errors' sequence with validation checkpoints would significantly improve clarity.	2 / 3
Progressive Disclosure	The skill has a clear overview structure with well-signaled one-level-deep references to related skills (iii-functions-and-triggers, iii-http-endpoints, iii-channels, etc.) in the Pattern Boundaries section. Content is appropriately split between this overview and referenced skills, and navigation is straightforward.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Commit: a7ebbbb

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