Help us improve
Share bugs, ideas, or general feedback.
From cms-cultivator
Transforms technical audit findings into client-friendly executive summaries. Generates stakeholder reports from existing audit files.
npx claudepluginhub kanopi/claude-toolbox --plugin cms-cultivatorHow this skill is triggered — by the user, by Claude, or both
Slash command
/cms-cultivator:audit-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate client-facing executive summaries from CMS Cultivator audit report files, transforming technical findings into accessible stakeholder communication.
Exports audit findings from markdown reports to Teamwork-compatible CSV for project management tools. Parses severity levels into tasks with due dates.
Structures WordPress diagnostic findings for technical and non-technical audiences with severity ratings, plain-language summaries, technical details, fixes, and action logs. Use for reports, communicating issues, or logging actions.
Audits deployed websites and web apps post-launch, cycling through Fix-Audit-Test phases to identify and resolve issues.
Share bugs, ideas, or general feedback.
Generate client-facing executive summaries from CMS Cultivator audit report files, transforming technical findings into accessible stakeholder communication.
This skill runs fully in Tier 1 using only file operations:
[original-name]-client-report.mdSame as Tier 1. This skill does not require additional Claude Code tools — it runs identically in both tiers.
# Site Health Report — [Site Name]
**Report Date**: [date]
**Prepared for**: [Client Name]
**Prepared by**: [Team/Agency Name]
## Overview
[2-3 sentences summarizing overall site health in plain language]
**Overall Health Score**: [score]/100
## Key Findings
### What's Working Well ✅
- [Positive finding 1]
- [Positive finding 2]
### Areas Requiring Attention
#### Urgent (Address Within 1 Week) 🔴
[Plain language description of critical issues and their business impact]
**Business Impact**: [Legal risk, lost revenue, user experience impact]
**Estimated Effort**: [X hours/days]
#### High Priority (Address This Month) 🟡
[Plain language description of high-priority issues]
**Business Impact**: [Impact description]
**Estimated Effort**: [X hours/days]
#### Planned Improvements (Next Quarter) 🟢
[Lower priority improvements]
## Recommended Actions
### Immediate (This Sprint)
1. [Action item with business justification]
2. [Action item]
### Short-Term (This Quarter)
1. [Action item]
### Long-Term (Roadmap)
1. [Action item]
## Investment Summary
| Priority | Issues | Est. Effort | Est. Cost* |
|----------|--------|-------------|------------|
| Urgent | [n] | [X hrs] | $ |
| High | [n] | [X hrs] | $ |
| Planned | [n] | [X hrs] | $ |
*Estimated at [agency rate]/hour. Actual costs will be confirmed in proposal.
## Next Steps
1. Review this report with your team
2. Prioritize issues based on business impact and budget
3. Schedule a follow-up meeting to discuss implementation roadmap
4. [Agency/team] will provide detailed proposals for approved work
---
*Technical details available in the accompanying developer audit report.*
| Technical Term | Client-Friendly Language |
|---|---|
| SQL injection | Security vulnerability allowing unauthorized data access |
| XSS vulnerability | Security gap that could allow malicious code injection |
| WCAG 2.1 AA | Accessibility standards ensuring site works for users with disabilities |
| Core Web Vitals | Google's page speed standards affecting search rankings |
| N+1 query | Database inefficiency causing slow page loads |
| Cache miss | Server inefficiency increasing page load times |
| Cyclomatic complexity | Code complexity increasing maintenance risk |
| Technical debt | Accumulated shortcuts requiring future cleanup |
| CVE | Known security vulnerability in a software component |