iii-http-invoked-functions
Registers external HTTP endpoints as iii functions using registerFunction(id, HttpInvocationConfig). Use when adapting legacy APIs, third-party webhooks, or immutable services into triggerable iii functions, especially when prompts ask for endpoint maps like { path, id } iterated into registerFunction calls.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-http-invoked-functions/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-crafted description that clearly defines a specific technical capability and provides explicit 'Use when' guidance with concrete scenarios. Its main weakness is that the trigger terms are heavily technical and may not match how all users would naturally phrase their requests, though for this niche domain that may be appropriate.
Suggestions
Consider adding more natural-language trigger variations such as 'wrap an API', 'connect external service', or 'register endpoint' to improve discoverability for users who may not use the exact technical terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists concrete actions: 'Registers external HTTP endpoints as iii functions using registerFunction(id, HttpInvocationConfig)'. It specifies the exact function signature and the types of inputs (legacy APIs, third-party webhooks, immutable services). | 3 / 3 |
Completeness | Clearly answers both 'what' (registers external HTTP endpoints as iii functions using registerFunction) and 'when' (Use when adapting legacy APIs, third-party webhooks, or immutable services, especially when prompts ask for endpoint maps iterated into registerFunction calls). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'registerFunction', 'HTTP endpoints', 'webhooks', 'endpoint maps', and '{ path, id }'. However, the terminology is quite technical and niche ('iii functions', 'HttpInvocationConfig') — a user might not naturally use these exact terms, and common variations like 'register API', 'wrap endpoint', or 'function registration' are not fully covered. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to a narrow domain — registering HTTP endpoints as iii functions via registerFunction with HttpInvocationConfig. This is unlikely to conflict with other skills due to its very specific technical niche and distinct trigger patterns. | 3 / 3 |
Total | 11 / 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 is well-organized with good progressive disclosure and clear pattern selection rules that help Claude decide when to apply it. However, it lacks inline executable code examples, relying entirely on external reference files for implementation details, and the 'When to Use' / 'Boundaries' sections are redundant with earlier content. Adding at least one complete inline code snippet and removing the duplicated guidance sections would significantly improve it.
Suggestions
Add at least one complete, executable inline code example showing the endpoint list + registerFunction loop pattern, rather than deferring all code to reference files.
Remove or merge the 'When to Use' and 'Boundaries' sections into 'Pattern selection rules' and 'Guardrails' respectively, as they contain redundant information.
Add explicit validation/error handling guidance, e.g., what to check after registration and how to handle non-2xx responses from registered endpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundant sections. The 'When to Use' and 'Boundaries' sections at the bottom largely repeat what's already covered in 'Pattern selection rules' and 'Guardrails'. The 'Core model' and 'Common shape' sections are lean and useful. | 2 / 3 |
Actionability | The skill provides structural guidance (API shapes, naming conventions, auth patterns) but lacks executable code examples inline. The actual code is deferred entirely to reference files. The 'Common shape' section shows pseudocode-level patterns rather than copy-paste ready code. | 2 / 3 |
Workflow Clarity | The pattern selection rules provide clear decision logic, and the core model outlines the sequence (register then trigger), but there are no explicit validation checkpoints or error-handling feedback loops for what happens when registration fails or endpoints return non-2xx responses. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as a concise overview with clear one-level-deep references to implementation files in three languages. Navigation is straightforward with well-signaled links to JS, Python, and Rust reference files. | 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.