Read stream metadata, settings, queries, significant events, and attachments, and manage stream lifecycle (enable,
Works with
disable, resync) via the Kibana Streams REST API. Streams are an experimental way to manage data in Kibana — expect API
and behavior changes. This skill covers read operations and lifecycle only; create, update, delete, fork, and
other mutating operations may be added in a later version.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionkibana-streamsExecute the skills CLI command in your project's root directory to begin installation:
Fetches kibana-streams 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 kibana-streams. Access via /kibana-streams 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
Read stream metadata, settings, queries, significant events, and attachments, and manage stream lifecycle (enable, disable, resync) via the Kibana Streams REST API. Streams are an experimental way to manage data in Kibana — expect API and behavior changes. This skill covers read operations and lifecycle only; create, update, delete, fork, and other mutating operations may be added in a later version.
For detailed endpoints and parameters, see references/streams-api-reference.md.
| Item | Description |
|---|---|
| Kibana URL | Kibana endpoint (e.g. https://localhost:5601 or a Cloud deployment URL) |
| Authentication | API key or basic auth (see the elasticsearch-authn skill) |
| Privileges | read_stream for read operations; manage_stream for lifecycle APIs |
Use the space-scoped path /s/{space_id}/api/streams when operating in a non-default space. For role configuration
(Kibana feature privileges and Elasticsearch-level permissions), refer to
Streams required permissions.
GET or POST to <kibana_url>/api/streams (or /s/<space_id>/api/streams for a space).POST /api/streams/_disable, _enable, and _resync are mutating — send kbn-xsrf: true
(or equivalent) as required by your Kibana version.| Operation | Method | Path |
|---|---|---|
| Get stream list | GET | /api/streams |
| Get a stream | GET | /api/streams/{name} |
| Get ingest stream settings | GET | /api/streams/{name}/_ingest |
| Get query stream settings | GET | /api/streams/{name}/_query |
| Get stream queries | GET | /api/streams/{name}/queries |
| Read significant events | GET | /api/streams/{name}/significant_events |
| Get stream attachments | GET | /api/streams/{streamName}/attachments |
| Operation | Method | Path |
|---|---|---|
| Disable streams | POST | /api/streams/_disable |
| Enable streams | POST | /api/streams/_enable |
| Resync streams | POST | /api/streams/_resync |
Path parameters: {name} and {streamName} are the stream identifier (same value; the API docs use both names).
Ingest settings (GET /api/streams/{name}/_ingest) expose two separate lifecycle areas:
ingest.lifecycle) — Controls how long the stream's data is retained. Use
lifecycle.dsl.data_retention (e.g. "30d") for explicit retention, or lifecycle.inherit for child streams. This
is what users usually mean when they ask to "set retention", "update retention", or "change the stream's retention".ingest.failure_store.lifecycle) — Controls retention of failed documents only
(documents that did not process successfully). Users rarely need to change this unless they explicitly mention the
failure store or failed-document retention.When a user asks to set or update retention, target the stream's main lifecycle (lifecycle.dsl.data_retention),
not the failure store, unless they specifically ask about failure store or failed documents.
curl -X GET "${KIBANA_URL}/api/streams" \
-H "Authorization: ApiKey <base64-api-key>"
curl -X GET "${KIBANA_URL}/api/streams/my-stream" \
-H "Authorization: ApiKey <base64-api-key>"
curl -X GET "${KIBANA_URL}/api/streams/my-stream/queries" \
-H "Authorization: ApiKey <base64-api-key>"
# Significant events
curl -X GET "${KIBANA_URL}/api/streams/my-stream/significant_events" \
-H "Authorization: ApiKey <base64-api-key>"
# Attachments (dashboards, rules, SLOs linked to the stream)
curl -X GET "${KIBANA_URL}/api/streams/my-stream/attachments" \
-H "Authorization: ApiKey <base64-api-key>"
# Disable streams (request body per API docs) — deletes wired stream data; warn and confirm before proceeding
curl -X POST "${KIBANA_URL}/api/streams/_disable" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
# Enable streams
curl -X POST "${KIBANA_URL}/api/streams/_enable" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
# Resync streams
curl -X POST "${KIBANA_URL}/api/streams/_resync" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
Check the Streams API operation pages for request/response bodies (e.g. request body for _disable/_enable/_resync if required).
ingest.lifecycle / lifecycle.dsl.data_retention). Do not change only the failure store retention unless they
explicitly ask about the failure store or failed documents.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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: kibana-streams is focused, and the summary matches what you get after install.
kibana-streams reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in kibana-streams — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
kibana-streams is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
kibana-streams fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for kibana-streams matched our evaluation — installs cleanly and behaves as described in the markdown.
We added kibana-streams from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
kibana-streams reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in kibana-streams — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
kibana-streams has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 58