
Graceful Degradation
- 13 installs
- 1 repo stars
- Updated March 10, 2026
- davidcastagnetoa/skills
Return partial pipeline responses with a score penalty when non-critical services fail, classifying agents by criticality and flagging degraded modules.
About
Implements a graceful-degradation pattern that returns partial results with a score penalty when non-critical services fail. A developer uses it to keep a pipeline operating instead of erroring when a non-essential dependency is down.
- Classifies services as critical vs non-critical for partial responses
- Neutral scoring, degraded flags, and auto-escalation to manual review
Graceful Degradation by the numbers
- 13 all-time installs (skills.sh)
- Ranked #3,516 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidcastagnetoa/skills --skill graceful_degradationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 13 |
|---|---|
| repo stars | ★ 1 |
| Last updated | March 10, 2026 |
| Repository | davidcastagnetoa/skills ↗ |
What it does
Return partial pipeline responses with a score penalty when non-critical services fail, classifying agents by criticality and flagging degraded modules.
Files
graceful_degradation
Patrón de degradación graceful que permite al sistema continuar operando con funcionalidad reducida cuando un servicio no crítico falla, en lugar de devolver un error total.
When to use
Usar en el api_gateway_agent y orchestrator_agent cuando un agente no crítico (antifraud geo-check, age estimation) no responde. El pipeline continúa con penalización de score.
Instructions
1. Clasificar agentes por criticidad:
- Críticos (pipeline se detiene): liveness, face_match, document_processor.
- No críticos (pipeline continúa): geo-check, age estimation, VPN detection.
2. Si agente no crítico falla, asignar score neutral (0.5) y flag degraded. 3. Incluir en respuesta: "degraded_modules": ["antifraud_geo"]. 4. Penalizar score global: reducir confianza en -0.05 por cada módulo degradado. 5. Si > 2 módulos degradados, derivar a MANUAL_REVIEW automáticamente. 6. Registrar modo degradado en métricas y auditoría. 7. Alertar al health_monitor_agent para investigar el servicio caído.
Notes
- Nunca degradar módulos críticos (liveness, face_match); si fallan, retornar error.
- El modo degradado debe ser transparente para el cliente en la respuesta.
- Revisar semanalmente las métricas de degradación para identificar servicios inestables.
List_Agents.md
list_skills.md
CLAUDE.md
Agents.md
.DS_Store