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.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized engine-config reference with executable examples and clear sequenced workflows, weakened mainly by redundancy between its two YAML blocks and a monolithic structure with no bundle files for progressive disclosure.

Suggestions

Consolidate the Code Example and Worker Config Format YAML blocks into one canonical example, or make the second explicitly reference the first, to remove overlapping worker configs and improve conciseness.

Deduplicate Key Concepts vs. the Runtime Workers table and Common Patterns vs. Adapting This Pattern so each fact appears once.

Move the full Worker Config Format reference and RBAC/Security details into files under references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Content is mostly dense and reference-style, but two large YAML blocks (Code Example and Worker Config Format) cover overlapping workers, and Key Concepts/table plus Common Patterns/Adapting This Pattern restate each other, so it could be tightened below the level-3 'every token earns its place' bar.	2 / 3
Actionability	Provides fully executable, copy-paste-ready YAML plus concrete commands ('iii worker add NAME[@VERSION]', 'iii worker sync --frozen', 'iii worker verify', 'docker pull iiidev/iii:latest', health-check curl) with exact ports and adapter names, matching the level-3 anchor.	3 / 3
Workflow Clarity	The Architecture section gives a clear startup sequence and the managed-worker lifecycle (add, commit config + iii.lock, verify in CI, sync after clone) includes explicit verification checkpoints ('iii worker sync --frozen', 'iii worker verify'), satisfying the level-3 clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	No references/scripts/assets bundle files exist and the ~230-line SKILL.md is monolithic, with the full Worker Config Format reference and RBAC details inlined where separate files would aid navigation, matching the level-2 'content that should be separate is inline' anchor rather than the split-and-signaled level-3.	2 / 3
	Total	10 / 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.

A well-formed, third-person description that concisely states both what it configures and when to use it, with concrete config-file and surface triggers. It closely matches the rubric's good examples with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates concrete config surfaces — 'workers, adapters, queue configs, ports, and environment variables' tied to a named file (iii-config.yaml) — matching the 'lists multiple specific concrete actions' anchor rather than the narrower level-2 'some actions'.	3 / 3
Completeness	Explicitly answers both what ('Configures the iii engine via iii-config.yaml — workers, adapters, queue configs, ports, and environment variables') and when ('Use when deploying, tuning, or customizing the engine'), matching the level-3 what-AND-when anchor.	3 / 3
Trigger Term Quality	Natural user-facing verbs 'Use when deploying, tuning, or customizing the engine' plus the concrete 'iii-config.yaml' trigger give good coverage of terms a user would actually say, satisfying the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Pinned to a named engine and config file with distinct triggers, giving a clear niche unlikely to fire for unrelated skills per the level-3 anchor.	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.