iii-getting-started

Install the iii engine, set up your first worker, and get a working backend running. Use when a user wants to start a new iii project, install the SDK, or needs help with initial setup and configuration.

Quality

83%

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

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

The body is a strong getting-started guide: executable across three languages, clearly sequenced with verification steps, and well-linked to deeper sibling skills. The main weakness is mild redundancy from the triple-language examples and several overlapping boundary/scoping sections.

Dimension	Reasoning	Score
Conciseness	Mostly lean with code-first guidance and minimal concept explanation, but the full TypeScript/Python/Rust worker examples are partly redundant and the several boundary-related sections ('Pattern Boundaries', 'When to Use', 'Boundaries') overlap, so it is not a 5.	4 / 5
Actionability	Fully executable and copy-paste ready — concrete install/create/compose commands, per-language SDK install lines, complete worker code in three languages, and a test curl with expected response covering the common cases.	5 / 5
Workflow Clarity	Clear Step 1–6 sequence with explicit checkpoints ('Verify it installed: iii --version' and the expected curl response); not a 5 because there is no error-recovery feedback loop if verification fails, though setup is non-destructive so this is a minor gap.	4 / 5
Progressive Disclosure	Well-organized overview with one-level-deep pointers to sibling skills (iii-core-primitives, iii-sdk-reference) and external doc URLs in dedicated sections; no bundle files exist, and the multiple overlapping boundary sections keep it just short of 5.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is strong: third-person voice, concrete actions, and an explicit 'Use when' clause covering both what and when. Minor improvements possible in trigger-term synonyms and sharper separation from sibling iii skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Install the iii engine, set up your first worker, and get a working backend running' — with only minor coverage gaps; not a 5 because scope is limited to initial setup rather than comprehensive capability listing.	4 / 5
Completeness	Explicitly answers both what ('Install the iii engine, set up your first worker, and get a working backend running') and when ('Use when a user wants to start a new iii project, install the SDK...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases 'start a new iii project, install the SDK, or needs help with initial setup and configuration' give good keyword coverage; falls short of 5 because 'initial setup and configuration' is somewhat generic and lacks synonyms a user might actually say.	4 / 5
Distinctiveness Conflict Risk	The product-specific 'iii' niche and setup-only scope make it mostly distinct with minimal conflict risk; not a 5 because 'set up your first worker' could lightly overlap with a sibling core-primitives skill.	4 / 5
	Total	17 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Path: skills/iii-getting-started/SKILL.md
Commit: a4e03dd

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