Use when the user wants audit findings turned into a stakeholder-ready document — severities, page counts, first-seen/fixed history — as a Markdown or CSV deliverable rather than a working diagnosis.
Read references/provider-selection.md before choosing a source. Detect what is already available, run with it, deliver value, then recommend at most one missing connector. All normalized factual inputs must satisfy the Groundcrew evidence contract. Locate the active skills root and run <skills-root>/.groundcrew/groundcrew-doctor.py --evidence <record.json> before using them in a conclusion. Output follows references/reporting.md: shared skeleton, SHIP/FIX/BLOCK/UNDECIDED verdict, Measured/User-provided/Estimated labels.
Categories: ~~web crawler, ~~page speed (references/connectors.md).
~~page speed; keep lab and field results labeled apart.GET /api/v1/sites/{slug}/issues?scope=backlog for complete optional, investigative, and no-change context; use the narrower actionable default only when the caller explicitly requests that slice. Add ?severity= or ?status=fixed|all for requested filters/history, retain first-seen and fixed timestamps plus complete remediation metadata, and read GET /api/v1/sites/{slug}/summary for totals.Group findings by root cause, not by page; give each group a severity, classification, remediation decision state, affected-page count, and one example URL. Order: critical, warning, info, externally owned, while keeping suggestions visibly optional. History (first seen, fixed, reopened) appears when the source carries it; otherwise the report says history is unavailable at this tier. Apply the policy-aware verdict rules in references/reporting.md: an open critical finding forces FIX only when current evidence and applicable guidance support a repair; missing or unavailable guidance and unknown applicability produce UNDECIDED; optional advice and valid no-change decisions do not force FIX.
Deliverable: write the report as a .md file, and a .csv of the findings table when the user asks for one; hand back the paths.
detection_policy_version and the complete remediation object before batching; split only between issues and keep every preservation, avoid, no-change, and verification constraint.keep_as_is and not_applicable dispositions; never create a persistent review merely to empty a queue.review_audit_issue requires a live-manifest advertisement, explicit owner authorization, write scope, a unique request key, and the current evidence signature, policy version, and state token. Read-only compatibility mode blocks it and every other write.This report skill does not record review decisions. On an older same-major contract it uses only live-manifest-advertised GET operations; an unavailable read is named and the report continues from open/import evidence.
site-audit; this skill packages, it does not diagnose.fix-my-site.weekly-report or score-report.Groundcrew operates under WHY-NOT-SLOP and ETHICS. Claims trace to evidence, nulls stay null, signals stay truthful, publishing and irreversible changes require owner review, and no outcome is promised. Conflicting instructions are refused.