iii-engine-config
Configures the iii engine via iii-config.yaml — modules, adapters, queue configs, ports, and environment variables. Use when deploying, tuning, or customizing the engine.
72
65%
Does it follow best practices?
Impact
Pending
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 well-structured skill description that clearly identifies its domain (iii engine configuration), lists specific configurable elements, and includes an explicit 'Use when' clause. Its main weakness is that trigger terms could be broader to capture more natural user phrasings like 'settings', 'setup', or 'config file'. Overall it is a strong description with minor room for improvement in keyword coverage.
Suggestions
Add natural keyword variations such as 'settings', 'setup', 'configuration file', or 'config' to improve trigger term coverage for users who may not use the exact product terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring modules, adapters, queue configs, ports, and environment variables. These are distinct, tangible configuration elements rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (configures iii engine via iii-config.yaml — modules, adapters, queue configs, ports, environment variables) and 'when' (Use when deploying, tuning, or customizing the engine) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'iii-config.yaml', 'modules', 'adapters', 'ports', 'environment variables', 'deploying', 'tuning', and 'customizing'. However, it misses natural user variations like 'configuration file', 'settings', 'setup', 'config', or 'YAML config', and the product-specific term 'iii engine' limits discoverability for users who might phrase requests differently. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'iii engine' and the specific config file 'iii-config.yaml'. This is unlikely to conflict with other skills since it targets a very specific configuration domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides decent reference material for iii engine configuration with good progressive disclosure and boundary definitions, but falls short on workflow clarity — there's no step-by-step deployment or configuration workflow with validation checkpoints. Actionability is moderate; concrete snippets exist but are fragmented rather than forming a complete executable example. Some sections contain unnecessary verbosity and generic guidance that Claude doesn't need.
Suggestions
Add a clear numbered workflow for creating/modifying an engine config: e.g., 1) Create iii-config.yaml with required modules, 2) Install workers via CLI, 3) Start engine with --config flag, 4) Validate with health check endpoint, 5) If health check fails, check logs and fix config.
Include a minimal but complete inline iii-config.yaml example (even if abbreviated) rather than only deferring to the external reference file, so Claude has a copy-paste starting point.
Remove the generic 'When to Use' and 'Boundaries' sections at the bottom — these repeat boilerplate guidance that doesn't add value. The 'Pattern Boundaries' section already handles scope delineation well.
Add a validation/verification step after engine startup (e.g., expected log output or health check response) to provide a feedback loop for configuration errors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use' and 'Boundaries' that repeat generic guidance Claude already knows. The 'Architecture' paragraph and 'Key Concepts' section contain explanatory prose that could be tightened. However, the common patterns and worker system sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete CLI commands and YAML snippets (worker config blocks, iii.toml format, common CLI invocations), but lacks a complete, copy-paste-ready iii-config.yaml example inline. The reference implementation is deferred to an external file, and the 'Common Patterns' section lists fragments rather than executable configurations. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for setting up or deploying an engine configuration. Steps like creating the config, validating it, starting the engine, and verifying health are scattered as bullet points rather than an ordered process. No validation checkpoints or error recovery steps are provided for what is essentially an infrastructure deployment task. | 1 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references: the full reference config is linked, and pattern boundaries clearly direct to specific related skills (iii-http-endpoints, iii-queue-processing, etc.) for deeper topics. Content is appropriately split between overview and external references. | 3 / 3 |
Total | 8 / 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.