Update to Writesonic

{
  "description": "Diagnose a visibility drop — which topics and platforms declined, whether citations were lost or sentiment turned, the exact prompts responsible, and a fix per cause. Use when the user asks why visibility, share of voice, or mentions went down.",
  "included_files": [],
  "name": "visibility-drop",
  "skill_md_contents": "---\nname: visibility-drop\ndescription: Diagnose a visibility drop — which topics and platforms declined, whether citations were lost or sentiment turned, the exact prompts responsible, and a fix per cause. Use when the user asks why visibility, share of voice, or mentions went down.\n---\nDiagnose the visibility drop for project \"$ARGUMENTS\" (resolve via `get_all_projects` if needed). Compare the drop period against the period before it. Do not skip steps or diagnose from the aggregate alone.\n\n1. `query_performance_report` dimensions=[\"topic\", \"date\"] website_type=\"SELF\" — which topics declined.\n2. `query_performance_report` dimensions=[\"model\", \"date\"] website_type=\"SELF\" — which platforms declined.\n3. `query_citation_report` dimensions=[\"date\"] website_type=\"SELF\" — were citations lost?\n4. `query_sentiment_report` dimensions=[\"date\"] website_type=\"SELF\" — did sentiment turn?\n5. `get_ai_answer_changes` — the exact prompts where answers changed; spot-check 2–3 with `get_prompt_answers`.\n6. Check for configuration changes (prompts or competitors added/removed) — these shift denominators and can mimic a real drop.\n\nReport: cause → evidence (numbers + period) → recommended fix, one block per cause. Declines first, no hyperbole.\n"
}