iii-directory

Engine introspection, workers registry proxy, and filesystem-backed skill + prompt reader for the iii engine. Every public function sits under a single directory::* namespace, split into four sub-namespaces (all MCP-agnostic):

• Skills (directory::skills::*) — markdown documents under iii://{id} plus an iii://directory/skills index. Use for "when and why to use my worker's tools".
• Prompts (directory::prompts::*) — static prompt templates listed by directory::prompts::list and read by directory::prompts::get. Parametric command templates the user invokes.
• Engine (directory::engine::*) — read-side enrichment over engine::functions::list, engine::workers::list, engine::trigger-types::list, and engine::triggers::list. "What's connected to the engine right now?"
• Registry (directory::registry::*) — HTTP proxy over api.workers.iii.dev with the same workers::{list,info} shape as directory::engine::workers::*. "What's published in the public registry?"

directory::engine::workers::* and directory::registry::workers::* share the core name / description / version fields, so a parser that touches only those keys works against either surface. The registry view also surfaces publication metadata (type, config, supported_targets, total_downloads, dependencies, optional image); the engine view adds runtime / connection state.

Skills and prompts are sourced from a single configured folder on disk (skills_folder); see the README for the install, configuration, and directory::skills::download flow.

How-tos

directory::skills::* — filesystem-backed skill reader

• directory::skills::list — enriched listing of every skill on disk (id, title, type, description, bytes, modified_at). title prefers the YAML frontmatter title: over the body H1; type is lifted from frontmatter type: (null when absent).
• directory::skills::get — read one skill body by id (returns the same id/title/type/description/modified_at as list plus body).
• directory::skills::index — short markdown index of every installed worker (one ##