iii-http-middleware
Registers engine-level middleware functions that run before HTTP handlers. Use when adding authentication, request logging, rate limiting, or any pre-handler logic to HTTP endpoints.
83
78%
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-http-middleware/SKILL.mdQuality
Discovery
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.
This is a strong skill description that concisely covers what the skill does (registers engine-level middleware), when to use it (authentication, logging, rate limiting, pre-handler logic), and uses proper third-person voice. It includes natural trigger terms and is clearly distinguishable from related but different skills like HTTP routing or endpoint creation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'registers engine-level middleware functions', 'authentication', 'request logging', 'rate limiting', 'pre-handler logic to HTTP endpoints'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Registers engine-level middleware functions that run before HTTP handlers') and when ('Use when adding authentication, request logging, rate limiting, or any pre-handler logic to HTTP endpoints') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'middleware', 'authentication', 'request logging', 'rate limiting', 'HTTP handlers', 'HTTP endpoints', 'pre-handler logic'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to engine-level middleware for HTTP handlers, with distinct triggers like 'middleware', 'pre-handler logic', 'rate limiting'. This is a well-defined niche unlikely to conflict with general HTTP routing or endpoint creation skills. | 3 / 3 |
Total | 12 / 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 is a reasonably well-structured middleware skill that clearly explains the mental model (continue/respond, chain ordering, short-circuiting) and provides good progressive disclosure to a reference implementation. Its main weaknesses are the lack of a complete inline executable example and some redundant boilerplate sections (When to Use, Boundaries) that consume tokens without adding unique value.
Suggestions
Include a minimal but complete inline executable example showing at least one middleware function registered and attached to a trigger, rather than relying entirely on the external reference file.
Remove or consolidate the 'When to Use' and 'Boundaries' sections — they contain generic boilerplate that Claude doesn't need and that overlaps with 'Pattern Boundaries'.
Add a brief troubleshooting or validation note, e.g., how to verify middleware is executing in the expected order or how to diagnose a middleware that silently fails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate that doesn't add value. The 'Pattern Boundaries' section also partially overlaps. The core technical content is reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete code snippets for common patterns (return values, header access, trigger config) but lacks a complete, executable inline example. It defers to an external reference file for the full working implementation, so the skill itself only has fragments rather than copy-paste-ready code. | 2 / 3 |
Workflow Clarity | The architecture diagram shows the execution flow clearly, and the key concepts explain the continue/respond short-circuit logic. However, there are no explicit validation steps or error-handling guidance — e.g., what happens if middleware throws, how to test middleware is correctly attached, or how to debug ordering issues. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections and a single-level reference to the full implementation file (../references/http-middleware.js). Content is appropriately split between the overview here and the detailed reference, with clear navigation. | 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.