New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Guidewire Observability And Incident Response

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and…

MITAuto-check passedDevOps & Cloud

Install Guidewire Observability And Incident Response

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-observability-and-incident-response -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace guidewire-observability-and-incident-response --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/guidewire-observability-and-incident-response .claude/skills/guidewire-observability-and-incident-response && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
guidewire-observability-and-incident-response
GitHub stars
2.8k
Token cost
~3.1k tokens
SKILL.md length
1,033 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and…

  • Works in 5 steps: Define SLIs that measure user-visible… → Burn-rate-based alerting, not threshold… → Top-five triage trees → …
  • Designing a dashboard for a new integration
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Reaches github.com; needs GW_CLIENT_SECRET

What it does

Guidewire Observability And Incident Response is an agent skill from jeremylongshore/tons-of-skills-marketplace. Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and never for transient noise; triage 401 spikes, 409 storms, 429 saturation, scope drift, and Gosu OOM cascades from signal to recovery in 15 minutes or less. Use when designing a dashboard for a new integration, writing the on-call runbook, or running a post-incident review. Trigger with "guidewire observability"…

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/API_REFERENCE.md` and `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Incident response, Site reliability engineering and Observability. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Designing a dashboard for a new integration
  • Writing the on-call runbook
  • Running a post-incident review
  • With guidewire observability

Example prompts

  • “guidewire observability”
  • “guidewire slo”
  • “guidewire on-call”
  • “/guidewire-observability-and-incident-response”

Requirements

  • A credential in GW_CLIENT_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*), Bash(jq:*), Grep, Glob

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Define SLIs that measure user-visible behavior
  2. Burn-rate-based alerting, not threshold alerting
  3. Top-five triage trees
  4. Recovery playbooks (top 5 incident classes)
  5. Post-incident review template (PIR)

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)
    • Bash(jq:*)
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, sql and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    Also links to:

    • sre.google
    • response.pagerduty.com
    • gcc.guidewire.com
    • brendangregg.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GW_CLIENT_SECRET

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Guidewire Observability And Incident Response loads about 3.1k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 165 tokens; SKILL.md has 1,033 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,033 words, ~3,128 tokens.

Download SKILL.mdSave it as .claude/skills/guidewire-observability-and-incident-response/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
guidewire-observability-and-incident-response
description
Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and never for transient noise; triage 401 spikes, 409 storms, 429 saturation, scope drift, and Gosu OOM cascades from signal to recovery in 15 minutes or less. Use when designing a dashboard for a new integration, writing the on-call runbook, or running a post-incident review. Trigger with "guidewire observability", "guidewire slo", "guidewire on-call", "guidewire 401 spike", "guidewire 409 storm", "guidewire incident".
allowed-tools
Read, Write, Edit, Bash(curl:*), Bash(jq:*), Grep, Glob
compatibility
Designed for Claude Code
version
1.26.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
guidewire, observability, sli-slo, incident-response, on-call, runbook

Guidewire Observability and Incident Response

Overview

Run a production Guidewire Cloud API integration with the dashboards, alerts, and runbooks an on-call engineer can act on at 3am. This skill consolidates the operational layer: what to measure, what to alert on, how to triage the top five incident classes, and how to close the loop with a post-incident review that prevents recurrence rather than performing root-cause theater.

Five operational failures this skill prevents:

  1. Vanity dashboards — graphs of total request count, no per-endpoint p99, no SLI burn rate; on-call sees green during a real outage because the right thing was never measured.
  2. Alert fatigue — every transient 5xx pages someone; in three weeks the team mutes the channel; a real incident two weeks later goes unnoticed for an hour.
  3. No triage tree — on-call wakes up to "401 spike", does not know whether to rotate a secret, restart the integration, or call GCC; loses 20 minutes Googling.
  4. Skipped post-incident review — the same root cause produces three incidents in a quarter because no one wrote down the action items from the first one.
  5. Common-errors table living in nine Slack threads — operators cannot find the recovery for an error they have seen before, ask the same question in #ops, the answer takes 45 minutes.

Prerequisites

  • A working integration emitting structured logs and metrics to a backend (Datadog, Grafana+Prometheus, New Relic, Splunk, or equivalent)
  • Access to a paging system (PagerDuty, Opsgenie, VictorOps) with on-call rotations defined
  • The integration_audit table from guidewire-security-and-rbac populated — incident triage depends on knowing what the integration tried to do
  • correlation_id propagated end-to-end through every Cloud API call

Instructions

Build the operational layer in this order. Each step targets one of the five operational failures listed in Overview.

1. Define SLIs that measure user-visible behavior

Track what users care about, not what is easy to measure. For a Guidewire integration, the SLIs that matter:

SLIMeasurementTarget
Token-endpoint availabilitysuccess rate of /oauth/token over a rolling 5min window≥99.9%
Cloud API write success2xx rate on POST/PATCH calls, excluding 4xx caller errors≥99.5%
Bind success ratebound / quoted ratio over rolling 1h, excluding referrals≥98%
FNOL intake p99 latencyend-to-end time from inbound event to claim.created log≤2s
Quote-to-bind median latencymedian time from quote-call to bind-success≤30s

5xx from upstream Cloud API counts against availability; 4xx from caller bugs (validation failures, scope mismatches) does not — those are caller errors, not integration outages. Distinguishing the two is the single biggest cause of either alert fatigue or missed incidents, depending on which way the bias goes.

2. Burn-rate-based alerting, not threshold alerting

Alerting on "error rate > 1%" pages the on-call every time a transient 502 happens. Alert on SLO burn rate instead — the rate at which the error budget is being consumed.

Fast burn:   2% error budget consumed in 1 hour       → page immediately
Slow burn:   5% error budget consumed in 6 hours      → page during business hours
Trickle:     10% error budget consumed in 3 days      → ticket, not page

A 5-minute outage that consumes 1% of the monthly budget should not page; a 20-minute outage that consumes 4% should. Burn-rate alerts encode this naturally.

3. Top-five triage trees

Each tree is the ~5-step decision sequence on-call follows from signal to recovery. Memorize the entry signal; the body is in the runbook.

T1: 401 spike on Cloud API calls

401s > 1% for 5min
├─ Check token age in cache: is the integration refreshing? → if no, restart token-cache process
├─ Decode a recent token, verify exp > now + 60s         → if no, clock skew or aggressive proxy caching
├─ Check GCC: is the Service Application enabled?         → if no, talk to tenant admin
└─ Check secret-rotation history: was a secret rotated in the last 24h? → if yes, run dual-secret swap or restart

T2: 409 storm on PATCH calls

409s > 5% for 5min
├─ Are concurrent writers expected? → if yes, scale checksum round-trip retry budget
├─ Is one resource-id producing all 409s? → if yes, it's a hot key; coordinate writes via queue
└─ Is the client retrying the bare PATCH instead of the GET-PATCH cycle? → fix the retry layer

T3: 429 saturation on Cloud API or Hub

429s > 1% for 10min
├─ Is the Hub /oauth/token endpoint 429ing? → token cache missing single-flight gate; deploy fix immediately
├─ Is the data-plane API 429ing? → check tenant quota in GCC, request increase if legitimate growth
└─ Is one customer driving the saturation? → tenant-side rate limit on the integration's intake

T4: Scope drift detected

Scope-drift alert from auth refresh
├─ What scope is missing? → check GCC > Identity & Access > Applications > [app] > Permissions
├─ Was a permission removed by a tenant admin? → coordinate; restore or accept loss of capability
└─ Was a scope renamed in a tenant config push? → update GW_SCOPES env, redeploy

T5: GUnit / runServer OOM (dev or staging)

OOMKilled or heap dump generated
├─ Is sample data set abnormally large? → reset dev DB, reload fixtures
├─ Is a recent change loading too many entities (no pagination, no filter)? → revert; add limit
└─ Is the JVM under-provisioned? → bump -Xmx in gradle.properties; restart
4. Recovery playbooks (top 5 incident classes)

Each playbook is one page in the on-call runbook. Concrete commands, not prose.

markdown
## Playbook: 401 spike — secret rotation suspected
1. Rotate in GCC > Identity & Access > Applications > [app] > Generate Secret
2. sops secrets.prod.<tenant>.sops.yaml  # set new GW_CLIENT_SECRET (and SECONDARY = old)
3. git commit -m "rotate(secrets): incident-driven rotation $(date -Iseconds)"
4. Trigger deploy of token service
5. Confirm token claims show iat > rotation timestamp: kubectl exec ... -- /token-debug
6. After 24h zero failures from primary: remove SECONDARY
7. Open audit row with reason="incident-401-spike"

Each playbook ends with an audit-row insert so the next post-incident review has the full timeline.

5. Post-incident review template (PIR)
markdown
# PIR: <date> — <one-line summary>

## Timeline
- HH:MM — first signal (alert link, dashboard screenshot)
- HH:MM — on-call paged
- HH:MM — root cause identified
- HH:MM — mitigation applied
- HH:MM — confirmation of recovery

## SLO impact
- Error budget consumed: X%
- Customer-impacting requests: N
- Compliance impact: <yes / no — if yes, NAIC notification window>

## Root cause
<the actual root cause, not a symptom; use 5-whys but don't perform; one paragraph max>

## What worked
<what the team did right; preserve these>

## What didn't
<what slowed the response; this drives action items>

## Action items (each with owner + target date)
- [ ] OWNER, BY: <date> — <concrete change>
- [ ] OWNER, BY: <date> — <concrete change>

## Recurrence prevention
<the one change that makes this exact incident impossible next time, not "be more careful">

The discipline is the action items having owners and dates. PIRs without those are theater.

Show full SKILL.md (431 more words)Show less

Output

A production-grade observability layer ships with all of the following:

  • A dashboard showing the five SLIs with their targets and current burn rate; one panel per SLI, each linked to the underlying logs/metrics query.
  • Burn-rate-based alerts wired to the paging system; fast-burn pages immediately, slow-burn opens a ticket, trickle goes to a weekly review.
  • Five triage trees memorized by every on-call rotation member; the entry signal is the alert title, the body is the runbook.
  • Five recovery playbooks one-page each, kept in the integration repo (so they version with the code), linked from each alert.
  • A PIR template applied to every incident with SLO impact > 0; action items tracked in the work-management system with owners and dates.

Examples

Example 1 — Datadog burn-rate monitor (SLO target 99.5%)
text
# error_budget = 0.5%/month = ~3.6h/month
# fast-burn: 2% budget in 1h → page
sum:trace.http_request.errors{service:guidewire-integration}.as_count() /
sum:trace.http_request.hits{service:guidewire-integration}.as_count() > 0.144   # 14.4x normal
Example 2 — Audit-table query for triage
sql
-- "What was the integration trying to do during the 401 spike?"
SELECT correlation_id, actor, api_method, api_path, status_code, reason, at
FROM integration_audit
WHERE at BETWEEN '2026-04-15T03:00:00Z' AND '2026-04-15T03:30:00Z'
  AND status_code = 401
ORDER BY at;
yaml
# Alert config
title: "GW Cloud API 401 spike"
runbook: https://github.com/acme/guidewire-integration/blob/main/runbooks/401-spike.md
priority: P1
escalation: "platform-oncall"

The on-call clicks the runbook link from the page; the runbook is in the repo so it versions with the code; updates land in PRs reviewed like any other change.

Error Handling

SymptomFirst checkLikely cause
401 spike on Cloud APItoken cache agereactive refresh, clock skew, secret rotation in flight
409 storm on PATCHconcurrent writers + retry patternclient retrying bare PATCH instead of GET-then-PATCH
429 on /oauth/tokensingle-flight gate active?thundering herd refresh from a stampede on token expiry
429 on data-plane APIper-tenant quotaanother integration sharing the tenant quota; growth past quota
403 Forbidden despite valid tokenscope-drift gatetenant admin removed a permission
PKIX path building failedcert chain in JVM trust storeprivate-CA cert renewal not propagated
Gosu OOM in productionrecent deploy + heap dumpunbounded entity load (missing filter or pagination)
FNOL p99 latency spikeupstream lookup latencyexternal policy-resolution service degraded
Bind success rate drops below SLOUW-issue volume + product mixnew product or new broker producing high-referral volume; not an outage
Audit table empty for an outage windowaudit insert path failingcheck the audit-write retry budget; never let audit failures block the request

For deeper coverage (RED method vs USE method tradeoffs, multi-tenant dashboard partitioning, synthetic FNOL probes, chaos-engineering tests for token-cache resilience), see implementation guide and API reference.

See Also

  • guidewire-install-auth — produces the auth-side signals this skill alerts on (token cache, scope drift)
  • guidewire-sdk-patterns — the structured GwError and 409 retry semantics this skill's triage trees assume
  • guidewire-security-and-rbac — the integration_audit table this skill queries during incidents
  • guidewire-ci-cd-pipeline — the deployment surface incident response interacts with (rollback, canary)

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/guidewire-observability-and-incident-response of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/API_REFERENCE.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Guidewire Observability And Incident Response next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Guidewire Observability And Incident Response compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Guidewire Observability And Incident Response this skilljeremylongshore/tons-of-skills-marketplace2.8k—~3.1kAutomated safety check: PassMIT
Observability Engineerdavila7/claude-code-templates33k8 repos~3.2kAutomated safety check: PassMIT
Incident Responderdavila7/claude-code-templates33k7 repos~2.6kAutomated safety check: PassMIT
It Operationsdavila7/claude-code-templates33k1 repos~3.7kAutomated safety check: PassMIT
Structured Logging Litemajiayu000/spellbook287—~1.7kAutomated safety check: PassMIT
Release Itwondelai/skills2.4k—~4kAutomated safety check: PassMIT

Similar skills

  • Observability Engineer

    davila7/claude-code-templates

    Build production-ready monitoring, logging, and tracing systems.

    33k GitHub starsUsed in 8 repos~3.2k tokens
    DevOps & CloudAuto-check passed

  • Incident Responder

    davila7/claude-code-templates

    Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.

    33k GitHub starsUsed in 7 repos~2.6k tokens
    DevOps & CloudAuto-check passed

  • It Operations

    davila7/claude-code-templates

    Manages IT infrastructure, monitoring, incident response, and service reliability.

    33k GitHub starsUsed in 1 repo~3.7k tokens
    DevOps & CloudAuto-check passed

  • Structured Logging Lite

    majiayu000/spellbook

    Design, audit, or implement application structured logging architecture from repository evidence.

    287 GitHub stars~1.7k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Release It

    wondelai/skills

    Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic.

    2.4k GitHub stars~4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Observability And Reliability

    cbrock84/headcount

    Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure.

    2k GitHub stars~931 tokensUpdated 23 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Guidewire Observability And Incident Response

What does Guidewire Observability And Incident Response do?

Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and…. Guidewire Observability And Incident Response is an agent skill from jeremylongshore/tons-of-skills-marketplace. Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and never for transient noise; triage 401 spikes, 409 storms, 429 saturation, scope drift, and Gosu OOM cascades from signal to recovery in 15 minutes or less.

When should I use Guidewire Observability And Incident Response?

Guidewire Observability And Incident Response fits situations like: designing a dashboard for a new integration; writing the on-call runbook; running a post-incident review; with guidewire observability.

How do I install Guidewire Observability And Incident Response in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-observability-and-incident-response -a claude-code`. Or copy the skill folder (skills/.curated/guidewire-observability-and-incident-response in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/guidewire-observability-and-incident-response in your project. Claude Code loads it when a task matches its description.

How do I install Guidewire Observability And Incident Response in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-observability-and-incident-response -a codex`. Or copy the skill folder (skills/.curated/guidewire-observability-and-incident-response in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/guidewire-observability-and-incident-response in your project. Codex loads it when a task matches its description.

Can I use Guidewire Observability And Incident Response in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-observability-and-incident-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/guidewire-observability-and-incident-response, .gemini/skills/guidewire-observability-and-incident-response, .github/skills/guidewire-observability-and-incident-response and .opencode/skills/guidewire-observability-and-incident-response in your project.

What does Guidewire Observability And Incident Response need to run?

Going by SKILL.md and its folder, Guidewire Observability And Incident Response needs credentials named GW_CLIENT_SECRET. Our summary lists: A credential in GW_CLIENT_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Bash(jq:*), Grep, Glob. Compatibility (from SKILL.md): Designed for Claude Code.

Does Guidewire Observability And Incident Response access the network?

SKILL.md names 5 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: sre.google, response.pagerduty.com, gcc.guidewire.com and brendangregg.com. This is read from the text; nothing was executed.

Is Guidewire Observability And Incident Response safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Guidewire Observability And Incident Response use?

Guidewire Observability And Incident Response is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Guidewire Observability And Incident Response use?

About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Guidewire Observability And Incident Response?

Skills that share tags, products or a category with Guidewire Observability And Incident Response: Observability Engineer (davila7/claude-code-templates, 33k stars), Incident Responder (davila7/claude-code-templates, 33k stars), It Operations (davila7/claude-code-templates, 33k stars) and Structured Logging Lite (majiayu000/spellbook, 287 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Guidewire Observability And Incident Response?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.