From armoctl
Outbound integrations — alert channels (Slack/email/webhook), SIEM forwarders, Jira ticket creation. Use to wire ARMO into external workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/armoctl:armoctl-integrationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Integrations is where ARMO emits, not consumes. Alert channels deliver events; SIEM forwarders ship logs; Jira lets the agent open tickets directly.
Integrations is where ARMO emits, not consumes. Alert channels deliver events; SIEM forwarders ship logs; Jira lets the agent open tickets directly.
alert-channels — Alert channel integrationsalert-channels create [guid] — Create an alert channel
--config-file (string) JSON file with channel-specific config (optional)--guid (string) Channel GUID (optional if provided as positional)--type (string) Channel type (slack|email|webhook) (required)fields — Print the integrations resource cheatsheetjira — Jira integration commandsjira create-ticket — Create a Jira issue (ticket)
--description (string) Issue description (optional)--field (stringSlice) Extra fields as key=value (repeatable, optional)--issue-type (string) Issue type name (required)--project (string) Project key (required)--summary (string) Issue summary (required)jira fields — List Jira fields available for an issue type
--issue-type (string) Issue type ID (required)--project (string) Project key (required)jira issue-types — List Jira issue types
--project (string) Filter by project keyjira projects — List Jira projectssiem — SIEM integrationssiem create [provider] — Create SIEM integration for the given provider
--config-file (string) JSON file with provider-specific config (required)unlink [guid] — Unlink an integration by GUID| Field | Description |
|---|---|
id | Issue type ID. |
name | Issue type name (Bug, Task, Epic, ...). |
description | Description. |
subtask | Whether this is a subtask type. |
| Field | Description |
|---|---|
key | Project key (e.g. SEC). |
name | Human-readable project name. |
id | Numeric Jira project ID. |
projectTypeKey | software | service_desk | business. |
lead | Project lead identifier. |
projectTypeKey — Jira project type: software | service_desk | business. Determines which issue types and workflows are available in the project.
armoctl integrations jira create-ticket --project <key> --issue-type Bug --summary 'Incident <guid>'
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub armosec/armoctl --plugin armoctl