Test infrastructure configurations and deployments - security scanning with Checkov/tfsec, cost estimation analysis, pre-deployment validation, post- deployment verification, integration testing, generates comprehensive test reports with pass/fail status, identifies vulnerabilities and compliance issues, tracks test history for trend analysis.
Runs security scans, cost analysis, and integration tests on infrastructure configurations. Triggers when validating Terraform code before deployment or verifying resources after deployment.
/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-results.mdworkflow/post-deployment-tests.mdworkflow/pre-deployment-tests.md<CRITICAL_RULES> IMPORTANT: Testing and validation rules
EXECUTE STEPS:
Step 1: Load Configuration
Step 2: Determine Test Phase
Step 3: Execute Tests
Step 4: Analyze Results
Step 5: Generate Report
Step 6: Document Results
OUTPUT COMPLETION MESSAGE:
ā
COMPLETED: Infrastructure Testing
Status: ${overall_status}
Tests Run: ${test_count}
Passed: ${passed_count}
Failed: ${failed_count}
Critical Issues: ${critical_count}
Report: ${report_path}
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Next: Review report before proceeding with ${next_action}
IF FAILURE:
ā FAILED: Infrastructure Testing
Phase: ${phase}
Tests Failed: ${failed_tests}
Critical Issues: ${critical_issues}
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Resolution: Address issues before proceeding to deployment
<COMPLETION_CRITERIA> This skill is complete and successful when ALL verified:
ā 1. Tests Executed
ā 2. Results Analyzed
ā 3. Report Generated
ā 4. History Updated
FAILURE CONDITIONS - Stop and report if: ā Critical security vulnerabilities found (return findings to manager) ā Test execution errors (return error details) ā Cost exceeds configured threshold (return cost analysis)
PARTIAL COMPLETION - Not acceptable: ā ļø Some tests skipped ā Return to Step 3 ā ļø Report not generated ā Return to Step 5 </COMPLETION_CRITERIA>
<OUTPUTS> After successful completion, return to agent:Test Report
Test Summary
Return to agent:
{
"status": "PASS|FAIL",
"phase": "${phase}",
"environment": "${environment}",
"tests_run": ${test_count},
"tests_passed": ${passed_count},
"tests_failed": ${failed_count},
"critical_issues": ${critical_count},
"cost_estimate": "${cost}" (pre-deployment only),
"report_path": "${report_path}",
"recommendations": ["..."]
}
Update:
<ERROR_HANDLING> <TEST_EXECUTION_ERROR> Pattern: Test tool fails to execute Action: 1. Log error details 2. Check tool installation 3. Return error to manager Delegate: None (inform manager) </TEST_EXECUTION_ERROR>
<CRITICAL_SECURITY_ISSUE> Pattern: Critical or high severity security finding Action: 1. Mark test as FAILED 2. Document findings 3. Return to manager with findings Delegate: None (block deployment) </CRITICAL_SECURITY_ISSUE>
<COST_THRESHOLD_EXCEEDED> Pattern: Estimated cost exceeds configured threshold Action: 1. Mark test as FAILED 2. Document cost analysis 3. Return to manager with cost breakdown Delegate: None (request user approval) </COST_THRESHOLD_EXCEEDED> </ERROR_HANDLING>
<EXAMPLES> <example> Input: environment=test, phase=pre-deployment Start: "š STARTING: Infrastructure Testing / Environment: test / Phase: pre-deployment" Process: - Load configuration - Run security scans (Checkov, tfsec) - Generate cost estimate - Analyze results - Generate report Completion: "ā COMPLETED: Infrastructure Testing / Status: PASS / Tests Run: 8 / Passed: 8" Output: {status: "PASS", tests_passed: 8, cost_estimate: "$45.30/month"} </example> <example> Input: environment=test, phase=post-deployment Start: "š STARTING: Infrastructure Testing / Environment: test / Phase: post-deployment" Process: - Load configuration - Verify deployed resources exist - Run integration tests - Check resource health - Analyze results - Generate report Completion: "ā COMPLETED: Infrastructure Testing / Status: PASS / Tests Run: 5 / Passed: 5" Output: {status: "PASS", tests_passed: 5, resources_verified: ["s3-bucket", "lambda-function"]} </example> <example> Input: environment=prod, phase=pre-deployment Start: "š STARTING: Infrastructure Testing / Environment: prod / Phase: pre-deployment" Process: - Load configuration - Run security scans - Find critical security issue (S3 bucket public access) - Mark as FAILED - Generate report with findings Completion: "ā FAILED: Infrastructure Testing / Critical Issues: 1 (S3 public access)" Output: {status: "FAIL", critical_issues: 1, findings: [{severity: "CRITICAL", issue: "S3 bucket allows public access"}]} </example> </EXAMPLES>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.