iii-http-endpoints

Exposes iii functions as REST API endpoints. Use when building HTTP APIs, webhooks, or inbound request handling where iii owns the route.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/iii-http-endpoints/SKILL.md

Quality

Discovery

89%

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 solid description that clearly communicates both what the skill does and when to use it, with good trigger terms covering REST APIs, webhooks, and HTTP endpoints. The main weakness is that the specificity of concrete actions could be improved—it describes the general purpose but doesn't enumerate specific capabilities like defining route handlers, middleware, or response formatting.

Suggestions

Add more specific concrete actions, e.g., 'Defines route handlers, processes HTTP requests, returns JSON responses, and configures webhook listeners' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (REST API endpoints) and a few actions (building HTTP APIs, webhooks, inbound request handling), but doesn't list concrete specific actions like defining routes, handling GET/POST methods, parsing request bodies, or returning responses.	2 / 3
Completeness	Clearly answers both 'what' (exposes iii functions as REST API endpoints) and 'when' (Use when building HTTP APIs, webhooks, or inbound request handling where iii owns the route), with an explicit 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'REST API', 'endpoints', 'HTTP APIs', 'webhooks', 'inbound request handling', and 'route'. These cover the main variations a user would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to exposing iii functions as REST endpoints with iii owning the route, which is a distinct niche. The qualifier 'where iii owns the route' helps differentiate from general API client or outbound HTTP skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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

The skill provides a well-structured overview of HTTP endpoint creation in the iii framework with clear architectural context, good cross-referencing to related skills, and useful adaptation guidance. Its main weaknesses are the lack of any inline executable code example (relying entirely on external references) and some redundancy in the boundary/usage sections. Adding a minimal complete inline example and consolidating the repeated boundary guidance would meaningfully improve it.

Suggestions

Add a minimal inline executable code example (e.g., a single GET route with registerFunction and registerTrigger) so the skill is actionable without requiring external file access.

Consolidate the 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single section to eliminate redundancy and save tokens.

Add explicit error handling guidance or validation steps (e.g., what happens with route conflicts, how to validate request bodies) to improve workflow clarity.

Remove preamble sentences like 'Use the concepts below when they fit the task' and 'Use the adaptations below when they apply' — these add no value for Claude.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundancy. The 'When to Use' and 'Boundaries' sections at the bottom repeat information already conveyed in 'Pattern Boundaries'. The 'Key Concepts' preamble ('Use the concepts below when they fit the task') and 'Adapting This Pattern' preamble are unnecessary filler. The architecture diagram and table are concise, but overall there's room to tighten.	2 / 3
Actionability	The skill provides concrete primitive names, config shapes, and response structures, but lacks inline executable code examples. It relies entirely on external reference files for working code. The 'Common Patterns' section shows code fragments but not a complete, copy-paste-ready example. A minimal inline example showing a full route registration would significantly improve actionability.	2 / 3
Workflow Clarity	The architecture section provides a clear request flow diagram, and the common patterns section lists the steps implicitly (register worker → register function → register trigger). However, there's no explicit numbered workflow sequence, no validation checkpoints, and no error handling guidance for common failure modes like route conflicts or malformed requests.	2 / 3
Progressive Disclosure	The skill references external files (http-endpoints.js, .py, .rs) and related skills (iii-http-middleware, iii-queue-processing) which is good structure. However, no bundle files were provided to verify these references exist, and the main content could benefit from a brief inline code snippet rather than deferring all executable examples to external files. The 'Pattern Boundaries' section effectively signals when to use other skills.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: iii-hq/iii
Commit: d51a06d

Reviewed: 3 days 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.