iii-python-sdk

Python SDK for the iii engine. Use when building workers, registering functions, or invoking triggers in Python.

Quality

56%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/iii-python-sdk/SKILL.md

Quality

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 distinctiveness is strong due to the specific 'iii engine' domain.

Suggestions

Add more concrete action descriptions, e.g., 'define worker classes, register handler functions, configure and fire event triggers' to improve specificity.

Include natural keyword variations users might say, such as 'iii Python library', 'iii API', 'iii client', or 'iii integration' to improve 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 terms 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' and 'Python SDK' with specific concepts like 'workers', 'registering functions', and 'invoking triggers' creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

37%

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 reasonable API reference table and some useful notes about SDK quirks (camelCase, event loop keepalive), but falls short on actionability by lacking a complete end-to-end worker example. The absence of a sequenced workflow for the multi-step process of setting up a worker (connect, register, run) is a significant gap. The content is moderately concise but includes some boilerplate sections that don't add value.

Suggestions

Add a complete, executable quick-start example showing the full worker lifecycle: register_worker → register_function with an async handler → register_trigger → asyncio.sleep loop.

Structure the content as a numbered workflow: 1. Install, 2. Connect (register_worker), 3. Register functions, 4. Register triggers, 5. Keep alive — with validation notes at each step.

Remove the 'When to Use' and 'Boundaries' boilerplate sections, and deduplicate the register_trigger entry in the exports table.

Add a brief error handling note or validation step (e.g., checking connection state via on_connection_state_change before registering functions).

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with a useful table of exports, but includes some unnecessary sections like 'When to Use' and 'Boundaries' that explain things Claude can infer. The duplicate `register_trigger` entry in the table and some verbose bullet points in Key Notes could be tightened.	2 / 3
Actionability	Provides some concrete code examples for trigger/trigger_async and a clear install command, but lacks a complete executable worker example (e.g., register_worker + register_function + handler + event loop). The examples are fragments rather than copy-paste-ready working programs.	2 / 3
Workflow Clarity	There is no clear sequenced workflow for setting up a worker (connect → register functions → register triggers → keep alive). The key steps are scattered across bullet points and the table without a coherent step-by-step process, and there are no validation checkpoints.	1 / 3
Progressive Disclosure	The skill references external documentation and related skills (Pattern Boundaries section), which is good. However, with no bundle files provided, the references to other skills are cross-skill pointers rather than structured one-level-deep file references. The inline content could benefit from a quick-start section separated from the reference table.	2 / 3
	Total	7 / 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.