Agent skill
post-deploy
Frontend post-deployment validation and performance checks. TODO: Implement for frontend. Invoked by: "/post-deploy", "verify deployment", "lighthouse check", "cdn check".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/post-deploy-eleva-labs-agentic-coding-templ-2
SKILL.md
Post-Deploy (Frontend)
Status: Stub - Not Implemented Domain: Frontend
Overview
Frontend-specific post-deployment skill for verifying CDN cache invalidation, running Lighthouse performance audits, and validating static asset delivery after deploying web applications.
Arguments
| Argument | Description | Example |
|---|---|---|
| environment | Target environment | staging, production |
| --skip-lighthouse | Skip Lighthouse audit | --skip-lighthouse |
| --skip-cdn | Skip CDN verification | --skip-cdn |
Usage Examples
# Run all post-deployment checks
/post-deploy production
# Quick verification without Lighthouse
/post-deploy staging --skip-lighthouse
# Full production verification
/post-deploy production --verbose
Frontend-Specific Checks
- CDN cache invalidation verification
- Lighthouse performance audit (Performance, Accessibility, SEO, Best Practices)
- Static asset delivery verification
- Service worker update verification
- Analytics tracking verification
- A/B test configuration verification
- CSP and security header checks
- Third-party script loading verification
TODO
- Define CDN cache invalidation workflow
- Add Lighthouse CI integration
- Define performance budget checks
- Add analytics verification steps
- Document A/B test verification
- Add security header validation
- Define bundle size regression checks
End of Skill
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?