iii-engine-config
Configures the iii engine via iii-config.yaml — workers, adapters, queue configs, ports, and environment variables. Use when deploying, tuning, or customizing the engine.
80
75%
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-engine-config/SKILL.mdQuality
Discovery
85%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 skill description that clearly identifies its domain (iii engine configuration via iii-config.yaml), lists specific configurable elements, and provides explicit trigger conditions. The main weakness is that trigger terms could include more natural user language variations beyond the technical terms already present.
Suggestions
Consider adding more natural user trigger terms such as 'setup', 'settings', 'configure', or 'change config' to improve discoverability when users phrase requests informally.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete configuration targets: workers, adapters, queue configs, ports, and environment variables. These are concrete, actionable items rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (configures the iii engine via iii-config.yaml with specific config targets) and 'when' (explicit 'Use when deploying, tuning, or customizing the engine'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'iii-config.yaml', 'workers', 'adapters', 'ports', 'environment variables', 'deploying', 'tuning', and 'customizing'. However, it misses natural user phrases like 'change settings', 'configuration file', 'setup', or 'configure iii' which users might commonly say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'iii engine' and the specific config file 'iii-config.yaml'. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong actionable content with concrete YAML examples, CLI commands, and specific configuration patterns that are copy-paste ready. Its main weaknesses are moderate verbosity (the large primitives table and some redundant sections), and the lack of a clear step-by-step deployment workflow with validation checkpoints. The progressive disclosure is reasonable with cross-references to other skills but the inline content is heavy.
Suggestions
Add a clear sequential workflow section (e.g., '1. Create iii-config.yaml → 2. Validate config → 3. Start engine → 4. Verify health endpoint') with explicit validation checkpoints.
Move the full primitives table to a reference file and keep only the most commonly used primitives inline, linking to the full list.
Remove the 'When to Use' and 'Boundaries' boilerplate sections at the bottom — these are generic and don't add value specific to this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Key Concepts' bullet lists that restate what the config examples already show, and the 'When to Use' / 'Boundaries' sections at the bottom are boilerplate. The primitives table is extensive but much of it could be trimmed. However, the code examples and patterns are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste ready YAML config blocks, specific CLI commands (iii worker add, docker pull), exact port numbers, health check commands, and complete worker configuration examples. The guidance is specific and executable. | 3 / 3 |
Workflow Clarity | While the skill covers many configuration patterns, it lacks a clear sequential workflow for setting up or deploying the engine. There are no explicit validation checkpoints — for instance, no step to verify the config is valid before starting, no feedback loop for troubleshooting startup failures. The 'Common Patterns' section lists commands but doesn't sequence them into a deployment workflow. | 2 / 3 |
Progressive Disclosure | The skill references a full working example at '../references/iii-config.yaml' and cross-references other skills in 'Pattern Boundaries', which is good. However, no bundle files were provided to verify the reference exists, and the main body contains a large amount of inline content (the full primitives table, extensive YAML examples) that could be split into reference files for better organization. | 2 / 3 |
Total | 9 / 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.