iii-node-sdk
Node.js/TypeScript SDK for the iii engine. Use when building workers, registering functions, or invoking triggers in TypeScript or JavaScript.
65
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-node-sdk/SKILL.mdQuality
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 niche (iii engine SDK for Node.js/TypeScript) and provides explicit trigger guidance. The 'Use when...' clause with specific actions and language mentions makes it easy for Claude to select appropriately. The main weakness is that the specific actions (building workers, registering functions, invoking triggers) could be slightly more concrete with examples of what those 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 high-level and could be more concrete with specific examples of what those actions entail. | 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 strong natural keywords users would say: 'Node.js', 'TypeScript', 'JavaScript', 'SDK', 'workers', 'registering functions', 'invoking triggers', and 'iii engine'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'iii engine' reference combined with the SDK context and specific actions (workers, triggers, registering functions). Unlikely to conflict with generic Node.js or TypeScript skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves as a lightweight API reference card but critically lacks any executable code examples or workflow guidance. While the table format is efficient for listing APIs, the absence of a quick-start code snippet (e.g., connecting a worker and registering a function) severely limits actionability. The boilerplate 'When to Use' and 'Boundaries' sections consume tokens without adding value.
Suggestions
Add a Quick Start section with a complete, executable example showing `registerWorker` → `registerFunction` → `trigger` flow in TypeScript
Remove or drastically shorten the 'When to Use' and 'Boundaries' sections, which are meta-instructions Claude doesn't need
Add a minimal workflow sequence (e.g., 1. Install, 2. Register worker, 3. Register function, 4. Test with trigger) with concrete code at each step
Include at least one concrete RBAC auth function example to make the AuthResult fields table actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The API table and RBAC fields are efficient reference material, but the 'When to Use' and 'Boundaries' sections are boilerplate that Claude doesn't need—these meta-instructions about when to apply the skill add little value and pad the content. | 2 / 3 |
Actionability | There is no executable code anywhere in the skill—no import statement, no initialization example, no working snippet. The API table lists function signatures but without a concrete usage example, Claude cannot copy-paste anything to get started. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow showing how to initialize the SDK, register a worker, register a function, and invoke it. The skill is purely a reference table with no step-by-step process or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The 'Pattern Boundaries' section provides clear one-level-deep references to related skills, and the external docs link is helpful. However, there are no bundle files to support the references, and the inline API tables could benefit from a separate detailed reference file rather than being listed without examples. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%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
d51a06d
- Reviewed
Table of Contents
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.