SKILL.md files to the platform during install()) and pull (download platform skills to disk).
At runtime, the Skill Router is what your agent talks to — it picks which skills to load on every query and emits the telemetry that powers per-skill effectiveness. This page covers the SDK surface; the Router page covers strategies, response shape, and the routing-id → trace join.
Sync skills from code to platform
skill_dirs argument is supported by all framework install() calls — OpenAI Agents, LangChain, LlamaIndex, etc.
Pull skills from platform to disk
Pull a public skill — no signup required
For consumers who just want to read a published skill without forking it into an org, the CLI’spull command works against the public registry
endpoint with no auth:
pull is read-only — no fork is created, no activation telemetry is
recorded. Use install() (Python) once you sign up to get the full
lifecycle. In the SDK, install() = fork + write SKILL.md to disk
(plus per-trace activation tracking); use fork() for the workspace copy
without the disk write.
SkillRouter — full CRUD
For programmatic skill management, instantiate SkillRouter directly:
What’s next
Skills guide
File format, registry, and SkillScore for skill effectiveness.
Skills Observability tutorial
Real-world example of measuring skill impact with experiments.