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.
85
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Critical
Do not install without reviewing
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 niche (iii engine setup) and provides explicit trigger guidance via a 'Use when' clause. The specificity of capabilities could be slightly improved by listing more concrete actions beyond general setup steps, but the domain-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iii engine) and some actions (install, set up worker, get backend running), but the actions are somewhat general setup steps rather than multiple distinct concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (install the iii engine, set up first worker, get a working backend running) and 'when' (explicit 'Use when' clause covering new project, SDK install, initial setup and configuration). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'new iii project', 'install the SDK', 'initial setup', 'configuration'. These cover common variations of how a user would ask for help getting started. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to the 'iii engine' ecosystem with distinct triggers like 'iii project', 'SDK', and 'first worker'. Unlikely to conflict with other skills due to the niche domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 getting-started skill with excellent actionability — every step is concrete and executable with full code examples in three languages. The progressive disclosure is well-handled with clear pointers to specialized skills and external docs. The main weaknesses are the lack of validation/troubleshooting steps in the workflow and some verbosity in meta-sections (When to Use, Boundaries) that could be trimmed or moved to frontmatter.
Suggestions
Add validation checkpoints after key steps — e.g., after Step 3 (verify engine is running with a health check curl), and after Step 5 (verify worker connected by checking console or engine logs).
Remove or significantly trim the 'When to Use' and 'Boundaries' sections, as these duplicate frontmatter-level concerns and consume tokens without adding actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use' and 'Boundaries' that restate frontmatter-level metadata, and the three-language examples (TypeScript, Python, Rust) add significant length. The 'Adapting This Pattern' and 'Recommended Next Steps' sections are useful but could be tightened. The opening sentence explaining what iii replaces is valuable context. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste-ready commands and code. The install, create, start, SDK install, worker code, and test curl command form a complete end-to-end workflow with concrete examples in three languages and an expected response. | 3 / 3 |
Workflow Clarity | The six steps are clearly sequenced and easy to follow, but there are no validation checkpoints or error recovery guidance beyond the initial version check. If the engine fails to start, the SDK install fails, or the worker doesn't connect, there's no troubleshooting or feedback loop. For a setup workflow that can fail at multiple points, this is a gap. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references to other skills (iii-state-management, iii-queue-processing, etc.) and external documentation links. The 'Pattern Boundaries' section explicitly directs users to more specific skills. Content is appropriately scoped to getting started without inlining advanced topics. | 3 / 3 |
Total | 10 / 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.