Open source agentic skills to administer Itential Platform in Claude Code, Copilot, Codex, and Cursor
AI agent skills for administering the Itential Platform: platform health, adapter and application lifecycle, workflow-engine control, users, groups, roles, service accounts, SSO, integrations and pre-built content. Works in Claude Code, Codex CLI, GitHub Copilot (CLI and VS Code) and Cursor.
| Skill | Use it for |
|---|---|
admin-platform | Day-to-day operations: health checks, start/stop/restart adapters and apps, workflow-engine workers, database indexes, system status |
admin-config | Setup and access: user accounts, groups, roles, OAuth service accounts, SSO, codeless integrations, profiles, pre-built content |
| Tool | Install |
|---|---|
| Claude Code | /plugin marketplace add itential/admin-skills then /plugin install itential-admin-skills@itential-admin-skills (same install covers the VS Code extension) |
| Codex CLI | codex plugin marketplace add itential/admin-skills then codex plugin add itential-admin-skills@itential-admin-skills (same install covers the VS Code extension) |
| GitHub Copilot in VS Code | Command Palette → Chat: Install Plugin From Source → itential/admin-skills |
| GitHub Copilot CLI | copilot plugin marketplace add itential/admin-skills then copilot plugin install itential-admin-skills@itential-admin-skills |
| Cursor | gh skill install itential/admin-skills --agent cursor --all in your project (or clone the repo and open it) |
How to check it worked, run skills, and update — per tool: docs/vendor-install.md.
Your org wants its own rules (naming, change policy, approved roles)? Set up your org's copy first and install from that instead —
docs/customization.md.
Make a folder to work in, with a .env holding your platform credentials:
mkdir my-platform && cd my-platform
cat > .env <<'EOF'
PLATFORM_URL=https://your-instance.itential.io
AUTH_METHOD=oauth
CLIENT_ID=your-client-id
CLIENT_SECRET=your-client-secret
EOF On a local/dev platform with a username and password, use AUTH_METHOD=password with USERNAME= and PASSWORD= instead.
Open your tool in that folder and ask:
"Check the health of my Itential platform."
The agent should start the admin-platform skill and report adapters, applications and their states — rather than guessing endpoints. You can also start it directly: /itential-admin-skills:admin-platform (Claude Code), $itential-admin-skills:admin-platform (Codex), /admin-platform (Copilot, Cursor).
Watch → Custom → Releases on this repo to hear about new versions, then update with your tool's command in docs/vendor-install.md. Claude Code updates on its own.
Don't edit a skill's SKILL.md (updates would overwrite it). Each skill has a custom/ folder for your org's rules:
skills/<skill-name>/
├── SKILL.md ← Itential's — never edit
└── custom/
├── org/ ← company-wide rules
├── team/ ← your team's rules
└── dev/ ← personal settings (not committed) An admin makes a private copy of this repo, the team commits markdown rules under the right skill's custom/ folder, and everyone installs from the org's copy — the rules come with every install. Step by step: docs/customization.md.
Itential publishes three skill packs. They install side by side, and each works on its own:
| Pack | Repo | Plugin | For |
|---|---|---|---|
| Builder | itential/builder-skills | itential-builder | Design, build and test automations — spec, feasibility, design, build, QA and as-built |
| Admin (this repo) | itential/admin-skills | itential-admin-skills | Platform health, adapters and applications, users, groups, roles, service accounts, SSO, integrations |
| Operator | itential/operator-skills | itential-operator-skills | Run automations, monitor jobs, diagnose and retry failures, approve manual tasks, manage triggers |
Install any of them the same way — the commands in docs/vendor-install.md, with that pack's repo and plugin name.
docs/vendor-install.md — install, run, update per tooldocs/customization.md — add your org's rules and keep them across updatesdocs/multi-vendor-architecture.md — how every harness installs from skills/, and the CI checksAGENTS.md — the guide every agent reads firstCONTRIBUTING.md — how to contribute, PR checks, and releasingCHANGELOG.md — what changed in each releaseContributions are welcome! Please read the Contributing Guide to get started. Before contributing, you'll need to sign our Contributor License Agreement. Everyone taking part follows the Code of Conduct.
This project is licensed under the GNU General Public License v3.0 — see the LICENSE file for details.