guidewire-observability
Monitor Guidewire InsuranceSuite: logging, metrics, tracing, and alerting via GCC. Trigger: "guidewire observability", "observability".
Best use case
guidewire-observability is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Monitor Guidewire InsuranceSuite: logging, metrics, tracing, and alerting via GCC. Trigger: "guidewire observability", "observability".
Teams using guidewire-observability should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/guidewire-observability/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How guidewire-observability Compares
| Feature / Agent | guidewire-observability | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Monitor Guidewire InsuranceSuite: logging, metrics, tracing, and alerting via GCC. Trigger: "guidewire observability", "observability".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Guidewire Observability
## Overview
Guidewire InsuranceSuite processes claims, policies, and billing through long-running batch jobs and synchronous Cloud APIs. Observability must track claim processing times, policy synchronization health, billing accuracy, and integration endpoint status. Batch failures in ClaimCenter or PolicyCenter can silently block downstream workflows, so real-time alerting on queue depth and job completion is critical for insurance operations SLAs.
## Key Metrics
| Metric | Type | Target | Alert Threshold |
|--------|------|--------|-----------------|
| Claim processing time | Histogram | < 30s | > 60s |
| Policy sync success rate | Gauge | > 99.5% | < 98% |
| Billing accuracy rate | Gauge | > 99.9% | < 99.5% |
| Cloud API latency p95 | Histogram | < 500ms | > 2s |
| Batch job completion rate | Gauge | 100% | < 95% per cycle |
| Integration queue depth | Gauge | < 100 | > 500 |
## Instrumentation
```typescript
async function trackGuidewireAPI(endpoint: string, operation: string, fn: () => Promise<any>) {
const start = Date.now();
try {
const result = await fn();
metrics.histogram('guidewire.api.latency', Date.now() - start, { endpoint, operation });
metrics.increment('guidewire.api.calls', { endpoint, status: 'ok' });
return result;
} catch (err) {
metrics.increment('guidewire.api.errors', { endpoint, status: err.statusCode });
throw err;
}
}
```
## Health Check Dashboard
```typescript
async function guidewireHealth(): Promise<Record<string, string>> {
const batchStatus = await gccAdmin.getBatchJobStatus();
const apiLatency = await metrics.query('guidewire.api.latency', 'p95', '5m');
const queueDepth = await gccAdmin.getIntegrationQueueDepth();
return {
batch_jobs: batchStatus.allCompleted ? 'healthy' : 'failed',
api_latency: apiLatency < 500 ? 'healthy' : 'slow',
integration_queue: queueDepth < 100 ? 'healthy' : 'backlogged',
};
}
```
## Alerting Rules
```typescript
const alerts = [
{ metric: 'guidewire.claim.processing_time_p95', condition: '> 60s', window: '15m', severity: 'warning' },
{ metric: 'guidewire.batch.completion_rate', condition: '< 0.95', window: '1h', severity: 'critical' },
{ metric: 'guidewire.integration.queue_depth', condition: '> 500', window: '10m', severity: 'critical' },
{ metric: 'guidewire.api.error_rate', condition: '> 0.02', window: '5m', severity: 'warning' },
];
```
## Structured Logging
```typescript
function logGuidewireEvent(event: string, data: Record<string, any>) {
console.log(JSON.stringify({
service: 'guidewire', event,
module: data.module, // ClaimCenter | PolicyCenter | BillingCenter
operation: data.operation, duration_ms: data.latency,
// Redact PII: no policyholder names, SSNs, or claim details
claim_id: data.claimId, policy_number: data.policyNum,
timestamp: new Date().toISOString(),
}));
}
```
## Error Handling
| Signal | Meaning | Action |
|--------|---------|--------|
| Batch job timeout | Long-running claim/policy sync stalled | Check GCC batch monitor, restart job |
| Queue depth > 500 | Integration backlog growing | Scale consumers, check downstream APIs |
| Policy sync < 98% | Data mismatch between systems | Audit sync logs, compare source records |
| API 503 errors | GCC maintenance or overload | Check GCC status page, retry with backoff |
| Billing discrepancy | Calculation or rounding error | Flag for manual review, audit batch output |
## Resources
- [Guidewire Developer Portal](https://developer.guidewire.com/)
- [Cloud API Reference](https://docs.guidewire.com/cloud/pc/202503/apiref/)
- [Guidewire Cloud Console](https://gcc.guidewire.com)
## Next Steps
See `guidewire-incident-runbook`.Related Skills
windsurf-observability
Monitor Windsurf AI adoption, feature usage, and team productivity metrics. Use when tracking AI feature usage, measuring ROI, setting up dashboards, or analyzing Cascade effectiveness across your team. Trigger with phrases like "windsurf monitoring", "windsurf metrics", "windsurf analytics", "windsurf usage", "windsurf adoption".
webflow-observability
Set up observability for Webflow integrations — Prometheus metrics for API calls, OpenTelemetry tracing, structured logging with pino, Grafana dashboards, and alerting for rate limits, errors, and latency. Trigger with phrases like "webflow monitoring", "webflow metrics", "webflow observability", "monitor webflow", "webflow alerts", "webflow tracing".
vercel-observability
Set up Vercel observability with runtime logs, analytics, log drains, and OpenTelemetry tracing. Use when implementing monitoring for Vercel deployments, setting up log drains, or configuring alerting for function errors and performance. Trigger with phrases like "vercel monitoring", "vercel metrics", "vercel observability", "vercel logs", "vercel alerts", "vercel tracing".
veeva-observability
Veeva Vault observability for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva observability".
vastai-observability
Monitor Vast.ai GPU instance health, utilization, and costs. Use when setting up monitoring dashboards, configuring alerts, or tracking GPU utilization and spending. Trigger with phrases like "vastai monitoring", "vastai metrics", "vastai observability", "monitor vastai", "vastai alerts".
twinmind-observability
Monitor TwinMind transcription quality, meeting coverage, action item extraction rates, and memory vault health. Use when implementing observability, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind observability", "twinmind observability".
speak-observability
Monitor Speak API health, assessment latency, session metrics, and pronunciation score distributions. Use when implementing observability, or managing Speak language learning platform operations. Trigger with phrases like "speak observability", "speak observability".
snowflake-observability
Set up Snowflake observability using ACCOUNT_USAGE views, alerts, and external monitoring. Use when implementing Snowflake monitoring dashboards, setting up query performance tracking, or configuring alerting for warehouse and pipeline health. Trigger with phrases like "snowflake monitoring", "snowflake metrics", "snowflake observability", "snowflake dashboard", "snowflake alerts".
shopify-observability
Set up observability for Shopify app integrations with query cost tracking, rate limit monitoring, webhook delivery metrics, and structured logging. Trigger with phrases like "shopify monitoring", "shopify metrics", "shopify observability", "monitor shopify API", "shopify alerts", "shopify dashboard".
salesforce-observability
Set up observability for Salesforce integrations with API limit monitoring, error tracking, and alerting. Use when implementing monitoring for Salesforce operations, tracking API consumption, or configuring alerting for Salesforce integration health. Trigger with phrases like "salesforce monitoring", "salesforce metrics", "salesforce observability", "monitor salesforce", "salesforce alerts", "salesforce API usage dashboard".
retellai-observability
Retell AI observability — AI voice agent and phone call automation. Use when working with Retell AI for voice agents, phone calls, or telephony. Trigger with phrases like "retell observability", "retellai-observability", "voice agent".
replit-observability
Monitor Replit deployments with health checks, uptime tracking, resource usage, and alerting. Use when setting up monitoring for Replit apps, building health dashboards, or configuring alerting for deployment health and performance. Trigger with phrases like "replit monitoring", "replit metrics", "replit observability", "monitor replit", "replit alerts", "replit uptime".