se-observability

Name: se-observability
Author: valesordev

SE observability query and reporting conventions

by valesordev(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from valesordev/vagabond.valesordev.com (.cursor/rules/se-observability.mdc). Copyright stays with the author.

SE Observability Rule

For observability analysis, require explicit time windows in prompts and summaries (for example: last 15m, 1h, 24h).
Name the datasource explicitly in investigation queries (for example: using loki, using prometheus).
Keep outputs evidence-first: facts, impact, likely cause, and next diagnostic step.

Query Construction Requirements

Prefer one investigative objective per query.
Include scope labels when relevant (service, environment, region).
Use reproducible CLI patterns for grafana-assistant in non-interactive mode (--json for structured output).

Reporting Format

State the time range and datasource first.
Quantify impact (counts, rates, latency percentiles, or affected entities).
Separate observed evidence from interpretation.
End with a concrete next action if uncertainty remains.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

valesordev-vagabond-valesordev-com-se-observability-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "valesordev-vagabond-valesordev-com-se-observability-rule",
  "kind": "skill",
  "name": "se-observability",
  "description": "SE observability query and reporting conventions",
  "publisher": "valesordev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "data_analysis"
    ],
    "tags": [
      "skill-md",
      "github-cursor-rules"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "SE observability query and reporting conventions"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-cursor-rules",
      "repository": "https://github.com/valesordev/vagabond.valesordev.com",
      "path": ".cursor/rules/se-observability.mdc",
      "ref": "7ef82be80bf1b45856f068260146ea5053e6627b",
      "url": "https://github.com/valesordev/vagabond.valesordev.com/blob/7ef82be80bf1b45856f068260146ea5053e6627b/.cursor/rules/se-observability.mdc",
      "key": "valesordev/vagabond.valesordev.com/.cursor/rules/se-observability.mdc"
    },
    "applies_to": "se/**"
  },
  "instructions": "# SE Observability Rule\n\n- For observability analysis, require explicit time windows in prompts and summaries (for example: last 15m, 1h, 24h).\n- Name the datasource explicitly in investigation queries (for example: using loki, using prometheus).\n- Keep outputs evidence-first: facts, impact, likely cause, and next diagnostic step.\n\n## Query Construction Requirements\n\n- Prefer one investigative objective per query.\n- Include scope labels when relevant (service, environment, region).\n- Use reproducible CLI patterns for `grafana-assistant` in non-interactive mode (`--json` for structured output).",
  "cost": {
    "context_tokens": 213
  }
}

Fetch it by URL: GET /api/v1/registry/valesordev-vagabond-valesordev-com-se-observability-rule/manifest?version=1.0.0