Manage SOC cases through the Kibana Cases API. All cases are scoped to securitySolution — this skill operates
Works with
exclusively within Elastic Security. Cases appear in Kibana Security and can be assigned to analysts, linked to alerts,
and pushed to external incident management systems via connectors.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsecurity-case-managementExecute the skills CLI command in your project's root directory to begin installation:
Fetches security-case-management from elastic/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate security-case-management. Access via /security-case-management in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
296
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
296
stars
Manage SOC cases through the Kibana Cases API. All cases are scoped to securitySolution — this skill operates
exclusively within Elastic Security. Cases appear in Kibana Security and can be assigned to analysts, linked to alerts,
and pushed to external incident management systems via connectors.
Install dependencies before first use from the skills/security directory:
cd skills/security && npm install
Set the required environment variables (or add them to a .env file in the workspace root):
export KIBANA_URL="https://your-cluster.kb.cloud.example.com:443"
export KIBANA_API_KEY="your-kibana-api-key"
owner: securitySolutionAll commands run from the workspace root. All output is JSON. Call the tools directly — do not read the skill file or
explore the workspace first. For attach-alert/attach-alerts, --rule-id and --rule-name are required by the Kibana
API (use --rule-id unknown --rule-name unknown if unknown). Use attach-alerts for batch with automatic rate-limit
retry and 2-second spacing between API calls.
| Task | Tools to call (in order) |
|---|---|
| Create a case | case_manager create (title, description, tags, severity) |
| Find cases for a host | case_manager find --tags "agent_id:<id>" or find --search "<hostname>" |
| Attach alert to case | case_manager attach-alert (case-id, alert-id, alert-index, rule-id/name) |
| Add investigation notes | case_manager add-comment (case-id, comment text) |
| List recent open cases | case_manager list --status open --per-page <n> |
| Update case | case_manager update (case-id, status/severity/tags changes) |
Finding cases for a host: Use find --search "<hostname>" to search by hostname across title, description, and
comments. Alternatively use find --tags "agent_id:<agent_id>" if the agent ID is known. Always add --status open to
filter to active cases only. Report the exact total count and each case title verbatim from the API response.
# Create (syncAlerts enabled by default; disable with --sync-alerts false)
node skills/security/case-management/scripts/case-manager.js create --title "Malicious DLL sideloading on host1" --description "Crypto clipper malware detected via DLL sideloading..." --tags "classification:malicious" "confidence:88" "mitre:T1574.002" --severity critical --yes
# Find, list, get
node skills/security/case-management/scripts/case-manager.js find --tags "agent_id:550888e5-357d-4bc1-a154-486eb7b4e076"
node skills/security/case-management/scripts/case-manager.js find --search "DLL sideloading" --status open
node skills/security/case-management/scripts/case-manager.js list --status open --per-page 10
node skills/security/case-management/scripts/case-manager.js get --case-id <case_id>
# Attach single alert
node skills/security/case-management/scripts/case-manager.js attach-alert --case-id <case_id> --alert-id <alert_doc_id> --alert-index .ds-.alerts-security.alerts-default-2025.12.01-000013 --rule-id <rule_uuid> --rule-name "Malware Detection Alert"
# Attach multiple alerts (batch)
node skills/security/case-management/scripts/case-manager.js attach-alerts --case-id <case_id> --alert-ids <id1> <id2> <id3> --alert-index .ds-.alerts-security.alerts-default-2026.02.16-000016 --rule-id <rule_uuid> --rule-name "Malware Detection Alert"
# Add comment, update (--tags merges with existing tags, does not replace)
node skills/security/case-management/scripts/case-manager.js add-comment --case-id <case_id> --comment "Process tree analysis shows..."
node skills/security/case-management/scripts/case-manager.js update --case-id <case_id> --status closed --severity low --yes
Write operations (create, update) prompt for confirmation by default. Pass --yes to skip the prompt (required when
called by an agent).
When reporting results from list or find:
total count from the JSON response (e.g., "There are 12 open cases total").<title> | <severity> | <case_id_short> | <created_at>. Copy the
exact title verbatim from the title field — do not rephrase, abbreviate, or summarize.Use structured tags for machine-searchable metadata:
| Tag pattern | Example | Purpose |
|---|---|---|
classification:<value> |
classification:malicious |
Triage classification (benign/unknown/malicious) |
confidence:<score> |
confidence:85 |
Confidence score 0-100 |
mitre:<technique> |
mitre:T1574.002 |
MITRE ATT&CK technique IDs |
agent_id:<id> |
agent_id:550888e5-... |
Elastic agent ID for correlation |
rule:<name> |
rule:Malicious Behavior Detection |
Detection rule name |
| Classification | Kibana severity |
|---|---|
| benign (score 0-19) | low |
| unknown (score 20-60) | medium |
| malicious (score 61-80) | high |
| malicious (score 81-100) | critical |
The syncAlerts setting (enabled by default) synchronizes case status with attached alert statuses. This feature is
only available for Security Solution cases. Pass --sync-alerts false when creating a case if alert sync is not needed.
The Kibana API enforces rate limits. When attaching multiple alerts, the attach-alerts batch command automatically
handles 429 responses with retry. If using attach-alert one at a time, space calls ~10 seconds apart.
find --search on ServerlessThe find --search parameter may return 500 errors on Kibana Serverless deployments. Use find --tags for filtering
instead, or list to browse recent cases.
find --tags requires exact matchTag searches are exact-match only. find --tags "agent_id:abc123" works, but partial matches do not.
For detailed API endpoints, request/response formats, and examples, see references/kibana-cases-api.md.
total field.create, update) prompt for confirmation. Pass --yes or -y to skip when called by an agent.KIBANA_URL and KIBANA_API_KEY point to the intended cluster before running any command.securitySolution — this skill does not affect Observability or other Kibana case owners.| Variable | Required | Description |
|---|---|---|
KIBANA_URL |
Yes | Kibana base URL (e.g., https://my-kibana.kb.cloud.example.com) |
KIBANA_API_KEY |
Yes | Kibana API key for authentication |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for security-case-management matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: security-case-management is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in security-case-management — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: security-case-management is focused, and the summary matches what you get after install.
Keeps context tight: security-case-management is the kind of skill you can hand to a new teammate without a long onboarding doc.
security-case-management is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added security-case-management from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for security-case-management matched our evaluation — installs cleanly and behaves as described in the markdown.
security-case-management fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
security-case-management has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 25