Appearance
Skills Manager
Part of Instructions Manager — the Skills track.
Governed agent skills for your coding agents — authored in the console, synced to disk with pm-skills.
The problem
Teams paste the same coding conventions, security rules, and review checklists into every agent tool — Claude Code, Cursor, Codex, Copilot — as loose SKILL.md files. That works until:
- Two repos drift on the same “secure coding” skill.
- Someone edits a managed skill locally and agents start following unreviewed instructions.
- A bad marketplace skill lands in production with no preview or scan gate.
- CI cannot prove which skill versions the pipeline used last Tuesday.
Agent skills are content. They need review, versioning, and a reproducible sync path — not only git copies of folders.
What Skills Manager does
elsai Skills Manager is a skill registry and sync client:
- Author and govern skills in the Prompt Manager console (project, organization, or marketplace tiers).
- Approve versions through the same review model your team already uses for prompts (project skills) or a scan-gated publish path (org / marketplace).
- Consume with the read-only CLI
pm-skills, which materializes approved skills into the folders agents already read (.claude/skills/,.agents/skills/,.github/skills/, …).
Console authoring
Create skills, edit
SKILL.md frontmatter and body, attach scripts/references, run security scans, and approve or publish versions. Tiered resolution
Project skills override organization skills, which override marketplace (global) skills of the same name. Installs pin exact SHAs until you update deliberately.
Read-only CLI
pm-skills never writes to the server. Authoring, installs, and approvals stay in the UI. A leaked key can read approved content at worst — not change it. Lockfile + drift
pm-skills.lock.json pins SHAs for reproducibility. status detects server updates and local tampering; CI can fail on drift. How it relates to Instructions Manager and Agentkit
| Product | Role |
|---|---|
| Instructions Manager | Umbrella product: prompts + skills on one platform |
| Prompts | Same console: orgs, projects, API keys. Skills live alongside prompts. |
| Skills | Skill-specific concepts, UI workflows, and the pm-skills CLI. |
| Agentkit AgentSkills | Runtime plugin that loads local SKILL.md folders your agents already use. |
Typical path: approve in Skills → pm-skills pull → Agentkit / Claude / Cursor reads the folders.
SaaS or on-prem — same CLI
SaaS
Hosted console and API. Point pm-skills at the SaaS API base URL and use your elsai_* key.
→On-Prem
Self-hosted Prompt Manager. Same CLI — set --server (or PM_SKILLS_SERVER) to your API origin. Marketplace and scanning are ops-gated flags.
→