{"id":73241,"plugin_id":"plugin_asdk_app_6acefad1823481918546ca83560c2644","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-31T01:20:24.856Z","digest":"a206de116b60343a60bb9c4fe7eedaf26d51b7e7ba712b602c223fa5a49b34e4","against":null,"payload":{"description":"Draft a Leafpad post, check its on-page SEO, and publish only after the user agrees.","included_files":[],"name":"write-and-publish","skill_md_contents":"---\nname: write-and-publish\ndescription: Draft a Leafpad post, check its on-page SEO, and publish only after the user agrees.\n---\n\nWrite with the user's own site, then stop before publishing.\n\n1. Call `leafpad_list_organizations` and use the site the user names. If they have one site, use it.\n2. Call `leafpad_get_company_data` with a question about the topic so the draft uses the site's own facts. If that returns nothing, say the knowledge base had no match and draft from what the user provided. Do not invent product facts, prices, or statistics.\n3. Call `leafpad_list_tags` and reuse tags that fit. Then call `leafpad_create_post` with `published` left false.\n4. Call `check_draft_seo` on the new post id. Tell the user the score and the checks that are not passing.\n5. Ask whether to revise the draft or publish it. Call `publish_post` only after the user agrees to publish. Calling `leafpad_update_post` is for edits, not for going live.\n\nDo not publish, schedule, or approve a refresh as part of saving a draft.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}