Analyze infrastructure deployment errors - categorize error types (permission/ config/resource/state), search issue log for historical solutions, rank solutions by success rate and context match, propose automated fixes via delegation, learn from resolution outcomes, track debugging metrics, handles permission errors by routing to permission-manager.
Analyzes infrastructure deployment errors by categorizing them, searching historical solutions, and proposing fixes. Automatically delegates permission errors to the permission manager and learns from resolution outcomes to improve future debugging.
/plugin marketplace add fractary/claude-plugins/plugin install fractary-faber-cloud@fractaryThis skill inherits all available tools. When active, it can use any tool Claude has access to.
workflow/analyze-solutions.mdworkflow/categorize-error.mdworkflow/search-solutions.md<CRITICAL_RULES> IMPORTANT: Debugging and error analysis rules
<COMPLETE_FLAG_BEHAVIOR> When --complete flag is present:
Automated Mode Enabled:
Interactive Mode (default, no --complete):
Example Flow with --complete:
deploy-apply fails with AccessDenied
↓
infra-deployer offers 3 options, user selects Option 2: "Run debug --complete"
↓
infra-debugger --complete invoked
↓
Categorizes as permission error
↓
Delegates to infra-permission-manager automatically
↓
Permission added to audit file and applied to AWS
↓
infra-debugger returns to infra-deployer with success
↓
infra-deployer continues deployment automatically
↓
Deployment completes successfully
When to Use:
When NOT to Use:
<ERROR_CATEGORIES> Errors are categorized into these types:
1. Permission Errors
2. Configuration Errors
3. Resource Errors
4. State Errors
5. Network Errors
6. Quota Errors
EXECUTE STEPS:
Step 1: Load Configuration
Step 2: Categorize Error
Step 3: Normalize Error
Step 4: Search Issue Log
Step 5: Analyze Solutions
Step 6: Propose Solution
Step 7: Log Error
Step 8: Apply Fix (if --complete flag)
Step 8 Alternative: Propose Fix (interactive mode)
OUTPUT COMPLETION MESSAGE:
✅ COMPLETED: Infrastructure Debugging
Category: ${error_category}
Issue ID: ${issue_id}
Solutions Found: ${solution_count}
Best Solution: ${solution_description}
Can Automate: ${automated}
${automation_info}
───────────────────────────────────────
Next: ${next_action}
IF NO SOLUTION FOUND:
⚠️ COMPLETED: Infrastructure Debugging (Novel Error)
Category: ${error_category}
Issue ID: ${issue_id}
Solutions Found: 0
This is a new error not seen before.
Manual investigation required.
───────────────────────────────────────
Error has been logged for future reference.
Please investigate and resolve manually.
IF FAILURE:
❌ FAILED: Infrastructure Debugging
Step: ${failed_step}
Error: ${debug_error}
───────────────────────────────────────
Resolution: Unable to analyze error
<COMPLETION_CRITERIA> This skill is complete and successful when ALL verified:
✅ 1. Error Categorized
✅ 2. Error Normalized
✅ 3. Solutions Searched
✅ 4. Proposal Generated
✅ 5. Error Logged
FAILURE CONDITIONS - Stop and report if: ❌ Cannot parse error message (return raw error to manager) ❌ Issue log corrupted (attempt repair, inform manager) ❌ Critical system error (escalate to manager)
PARTIAL COMPLETION - Not acceptable: ⚠️ Error not logged → Return to Step 7 ⚠️ No solution proposed → Generate "manual investigation" proposal </COMPLETION_CRITERIA>
<OUTPUTS> After successful completion, return to agent:Debug Report
Delegation Instructions (if automated)
Manual Instructions (if not automated)
Return to agent:
{
"status": "solution_found|no_solution|novel_error",
"issue_id": "${issue_id}",
"error_category": "${category}",
"error_code": "${code}",
"resource_type": "${resource_type}",
"root_cause": "Human-readable explanation of what went wrong",
"proposed_solution": {
"description": "What this solution does",
"steps": ["Step 1", "Step 2", "Step 3"],
"automated": true|false,
"success_rate": 95.5,
"avg_resolution_time": 45
},
"delegation": {
"can_delegate": true|false,
"target_skill": "infra-permission-manager",
"operation": "auto-grant",
"parameters": {
"permission": "s3:PutObject",
"resource": "arn:aws:s3:::bucket-name"
}
},
"manual_steps": [
"If automated is false, provide manual steps here"
]
}
<DELEGATION_PATTERNS> <PERMISSION_ERROR> When error_category == "permission": Target: infra-permission-manager Operation: auto-grant Parameters: { environment: ${environment}, permission: ${missing_permission}, resource: ${resource_arn} } </PERMISSION_ERROR>
<STATE_ERROR> When error_category == "state": Target: handler-iac-${iac_handler} Operation: state-fix Parameters: { operation: "refresh|import|remove", resource: ${resource_id} } </STATE_ERROR>
<CONFIG_ERROR> When error_category == "config": No automatic delegation - return manual steps User must fix configuration issues </CONFIG_ERROR> </DELEGATION_PATTERNS>
<DOCUMENTATION> After analyzing error and proposing solution:Log error in issue log: Execute: ../devops-common/scripts/log-resolution.sh --action=log-issue
After solution is attempted (manager will call back): Execute: ../devops-common/scripts/log-resolution.sh --action=log-solution Update success rate based on outcome
</DOCUMENTATION><ERROR_HANDLING> <ISSUE_LOG_NOT_FOUND> Pattern: Issue log file doesn't exist Action: 1. Initialize issue log from template 2. Continue with error logging 3. Note: First error logged </ISSUE_LOG_NOT_FOUND>
<UNPARSEABLE_ERROR> Pattern: Cannot extract meaningful information from error Action: 1. Log raw error message 2. Categorize as "unknown" 3. Return to manager with request for manual investigation </UNPARSEABLE_ERROR>
<MULTIPLE_MATCHING_SOLUTIONS> Pattern: Multiple solutions with similar scores Action: 1. Select solution with highest success rate 2. Include alternative solutions in proposal 3. Let manager/user choose if success rates similar </MULTIPLE_MATCHING_SOLUTIONS> </ERROR_HANDLING>
<LEARNING_MECHANISM> This skill learns from outcomes through:
Solution Success Tracking
Pattern Recognition
Automation Improvement
Context Learning
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.