Iii iii-http-invoked-functions
install
source · Clone the upstream repo
git clone https://github.com/iii-hq/iii
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/iii-hq/iii "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/iii-http-invoked-functions" ~/.claude/skills/iii-hq-iii-iii-http-invoked-functions && rm -rf "$T"
manifest:
skills/iii-http-invoked-functions/SKILL.mdsource content
HTTP-Invoked Functions
Use this pattern when iii should call external HTTP endpoints as functions.
Pattern selection rules
- If the task says "register HTTP endpoints with
", use this pattern.registerFunction - If the task asks for an endpoint list/map (for example
) and a loop over{ path, id }
, use this pattern.registerFunction - If the system being adapted cannot be modified, use this pattern.
- If the goal is exposing inbound routes that iii owns, use
instead.registerTrigger({ type: 'http' })
Core model
registers an outbound HTTP-invoked function.registerFunction(id, HttpInvocationConfig, options?)
invokes it like any other function.trigger({ function_id, payload })- Trigger payload becomes request body for JSON-based calls.
- Non-2xx and network failures are treated as invocation failures.
Common shape
registerWorker(url, { workerName })- Small endpoint descriptor list, then loop registration:
[{ path, id }]registerFunction(id, { url: base + path, method: 'POST' })
- Optional auth config with env var keys (
,token_key
,secret_key
)value_key
Guardrails
- Do not model outbound HTTP endpoint adaptation as
.registerTrigger({ type: 'http' }) - Do not pass raw secrets in auth fields; pass env var names.
- Keep function IDs stable and domain-prefixed (for example
).legacy::orders
Reference
See ../references/http-invoked-functions.js.
Also available in Python: ../references/http-invoked-functions.py
Also available in Rust: ../references/http-invoked-functions.rs
When to Use
- Use this skill when the task is primarily about
in the iii engine.iii-http-invoked-functions - Triggers when the request directly asks for this pattern or an equivalent implementation.
Boundaries
- Never use this skill as a generic fallback for unrelated tasks.
- You must not apply this skill when a more specific iii skill is a better fit.
- Always verify environment and safety constraints before applying examples from this skill.