Skills
The Skills pack turns recurring IoT Pulse jobs into packaged, multi-step workflows your agent can run out of the box. It is the third front-end of the Developer Integration Platform, alongside the CLI and the MCP server. Like them, it is a thin wrapper over the public API: no business logic, no new endpoints — tenant and scopes are resolved server-side from your scoped API key.
The workflows
Section titled “The workflows”| Workflow | What it does | Scopes |
|---|---|---|
| Onboard a device fleet | Enumerate the fleet, then set each device’s name, group, and metadata. | devices:read, devices:write |
| Tune thresholds for a process type | Review the groups of a process type and recommend threshold changes (advisory). | groups:read, thresholds:read, anomalies:read |
| Triage anomalies → tickets | Review open anomalies, acknowledge them, and update the existing linked tickets. | anomalies:read/write, tickets:read/write |
Two ways to run them
Section titled “Two ways to run them”As MCP prompts
Section titled “As MCP prompts”If you connect to the IoT Pulse MCP server, the three workflows are exposed as MCP prompts. Any MCP-capable client (Claude Desktop, Cursor, your own agent) can list and invoke them — the prompt expands into instructions that drive the server’s read/write tools.
onboard_device_fleet— arguments:groupId(optional),namePrefix(optional).tune_thresholds_for_process_type— argument:processType(required).triage_anomalies_to_tickets— arguments:deviceId(optional),status(defaultopen).
Your client lists them via the standard MCP prompts/list call and fetches one
with prompts/get. Authentication is the same API key you use for the MCP tools
(sent as Authorization: Bearer <key> or X-API-Key).
As portable Agent Skills (CLI)
Section titled “As portable Agent Skills (CLI)”The same workflows ship as portable Agent Skills
that drive the iotpulse CLI. Each skill’s SKILL.md lists the
exact CLI commands and the scopes it needs.
Download the skills
Section titled “Download the skills”The skills live in their own public repo,
IoT-Pulse-LLC/iotpulse-skills.
Clone it, or download it as a ZIP from GitHub:
git clone https://github.com/IoT-Pulse-LLC/iotpulse-skills.gitThen copy a skill directory into your agent’s skills location (for Claude Code,
~/.claude/skills/<skill-name>/) and ask it to run the workflow:
cp -r iotpulse-skills/onboard-device-fleet ~/.claude/skills/Capability boundaries
Section titled “Capability boundaries”These skills drive the iotpulse CLI, so they’re bounded by
the CLI’s command set — which is a subset of the public API. Today the CLI
can write device config, anomaly acknowledgements, and ticket
updates, but it does not yet ship commands to create threshold packs, groups,
shifts, or tickets. (The underlying public API and
the MCP server can do those — the CLI just hasn’t added the
commands yet.) So, when running these skills over the CLI:
- Tune thresholds is advisory: it reads current thresholds and recommends changes. Apply them in the admin app under Settings → Threshold Packs, or via the API / MCP server.
- Triage anomalies updates existing tickets only. If an anomaly has no ticket, the workflow records it for you to create one in the admin app.
A user-authored skill marketplace is not part of this release.