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

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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 highly actionable, well-sequenced getting-started guide with executable code across three languages and clear navigation to sibling skills. Its main weakness is length and some redundancy among the trailing meta sections, which keeps conciseness below the top anchor.

Suggestions

Consolidate the overlapping 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single concise boundaries block to reduce redundancy and token cost.

Consider collapsing the three near-identical language examples into one primary example with a short table or brief per-language snippets for the others, trimming the longest section of the file.

Move the external 'Key Resources' link list to the end or a reference section to keep the core install-and-run workflow unbroken.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient with concrete code rather than concept explanations, but the three full language implementations plus the overlapping 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections could be tightened. Not a 3 because the trailing meta sections repeat each other and the frontmatter; not a 1 because there is no padded explanation of concepts Claude already knows.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code in TypeScript, Python, and Rust plus concrete shell commands and a curl test with expected output, matching the executable-anchor example.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with an explicit verification checkpoint ('Verify it installed: iii --version') and a 'Test It' step; no destructive or batch operations are present that would require a validate-fix-retry loop.	3 / 3
Progressive Disclosure	No bundle files exist, but the body is well-organized into clear sections and points to one-level-deep references (sibling iii skills and external doc URLs) that are clearly signaled in 'Recommended Next Steps' and 'Pattern Boundaries', satisfying the simple-skill allowance for a 3.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is concise, concrete, and fully covers both capabilities and explicit trigger conditions in third-person voice. It is a strong example with no notable gaps.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Install the iii engine, set up your first worker, and get a working backend running'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what (install engine, set up worker, run backend) and when via the 'Use when a user wants to...' clause, satisfying the what-AND-when anchor.	3 / 3
Trigger Term Quality	Includes natural user phrasings ('start a new iii project', 'install the SDK', 'initial setup and configuration') that a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to a distinct iii-setup niche with iii-specific triggers, making it unlikely to fire for unrelated skills; third-person voice is used throughout.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Commit: d7ae816

Reviewed: 1 day 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.