iii-python-sdk
Python SDK for the iii engine. Use when building workers, registering functions, or invoking triggers in Python.
68
60%
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-python-sdk/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 is well-structured with a clear 'Use when...' clause that explicitly states both what the skill does and when to use it. Its main weakness is that the actions listed ('building workers', 'registering functions', 'invoking triggers') are somewhat abstract and could benefit from more concrete elaboration. The trigger terms are adequate but lean technical, potentially missing more natural user phrasings.
Suggestions
Add more concrete action descriptions, e.g., 'define worker classes, register handler functions, configure and fire event triggers' to improve specificity.
Include natural language variations users might say, such as 'iii Python library', 'iii API', or 'iii integration' to broaden trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Python SDK for the iii engine') and some actions ('building workers, registering functions, invoking triggers'), but these are somewhat abstract and not fully concrete—e.g., what does 'building workers' entail specifically? | 2 / 3 |
Completeness | Clearly answers both 'what' ('Python SDK for the iii engine') and 'when' ('Use when building workers, registering functions, or invoking triggers in Python'), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Python', 'SDK', 'workers', 'functions', 'triggers', and 'iii engine', but these are fairly technical and may miss natural user phrasing variations. A user might say 'iii Python library' or 'iii API' which aren't covered. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'iii engine', 'Python SDK', 'workers', 'registering functions', and 'invoking triggers' creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
44%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-organized reference table and good progressive disclosure to related skills, but critically lacks a complete end-to-end workflow showing how to build a worker from scratch. The examples are fragmentary rather than showing the full lifecycle, and some sections contain generic boilerplate that wastes tokens.
Suggestions
Add a complete minimal working example showing the full worker lifecycle: register_worker → register_function → register_trigger → asyncio.sleep loop, so Claude can produce working code immediately.
Remove the generic 'When to Use' and 'Boundaries' sections, which add no SDK-specific value and waste tokens.
Sequence the Key Notes into a numbered workflow or 'Getting Started' section that shows the correct order of operations for setting up a worker.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with a clean table format, but the 'When to Use' and 'Boundaries' sections are generic boilerplate that Claude doesn't need. The 'Key Notes' section has some useful non-obvious details (camelCase statusCode, event loop pattern) but also some obvious guidance. | 2 / 3 |
Actionability | Provides a useful API reference table and two concrete trigger examples, but lacks a complete executable example showing worker registration, function registration, and the full lifecycle. The install command and exports are helpful but the examples are fragments rather than copy-paste-ready working code. | 2 / 3 |
Workflow Clarity | There is no clear workflow showing how to set up a worker end-to-end (register_worker → register_function → register_trigger → keep alive). The skill lists exports and notes but never sequences them into a coherent multi-step process, which is essential for an SDK integration skill. | 1 / 3 |
Progressive Disclosure | Clean structure with a concise overview, well-signaled one-level-deep references to related skills (iii-functions-and-triggers, iii-http-middleware, etc.), and an external API reference link. Content is appropriately split between this overview and companion skills. | 3 / 3 |
Total | 8 / 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.