skills/audit-export/SKILL.md
Export audit findings from markdown report files to Teamwork-compatible CSV format for project management tools (Jira, Monday, Linear also supported). Auto-activates when user asks to "export audit to CSV", "create tasks from audit", or provides an audit report file and asks to export it. Invoke when user provides audit report filename and wants CSV output for project management import.
npx skillsauth add kanopi/cms-cultivator audit-exportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Export audit findings from CMS Cultivator markdown reports to CSV format for project management tools.
This skill runs fully in Tier 1 using only file operations:
## Critical Issues or ### CRITICAL → Phase 1: Critical Issues (DUE DATE = today + 3 days)## High Priority or ### HIGH → Phase 2: High Priority (DUE DATE = today + 10 days)## Medium Priority or ### MEDIUM → Phase 3: Medium Priority (DUE DATE = today + 20 days)## Low Priority or ### LOW → Phase 4: Long-term Optimization (no due date)[original-name]-tasks.csvSame as Tier 1. This skill does not require additional Claude Code tools — it runs identically in both tiers.
Columns: TASKLIST, TASK, DESCRIPTION, ASSIGN TO, START DATE, DUE DATE, PRIORITY, ESTIMATED TIME, TAGS, STATUS
Critical rules:
Each extracted task uses this template in the DESCRIPTION column:
## Description
Teamwork Ticket(s): [To be assigned]
- [ ] Was AI used in this pull request?
> As a developer, I need to {goal}
{summary from audit}
## Acceptance Criteria
* {extracted from audit}
## Assumptions
* {known limitations}
## Steps to Validate
1. {testing instructions}
## Affected URL
{link if available}
## Deploy Notes
{file paths, cache clearing, config imports}
SecurityPerformanceAccessibilityCode Quality2h15maudit-live-site-2026-04-15-1430.mdaudit-live-site-2026-04-15-1430-tasks.csvPrimary: Teamwork (full template format) Also works with: Jira, Monday.com, Linear, Asana (CSV import with column mapping)
tools
Strategist-focused site audit for discovery and pre-discovery. Given a site URL and optional qualitative research data, navigates the site via CoWork, audits against all 21 UX Laws from lawsofux.com, reviews content hierarchy, synthesises qualitative data, runs Lighthouse, and produces two deliverables — a Project Knowledge Summary (Markdown for Claude Desktop Projects) and a polished, iterable HTML Artifact for client sharing. Use when a strategist, UX lead, or PM asks for a discovery audit, UX laws audit, content hierarchy review, pre-discovery site review, "audit this site for strategy", "strategist audit", "UX audit", or pastes a site URL with discovery context. Not for developer audits — use accessibility-audit, performance-audit, or live-site-audit for those.
development
Provide story point estimation guidance with hour calculations for software development tasks. Uses Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34+) and converts story points to hours. Includes platform-specific adjustments and velocity calculations.
tools
Perform a full QA review of a Teamwork task by reading the task and all its comments for context, extracting the multi-dev URL, generating dynamic validation steps tailored to the task type, and using CoWork browser automation to execute those steps on the multi-dev environment. Produces a structured validation report with pass/fail per step, screenshots, internal notes, and a client-facing summary — all shown in chat. Use this skill whenever the user asks to QA, test, validate, or review a Teamwork task or multi-dev environment — even if they just say "can you QA this?" or paste a Teamwork link. Also triggers for phrases like "run QA on", "check the multi-dev", "validate this task", "test the dev link", or "review the ticket". Works across Drupal/CMS updates, WordPress/plugin updates, bug fixes, new feature development, and general web development tasks.
tools
Generate a client-facing project heartbeat / status update message for a Kanopi project, ready to be posted as a Teamwork message. Use this skill whenever the user asks to write, draft, generate, or send a project update, heartbeat, status update, or progress report to a client. Also triggers when the user says things like "time for a project update", "draft the heartbeat", "write up the update for [project]", or "it's been two weeks, let's send an update". Always use this skill — even if the user doesn't say "heartbeat" — whenever the intent is to summarise recent project activity for a client audience.