{"id":55182,"plugin_id":"plugin_asdk_app_6a7074e91c008191942479b885fb0d9b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-26T06:08:10.159Z","digest":"d92ed81ebc8536f5ff6e3e16f8ff0e57b8da41be99b1aa3a9d9fe2eaf97608d7","against":null,"payload":{"description":"Help a user start with Publora: show connected accounts with example prompts, connect a missing social account, or prepare and schedule their first post. Use for first-run help and requests for accounts plus examples. A request only to list accounts or check the queue does not require a guided first-post flow.\n","included_files":[],"name":"publora-setup","skill_md_contents":"---\nname: publora-setup\ndescription: >\n  Help a user start with Publora: show connected accounts with example prompts,\n  connect a missing social account, or prepare and schedule their first post.\n  Use for first-run help and requests for accounts plus examples. A request only\n  to list accounts or check the queue does not require a guided first-post flow.\n---\n\n# Get started with Publora\n\nFollow the user's current request. The Try now prompt asks for accounts and\nexamples; it does not authorize creating a post. This skill can also be chosen\nfrom a first-post request without any setup button.\n\n## Accounts and a useful next step\n\nThis section is for personal accounts. If the user explicitly chooses Agency\nclient work, follow the Agency flow in `publora-publishing`: discover the\nworkspace with `company_list_contexts`, read its capabilities with\n`company_get_workspace_context`, then use separate `company_*` operations\nand channel keys from `company_list_channels`.\nIf those tools are unavailable, explain that limitation instead of substituting\npersonal accounts. Keep the same draft-first sequence in either context.\n\nCall `list_connections`. Use actual account names, exact `platformId` values,\nand connection status from the result. If authorization or the tool fails,\nexplain how to reconnect/retry; do not describe the failure as an empty list.\n\nIf accounts are connected, show them and two short examples adapted to an\nactive account (or use explicit placeholders):\n\n- \"Draft a post about [topic] for my [account].\"\n- \"Schedule this draft for [date] at [time] [time zone].\"\n\nIf there are no accounts, link to [Connect a social account in Publora](https://app.publora.com/dashboard/accounts).\nExplain the steps: sign in to the same Publora account used by the plugin,\nchoose the social network, follow its connection instructions and select the\naccount/page if asked, then return and say \"Check my connected accounts.\"\nFor Telegram and networks that use credentials, follow the dashboard's own\ninstructions rather than asking for credentials in chat.\n\nIf all accounts require reconnection, use the same dashboard link and ask the\nuser to reconnect one. If only some require reconnection, offer an active one\nand identify the others clearly. Recheck connections after the user returns.\n\nA user can prepare text in chat before connecting an account. Do not invent a\nPublora draft ID or call `create_post` until a real target is available.\n\n## From a draft to the first scheduled post\n\nWhen the user wants to continue, ask for the missing topic and target account.\nUse choices and content they have already provided. Prepare the text for\nreview before asking for a publishing time. Saving a draft uses `create_post`\nwithout `scheduledTime` or `publishNow`; follow the packaged `publora-publishing` skill for\nexact target IDs and post operations. For media requirements, follow\n`publora-media`; a text proposal can be reviewed in chat before adding media.\n\nAfter the user approves the draft, obtain the missing date, time and time zone.\nSummarize the approved content, target and exact local time with its time zone.\nSchedule on the user's confirmation; do not ask again if their latest request\nalready approves those exact details. Convert the chosen time to UTC.\nCheck `account_context` for the schedule horizon or quota errors when needed;\nnever switch to immediate publication to bypass a scheduling limit.\n\nIf a saved draft already exists, schedule that draft with `update_post`, keeping\nits `postGroupId`, with `status: \"scheduled\"` and the agreed `scheduledTime`,\nrather than creating a duplicate. Omit `publishNow`. Read its current state first\nwhen needed and verify required media are ready. For an uncertain\nwrite result, inspect the existing post before retrying; reuse the same\nidempotency key and identical body for the same operation, when the tool\nsupports that key. If the current client lacks a required tool or argument,\nexplain the connection-update requirement; do not invent an argument.\n\nVerify the result with `get_post`. Report the stored status, target accounts,\nactual scheduled time (in the user's time zone), and post ID. A draft is not a\nscheduled post; scheduled is not published. If scheduling fails, explain the\nspecific repair and keep the approved draft available.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}