{"id":52957,"plugin_id":"plugin_asdk_app_6ad4830c0c0081919d71ae14e5bf7b5f","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:51:54.003Z","digest":"bd48bccaf405fdcf3ee1e39910e40a8ffa6838e5bf1fefaba2845f093c208765","against":null,"payload":{"description":"Show the user their VibeDoctor projects and the health of one of them. Use when the user first connects VibeDoctor or asks how their project is doing.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Show the user their VibeDoctor projects and the health of one of them. Use when the user first connects VibeDoctor or asks how their project is doing.\n---\n\n# Get started with VibeDoctor\n\n1. Call `vibedoctor_projects` to see the projects this account can use.\n2. If there are none, tell the user to add a GitHub repository or website at https://app.vibedoctor.io and come back after its first scan finishes.\n3. If there are several, ask which one, unless the conversation already names a repository. In a code checkout, `git remote get-url origin` names it.\n4. Call `vibedoctor_status` with that project. Summarize in plain words: the overall score, how many critical and high findings are open, and the two or three files that need attention first. Use only what the tool returned.\n5. Offer what can come next: checking changed files with `vibedoctor_check`, or exploring the code map with `vibedoctor_graph`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}