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

templates/incident.md

View on GitHub
# Incident summary format

One short summary per finished run, at `<output root>/incidents/<date>-<service>.md`. If that name is taken (another environment or a second incident the same day), append `-<env>`, then `-2`, `-3`. It is the memory a later run greps. It is not the report: link to the run directory and keep the body to a screen.

Write one when the run named a cause at any label, or when the user asks. A run that found no cause, Fast mode especially, does not create one unless asked. It is written after the user approves the record-phase diff.

## Front matter

```yaml
---
id: <date>-<service>-<env>-<short-slug>      # lowercase
date: <YYYY-MM-DD>
service: <service>
env: <environment>
siblings: [<members affected>]               # or [all]
window_utc: <start>/<end>
symptoms: [<terms from the symptom list>]
cause_category: <one term from the cause list>
cause: <one line>
deps: [<services or third parties on the failing path>]
label: <Confirmed|Likely|Assumed>                # unknown cause_category always takes Assumed
mode: <fast|deep>
time_to_cause_min: <minutes, or null>
run: runs/<run directory name>
---
```

Keep every value on one line so that a `grep` over the front matter finds it.

## Body

- What happened: two or three sentences.
- Causal chain: trigger, mechanism, symptom, each with its label.
- What found it: the query or signal that decided the case.
- What did not help: dead ends worth skipping next time.
- Follow-ups raised.

## Symptom vocabulary

Use these words, several if needed. Use `other` only when none fits.

| Group | Terms |
|---|---|
| Request outcomes | `latency`, `timeouts`, `unavailable`, `errors-5xx`, `errors-4xx`, `throughput-drop` |
| Background work | `queue-backlog`, `job-failure` |
| Resources and process health | `crash-restart`, `memory`, `cpu`, `disk`, `db-connections` |
| Correctness and money | `data-inconsistency`, `cost-spike` |
| Anything else | `other` |

## Cause vocabulary

Choose exactly one.

| Term | Meaning |
|---|---|
| `deploy` | A release of application code or its image. |
| `config` | A change to configuration, flags, limits or infrastructure definition. |
| `dependency` | A service of the same organisation that this one calls or consumes from. |
| `third-party` | A vendor or external service outside the organisation. |
| `capacity` | Load within expected bounds exceeded provisioned or configured capacity. |
| `capacity-config` | Capacity was set or scheduled away by configuration, with no load involved: desired count at zero, a scale-to-zero or stop schedule that did its job, a minimum that blocked a start. |
| `resource-exhaustion` | A finite resource ran out: memory, descriptors, connections, disk, quota. |
| `infra-event` | The platform changed under the service: instance reclaim, zone impairment, host failure, node drain. |
| `schedule` | A timed job, scheduled scaling action or maintenance window. |
| `traffic` | An unusual request pattern: a spike, a bot fleet, a retry storm. |
| `data` | The content of the data (a bad record, a size, a skew) triggered the failure. |
| `credentials-cert` | An expired or revoked credential or certificate. |
| `network-dns` | Routing, DNS or connectivity. |
| `unknown` | No cause reached `Likely`. |

## Label vocabulary

`Confirmed`, `Likely` or `Assumed`, the label of the cause as in the report. When `cause_category` is `unknown`, the label is `Assumed`: the lead hypothesis, if any, goes in the body. `Ruled out` applies to hypotheses, not to an incident.

## Lookup rules

- Search only after the run's own ranked hypotheses exist, so history cannot set the agenda. `grep` the front matter of `incidents/` for the service, each entry of `deps`, and the symptom words.
- A match becomes its own hypothesis with ID `from-history:<file>.md` (the file name exactly, extension included), even when it overlaps another one. It is a lead, never evidence, and a query of the current run has to support it.
- Past incidents are never passed to evidence workers.
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: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated 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: 196kUpdated Claude CodeCodexVerifiedInstall