iii-effect-system
Builds composable, pipeable function chains on the iii engine. Use when building functional pipelines, effect systems, or typed composition layers where each step is a pure function with distributed tracing.
73
66%
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-effect-system/SKILL.mdQuality
Discovery
75%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 has a clear structure with both 'what' and 'when' clauses, and targets a very specific niche (the iii engine with functional pipelines and distributed tracing), making it distinctive. However, the specificity of concrete actions could be improved by listing more discrete capabilities, and some trigger terms lean toward jargon that users may not naturally use.
Suggestions
List more concrete actions beyond 'builds function chains'—e.g., 'define pipeline steps, compose effects, add distributed tracing spans, type-check composition layers'.
Add simpler or more common trigger term variations that users might naturally say, such as 'pipe functions', 'chain operations', 'function composition', or 'iii pipeline'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (functional pipelines on 'iii engine') and some actions ('composable, pipeable function chains'), but doesn't list multiple concrete actions—it's more of a high-level characterization than a list of specific capabilities like 'create chains, add tracing, compose effects'. | 2 / 3 |
Completeness | Clearly answers both 'what' (builds composable, pipeable function chains on the iii engine) and 'when' (Use when building functional pipelines, effect systems, or typed composition layers where each step is a pure function with distributed tracing), with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'functional pipelines', 'effect systems', 'typed composition', 'pure function', 'distributed tracing', and 'iii engine'. However, some terms are fairly niche/jargon-heavy and it's unclear if users would naturally say 'typed composition layers' or 'effect systems'; common variations or simpler synonyms are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The 'iii engine' is a very specific platform reference, and the combination of functional pipelines, effect systems, typed composition, and distributed tracing creates a narrow, distinctive niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured conceptual overview of effect system composition on the iii engine, with good progressive disclosure and clear pattern boundaries. However, it lacks inline executable code examples (deferring everything to a reference file) and could be tightened by removing redundant sections. The workflow description would benefit from explicit validation/error-handling checkpoints rather than just noting that 'errors propagate naturally.'
Suggestions
Add at least one inline executable code snippet showing a minimal 2-effect composition (e.g., parse → persist) rather than deferring all code to the reference file.
Remove or consolidate the redundant 'When to Use' and 'Boundaries' sections into the existing 'Pattern Boundaries' section to improve conciseness.
Add explicit error handling/validation guidance in the workflow — e.g., what to check after each trigger call, how to handle partial pipeline failures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the end repeat information already conveyed in 'Pattern Boundaries'. The 'Common Patterns' section partially restates what's already shown in the architecture diagram and primitives table. | 2 / 3 |
Actionability | Provides useful primitives table and architectural overview, but lacks executable code examples inline — the actual implementation is deferred entirely to a reference file. The 'Common Patterns' section lists API calls but doesn't show them in runnable context. | 2 / 3 |
Workflow Clarity | The architecture diagram shows a clear sequence of effects, and error propagation is mentioned, but there are no explicit validation checkpoints or feedback loops for when effects fail. The workflow is described at a conceptual level rather than with concrete verification steps. | 2 / 3 |
Progressive Disclosure | Good structure with a clear overview, well-organized sections, and a single-level reference to the full implementation file. The content is appropriately split between the skill overview and the reference implementation. | 3 / 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
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.