Create and manage SLOs in Elastic Observability. SLOs track service performance against measurable targets using
Works with
service-level indicators (SLIs) computed from Elasticsearch data.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionobservability-manage-slosExecute the skills CLI command in your project's root directory to begin installation:
Fetches observability-manage-slos 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 observability-manage-slos. Access via /observability-manage-slos 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
Create and manage SLOs in Elastic Observability. SLOs track service performance against measurable targets using service-level indicators (SLIs) computed from Elasticsearch data.
SLO operations go through the Kibana API. Authenticate with either an API key or basic auth:
# API key
curl -H "Authorization: ApiKey <base64-encoded-key>" -H "kbn-xsrf: true" <KIBANA_URL>/api/observability/slos
# Basic auth
curl -u "$KIBANA_USER:$KIBANA_PASSWORD" -H "kbn-xsrf: true" <KIBANA_URL>/api/observability/slos
For non-default spaces, prefix the path: /s/<space_id>/api/observability/slos.
Include kbn-xsrf: true on all POST, PUT, and DELETE requests.
| Type | API value | Use case |
|---|---|---|
| Custom KQL | sli.kql.custom |
Raw logs — good/total using KQL queries |
| Custom metric | sli.metric.custom |
Metric fields — equations with aggregations |
| Timeslice metric | sli.metric.timeslice |
Metric fields — per-slice threshold check |
| Histogram metric | sli.histogram.custom |
Histogram fields — range/value_count |
| APM latency | sli.apm.transactionDuration |
APM — latency threshold |
| APM availability | sli.apm.transactionErrorRate |
APM — success rate |
| Synthetics availability | sli.synthetics.availability |
Synthetics monitors — uptime percentage |
objective.target is a decimal between 0 and 1 (for example 0.995 for 99.5%).budgetingMethod: "timeslices".transform and ingest roles.POST .../slos/{id}/_reset when an SLO is stuck or after index mapping changes.groupBy manually.For official documentation, refer to the following resources:
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: observability-manage-slos is focused, and the summary matches what you get after install.
observability-manage-slos has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for observability-manage-slos matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend observability-manage-slos for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: observability-manage-slos is the kind of skill you can hand to a new teammate without a long onboarding doc.
observability-manage-slos has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: observability-manage-slos is focused, and the summary matches what you get after install.
observability-manage-slos reduced setup friction for our internal harness; good balance of opinion and flexibility.
observability-manage-slos fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
observability-manage-slos has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 71