{"id":52036,"plugin_id":"plugin_asdk_app_6ac86f5ea1588191adc103933a9248fd","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:48:24.296Z","digest":"9f0b97a81785691d7dfb755471af85649c4a0520b33251da1947a82bbf6c8ada","against":null,"payload":{"description":"Draft, rewrite, edit, or repurpose content for a brand connected to Stanza, including articles, social posts, emails, and website copy. Use even when the user does not mention brand voice or wants the content to stay in chat.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":276}],"name":"write-with-stanza","skill_md_contents":"---\nname: write-with-stanza\ndescription: Draft, rewrite, edit, or repurpose content for a brand connected to Stanza, including articles, social posts, emails, and website copy. Use even when the user does not mention brand voice or wants the content to stay in chat.\n---\n\n# Write with Stanza\n\nUse the customer's current voice, relevant writing skills, and facts from Stanza\nto create the requested content. Explicit user instructions take precedence over\nthis skill and the brand's default style.\n\n## Before composing\n\n1. Resolve the brand from the conversation or selected article. If needed, use\n   `list_organizations` to find accessible projects. Ask which brand only when\n   the choice is ambiguous. Use that project's ID as `brand` for context tools\n   and as `projectId` for article tools; keep all retrievals scoped to it.\n2. Call `get_voice` before composing each new writing or rewriting request,\n   including follow-up requests and work that stays in chat. Apply the returned\n   choices, examples, and never-dos even when the user did not say \"in our voice.\"\n   Reuse that result while completing the request; fetch again for a new request\n   or a different brand. When the user explicitly requests another style, honor\n   it. If voice guidance is missing or cannot be retrieved, say so; use the\n   user's supplied style or offer a neutral draft without claiming it matches\n   the brand. Never invent saved guidance.\n3. For a channel or format, call `list_skills` and use `read_skill` to load the\n   relevant customer skill. An explicitly named skill can be loaded directly by\n   slug. Read its supporting files when needed. If no skill matches, continue\n   using the requested format and the voice guidance. Ask about material\n   conflicts between customer guidance when the user's request doesn't resolve\n   them.\n4. Gather the facts needed for this piece with `get_context`, `search_context`,\n   and `read_context_file`. Read an existing article with `read_article` before\n   rewriting it. Follow source links when a claim needs support; do not turn\n   missing or conflicting information into confident product claims.\n\nTool names above are the Stanza operations. Use the names exposed by the host,\nwhich may prefix them with the server or plugin name. If Stanza tools are not\navailable, explain that Stanza needs to be connected; do not pretend retrieval\nsucceeded. If product facts cannot be retrieved, use facts the user supplied or\nask for the missing information. A neutral voice is not permission to invent\nproduct details.\n\n## Compose and deliver\n\nWrite the content yourself using the retrieved guidance. Check the result\nagainst the voice's examples and never-dos, the applicable customer skill, and\nthe user's requested audience, length, and purpose. Check factual claims and\ncalls to action against the sources too: do not invent setup steps, controls,\nor product capabilities. Keep source notes outside\nthe finished copy unless citations belong in the requested format.\n\nKeep the result in chat when requested. When the user asks to save a new draft,\nuse `create_draft` and return its editor link. To change an existing article,\nuse `read_article` then `edit_article`, preserving unrelated text. Follow the\ntools' editor-opening and retry instructions for the current host. Saving a\ndraft does not publish it.\n\nThis writing workflow does not apply to factual lookups, creating blank drafts,\nsaving supplied text verbatim, or mechanical changes such as fixing a typo or\nformatting. Preserve the user's exact text in those cases; don't introduce a\nvoice rewrite. It also does not change the assistant's ordinary conversational\nvoice or apply to unrelated coding tasks.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}