Skip to content

culiops/culiops-skills / skills/sre-investigate

sre-investigate

Unverified

FileKindSize
SKILL.mdskill md71.5 KB
access/standalone.mdmarkdown19.0 KB
agents/evidence.mdmarkdown8.1 KB
agents/helper.mdmarkdown3.9 KB
analytics/bin/logs-fetchexecutablescript229 B
analytics/bin/logs-inventoryexecutablescript209 B
analytics/bin/logs-statusexecutablescript192 B
analytics/bin/sqlqexecutablescript212 B
analytics/lib/s3logs/__init__.pyscript62 B
analytics/lib/s3logs/awscli.pyscript10.0 KB
analytics/lib/s3logs/budget.pyscript9.6 KB
analytics/lib/s3logs/cli_fetch.pyscript34.0 KB
analytics/lib/s3logs/cli_inventory.pyscript7.0 KB
analytics/lib/s3logs/cli_sqlq.pyscript18.4 KB
analytics/lib/s3logs/cli_status.pyscript3.0 KB
analytics/lib/s3logs/config.pyscript7.4 KB
analytics/lib/s3logs/convert.pyscript23.6 KB
analytics/lib/s3logs/duck.pyscript11.4 KB
analytics/lib/s3logs/layout.pyscript8.8 KB
analytics/lib/s3logs/paths.pyscript4.9 KB
analytics/lib/s3logs/redact.pyscript22.1 KB
analytics/lib/s3logs/s5.pyscript9.1 KB
analytics/lib/s3logs/sqlguard.pyscript11.8 KB
analytics/lib/s3logs/validate.pyscript4.4 KB
analytics/logs.env.exampleother4.2 KB
analytics/sql/alb/by_minute.sqlother918 B
analytics/sql/alb/lb_vs_target_status.sqlother629 B
analytics/sql/alb/status_by_target.sqlother887 B
analytics/sql/alb/summary.sqlother1.2 KB
analytics/sql/alb/target_latency_pct.sqlother1.4 KB
analytics/sql/alb/top_clients.sqlother429 B
analytics/sql/alb/top_paths_5xx.sqlother673 B
analytics/sql/cloudfront/aborted.sqlother1.1 KB
analytics/sql/cloudfront/by_day.sqlother499 B
analytics/sql/cloudfront/by_hour.sqlother489 B
analytics/sql/cloudfront/by_object.sqlother544 B
analytics/sql/cloudfront/bytes_per_viewer.sqlother1.1 KB
analytics/sql/cloudfront/cache_results.sqlother823 B
analytics/sql/cloudfront/client_concentration.sqlother707 B
analytics/sql/cloudfront/edges.sqlother434 B
analytics/sql/cloudfront/object_by_day.sqlother599 B
analytics/sql/cloudfront/range_requests.sqlother528 B
analytics/sql/cloudfront/referer_pages.sqlother393 B
analytics/sql/cloudfront/status_codes.sqlother342 B
analytics/sql/cloudfront/summary.sqlother719 B
analytics/sql/cloudfront/top_clients.sqlother353 B
analytics/sql/cloudfront/top_objects.sqlother349 B
analytics/sql/cloudfront/top_referers.sqlother492 B
analytics/sql/cloudfront/user_agents.sqlother533 B
analytics/sql/waf/asns.sqlother378 B
analytics/sql/waf/by_day.sqlother453 B
analytics/sql/waf/by_minute.sqlother314 B
analytics/sql/waf/client_keys.sqlother443 B
analytics/sql/waf/clients.sqlother521 B
analytics/sql/waf/compare_days.sqlother924 B
analytics/sql/waf/concentration.sqlother775 B
analytics/sql/waf/count_rules.sqlother556 B
analytics/sql/waf/countries.sqlother373 B
analytics/sql/waf/fingerprints.sqlother424 B
analytics/sql/waf/header_shape.sqlother425 B
analytics/sql/waf/labels.sqlother347 B
analytics/sql/waf/matched_data.sqlother530 B
analytics/sql/waf/rules_by_minute.sqlother497 B
analytics/sql/waf/summary.sqlother735 B
analytics/sql/waf/top_rules.sqlother361 B
analytics/sql/waf/uris.sqlother402 B
analytics/sql/waf/user_agents.sqlother557 B
analytics/tests/conftest.pyscript4.7 KB
analytics/tests/gen_fixtures.pyscript19.7 KB
analytics/tests/stubs/awsexecutablescript4.9 KB
analytics/tests/stubs/s5cmdexecutablescript4.5 KB
analytics/tests/test_awscli.pyscript16.0 KB
analytics/tests/test_budget.pyscript13.3 KB
analytics/tests/test_config.pyscript9.1 KB
analytics/tests/test_convert.pyscript25.9 KB
analytics/tests/test_duck.pyscript10.6 KB
analytics/tests/test_fetch.pyscript42.8 KB
analytics/tests/test_gen_fixtures.pyscript1.9 KB
analytics/tests/test_inventory.pyscript12.9 KB
analytics/tests/test_layout.pyscript9.8 KB
analytics/tests/test_named_queries.pyscript26.7 KB
analytics/tests/test_paths.pyscript3.2 KB
analytics/tests/test_redact.pyscript32.0 KB
analytics/tests/test_s5.pyscript17.8 KB
analytics/tests/test_sqlguard.pyscript10.8 KB
analytics/tests/test_sqlq.pyscript37.2 KB
analytics/tests/test_status.pyscript5.8 KB
analytics/tests/test_validate.pyscript2.9 KB
environment.template.mdmarkdown7.1 KB
playbooks/changes.mdmarkdown37.2 KB
playbooks/errors.mdmarkdown10.4 KB
playbooks/external.mdmarkdown15.4 KB
playbooks/infra-state.mdmarkdown13.7 KB
playbooks/logs-s3.mdmarkdown29.5 KB
playbooks/logs.mdmarkdown21.3 KB
playbooks/metrics.mdmarkdown39.0 KB
playbooks/other-backends.mdmarkdown7.2 KB
playbooks/traces.mdmarkdown16.2 KB
playbooks/waf.mdmarkdown17.2 KB
templates/incident.mdmarkdown3.9 KB
templates/ledger.mdmarkdown9.7 KB
templates/lesson.mdmarkdown2.7 KB
templates/profile.mdmarkdown4.5 KB
templates/report.mdmarkdown6.5 KB

environment.template.md

View on GitHub
# sre-investigate environment

Copy this file once per repo to `<output root>/environment.md` (`.culiops/sre-investigate/environment.md`, or `$CULIOPS_HOME/<workspace>/sre-investigate/environment.md`) and fill it in. It is local and never committed. The skill reads it at the start of every run; it holds facts about your estate, not method.

Rules for filling it in:

- **Names, never secrets.** Token fields hold the name of an environment variable. Never paste a token, a password or a key here.
- **Placeholders are placeholders.** Every value below is an example. Delete rows you do not have; leave nothing half-filled. An empty list means "not used", and the skill records the matching backend as a gap.
- **Defaults are neutral.** The severity scale and budgets are starting points. Replace them with your organisation's own.

## Timezone

The skill works in UTC everywhere. The report also shows your local time, taken from here. If this is empty the skill asks; it does not guess.

```yaml
timezone: <IANA zone, for example Europe/London>
```

## AWS profiles

One row per account the investigation may read. Use a read-only profile (`ReadOnlyAccess` or tighter), never an administrator one. Profiles are passed with `--profile` on every command.

```yaml
aws:
  profiles:
    - name: <profile-name>
      account: "111122223333"
      region: us-east-1
      purpose: <what runs in this account, for example "production workloads">
    - name: <profile-name>
      account: "444455556666"
      region: eu-west-1
      purpose: <for example "non-production">
```

An account you cannot read from a profile is listed under `purpose` as "no profile", so the run records a gap instead of guessing.

## Kubernetes contexts

```yaml
kube:
  contexts:
    - name: <kubeconfig-context-name>
      cluster: <cluster name>
      namespaces: [<namespace>]    # the namespaces the investigation reads; used by the write-check
      purpose: <for example "production">
```

## Datasources

One row per observability backend you want the skill to use. `id/url` is a datasource UID, a base URL, or a project slug, whichever the backend uses. `token_env` is the environment variable that holds the token. Leave it empty for backends that use your AWS or kube credentials.

```yaml
datasources:
  - backend: <prometheus | loki | tempo | grafana | sentry | cloudwatch | xray | datadog | newrelic | elastic-apm>
    name: <human name, for example "metrics (production)">
    id/url: <datasource UID or https://metrics.example.com>
    token_env: <ENV_VAR_NAME>
  - backend: <backend>
    name: <name>
    id/url: <https://logs.example.org>
    token_env: <ENV_VAR_NAME>
```

Prefer viewer-only tokens.

## Code and tickets

Application source is read by ref only: `gh` (read-only calls) and/or a local clone. The skill never runs `pull` or `checkout`.

```yaml
code:
  github_repos: [example-org/<service-repo>]
  local_clones:
    - repo: <service-repo>
      path: </absolute/path/to/clone>
```

If your tickets are readable through a read-only MCP server or an API, name the route here (variable names only): `tickets: <route and token_env>`.

## Core flows

The user-facing flows whose failure makes an incident severe. They drive the severity scale and the business-metric checks.

```yaml
core_flows:
  - name: <flow, for example "sign-in">
    # optional: how to see this flow in data
    metric: <counter or query name>
    datasource: <datasource name from above>
    key_labels: [<label>, <label>]
  - name: <flow>
```

If your organisation has an SLO or error budget for a flow, say where it lives (used first when sizing impact):

```yaml
slo:
  source: <for example "Prometheus recording rules" or "SLO dashboard URL">
  names: [<slo name>]
```

## Severity

Neutral default scale. Replace it with your organisation's scale; the skill only ever suggests a severity, the incident owner decides.

| Level | Meaning |
|---|---|
| SEV1 | A customer-facing core flow is down, or more than 5% of requests are failing. |
| SEV2 | Significant partial degradation: one feature, region or tenant affected, with a workaround or partial service. |
| SEV3 | Minor or internal impact, or a non-critical service. |
| SEV4 | Non-production only, or no impact on customers. |

## Budgets

How much one run may spend on queries, and how wide a single query may reach. These are neutral starting values, and your organisation should tune them. `queries` counts data queries against observability backends (metric, log, trace and error-tracker queries, the metered or heavy ones). Free control-plane reads (AWS describe, list, get and lookup calls, `kubectl get`/`describe`, git and `gh` reads) are logged in the query log but do not count.

```yaml
budgets:
  fast:
    queries: 20
    log_gb_scanned: 2
    cloudwatch_metric_requests: 100
  deep:
    queries: 60
    log_gb_scanned: 10
    cloudwatch_metric_requests: 500
  per_query_soft_limit_gb: 1     # a log query estimated above this is narrowed first (shorter window, one stream); never a prompt on its own
  windows:                       # widest window per query type; a wider one asks first
    log_stats: 48h               # Loki index stats, Logs Insights estimate
    log_patterns: 2h
    log_metric: 12h              # counts per minute from logs
    log_raw: 30m                 # raw lines
    trace_aggregation: 24h       # TraceQL metrics, grouped trace summaries
    trace_samples: 1h            # window for raw trace samples
    prom_quantile_range: 12h     # histogram_quantile over raw buckets (recording rules are exempt)

insights_ask_threshold_gb: 2     # a CloudWatch Logs Insights query whose padded estimate is above this always asks, in both modes
insights_estimate_factor: 10     # used only by the fallback estimate (storedBytes, a lower bound); the preferred estimate is the log group's IncomingBytes over the window
```

When the skill asks, in either mode:

- a Logs Insights query whose padded estimate (the log group's `IncomingBytes` over the window, or, as a fallback, the `storedBytes` lower bound × `insights_estimate_factor`) is still above `insights_ask_threshold_gb` after narrowing, or that has no estimate at all (this applies even in Fast mode, where read-only waves otherwise run without waiting);
- a query would take the run past its `budgets.<mode>` totals;
- a query needs a window wider than its `budgets.windows` cap.

`per_query_soft_limit_gb` never prompts by itself: a log query estimated above it is narrowed first, and runs as narrowed if none of the three conditions above applies. Keep `insights_ask_threshold_gb` at or above the soft limit, so narrowing always comes before asking. Lower `insights_estimate_factor` only after the ledgers of several runs show `bytesScanned` staying well under the padded estimate for your log groups; small or bursty groups can exceed the `storedBytes` lower bound by several orders of magnitude, so the factor alone is not a safe cap for them.

## Notes

Anything else the skill should know that does not fit above: naming conventions for log labels or service names, parallel deployments (regions, shards, tenants) and how to tell them apart, known noisy alerts. Keep it short and factual.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall