iii-browser-sdk
Browser SDK for connecting to the iii engine from web applications via WebSocket. Use when building browser-based clients that register functions, invoke triggers, or consume streams from the frontend.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong, well-crafted description that clearly identifies the skill's domain (browser SDK for iii engine), lists specific capabilities (register functions, invoke triggers, consume streams), and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and includes natural developer-facing keywords that would help Claude correctly select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'connecting to the iii engine from web applications via WebSocket', 'register functions', 'invoke triggers', 'consume streams from the frontend'. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Browser SDK for connecting to the iii engine via WebSocket, registering functions, invoking triggers, consuming streams) and 'when' (explicit 'Use when building browser-based clients that register functions, invoke triggers, or consume streams from the frontend'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'Browser SDK', 'WebSocket', 'web applications', 'browser-based clients', 'register functions', 'invoke triggers', 'consume streams', 'frontend'. Good coverage of terms a user building browser clients would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: browser-specific SDK for the iii engine via WebSocket. The combination of 'Browser SDK', 'iii engine', 'WebSocket', and 'frontend' creates a very specific scope unlikely to conflict with other skills like server-side SDKs or general web development tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 SDK reference skill with executable examples, a clear API table, and good cross-references to related skills. Its main weakness is some redundancy between Common Patterns and Quick Start, plus boilerplate meta-sections (When to Use, Boundaries) that add little value for Claude. Overall it's well-structured and actionable.
Suggestions
Remove or consolidate the 'When to Use' and 'Boundaries' sections—these are meta-instructions better suited for YAML frontmatter or skill routing, not the body content.
Merge 'Common Patterns' into the Quick Start or trim it to only show patterns not already demonstrated (e.g., TLS connection, stream URL), avoiding duplication.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like 'When to Use' and 'Boundaries' that are meta-instructions Claude doesn't need in the body. The 'Common Patterns' section partially duplicates the Quick Start example. The 'Pattern Boundaries' section is useful but could be tighter. | 2 / 3 |
Actionability | The Quick Start provides fully executable TypeScript code showing connection, function registration, and trigger invocation. The Key Exports table gives concrete API signatures. Common Patterns section provides copy-paste ready snippets for typical use cases. | 3 / 3 |
Workflow Clarity | This is a simple SDK skill (single-purpose: connect browser to engine). The Quick Start demonstrates a clear sequence: connect → register function → trigger. For a non-destructive SDK usage skill, this level of workflow clarity is appropriate and unambiguous. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with a clear link to the full API reference docs. It appropriately references related skills (iii-node-sdk, iii-realtime-streams, etc.) for adjacent concerns. Content is well-structured with clear sections and not monolithic. | 3 / 3 |
Total | 11 / 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
8921efa
- 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.