graceful-degradation
Graceful Degradation with Helpful Messages
When & Why to Use This Skill
This Claude skill implements a robust 'Graceful Degradation' design pattern for AI agents and software systems. It ensures that when optional services or tools are unavailable, the system doesn't fail silently; instead, it provides actionable fallback messages and continues with reduced functionality, significantly improving user experience and system reliability.
Use Cases
- Local LLM Connectivity: Detecting if local services like LMStudio or Ollama are active and providing specific setup instructions to the user if they are offline.
- Third-Party API Resilience: Managing optional API dependencies by notifying users of specific feature limitations during outages while keeping the core application functional.
- Development Environment Troubleshooting: Identifying missing environment variables or configuration files early and guiding developers through the necessary fix steps.
- Resource-Heavy Task Management: Checking for high-compute resource availability before execution and offering lighter alternatives if the primary service is throttled.
| name | graceful-degradation |
|---|---|
| description | Graceful Degradation with Helpful Messages |
| user-invocable | false |
Graceful Degradation with Helpful Messages
When optional services are unavailable, degrade gracefully with actionable fallback messages.
Pattern
Check availability at the start, cache the result, and provide helpful messages that explain what's missing and how to fix it.
DO
- Check service availability early (before wasting compute)
- Cache health check results for the session (e.g., 60s TTL)
- Provide actionable fallback messages:
- What service is missing
- What features are degraded
- How to enable the service
- Continue with reduced functionality when possible
DON'T
- Silently fail or return empty results
- Check availability on every call (cache it)
- Assume the user knows how to start missing services
Example: LMStudio Check Pattern
let lmstudioAvailable: boolean | null = null;
let lastCheck = 0;
const CACHE_TTL = 60000; // 60 seconds
async function checkLMStudio(): Promise<boolean> {
const now = Date.now();
if (lmstudioAvailable !== null && now - lastCheck < CACHE_TTL) {
return lmstudioAvailable;
}
try {
const response = await fetch('http://localhost:1234/v1/models', {
signal: AbortSignal.timeout(2000)
});
lmstudioAvailable = response.ok;
} catch {
lmstudioAvailable = false;
}
lastCheck = now;
return lmstudioAvailable;
}
// Usage
if (!await checkLMStudio()) {
return {
result: 'continue',
message: `LMStudio not available at localhost:1234.
To enable Godel-Prover tactic suggestions:
1. Install LMStudio from https://lmstudio.ai/
2. Load "Goedel-Prover-V2-8B" model
3. Start the local server on port 1234
Continuing without AI-assisted tactics...`
};
}
Fallback Message Template
[Service] not available at [endpoint].
To enable [feature]:
1. [Step to install/start]
2. [Configuration step if needed]
3. [Verification step]
Continuing without [degraded feature]...
Source Sessions
- This session: LMStudio availability check with 60s caching and helpful fallback
- 174e0ff3: Environment variable debugging - print computed paths for troubleshooting