{"id":98566,"plugin_id":"plugin_asdk_app_6ac47963cb448191a5b1757e0682bd6a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:13:07.932Z","digest":"310a8de3a1147053f6790543e0d09b7304bf7d62589cb48688c2e2a3d814225d","against":null,"payload":{"description":"Use when a freelancer, consultant or agency wants a finished Sitewalk audit turned into a short client-ready SEO report for a client or a manager: the site health score, the top problems in plain English and the links to the full report, PDF and CSV.","included_files":[],"name":"client-report","skill_md_contents":"---\nname: client-report\ndescription: Use when a freelancer, consultant or agency wants a finished Sitewalk audit turned into a short client-ready SEO report for a client or a manager: the site health score, the top problems in plain English and the links to the full report, PDF and CSV.\n---\n\nTurn a finished audit into a short report a non-technical reader can act on. Do not start a new audit for this.\n\n1. Use the `audit_id` of the audit already discussed in this chat. If there is none, ask which site, then run the audit as usual first.\n2. Call `get_audit_report`.\n3. Write the report in this order: one sentence on the overall state of the site, with the health score if the report returns one; the three problems to fix first, each with what it is in plain English, how many pages it affects and the fix; then a short list of the remaining issues by impact.\n4. Leave jargon out. Where a technical term is needed, explain it in a few words.\n5. End with the full report link and the PDF and CSV links from the report, so the reader can open or forward them.\n\nUse only the issues, counts, score and links the report returns. Do not add issues, traffic estimates or promises about rankings.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}