Update to Daoco

{
  "description": "Read and apply a personal or business brand's saved voice, audience, positioning, and visual identity from Daoco. Use for brand questions or to ground the user's current work in their Daoco context.",
  "included_files": [],
  "name": "daoco-brand-context",
  "skill_md_contents": "---\nname: daoco-brand-context\ndescription: Read and apply a personal or business brand's saved voice, audience, positioning, and visual identity from Daoco. Use for brand questions or to ground the user's current work in their Daoco context.\n---\n\n# Use brand context\n\nRead [the shared Daoco workflow](../daoco-marketing/SKILL.md) for brand selection and tool boundaries. Call `get_brand_context` for the selected brand and use the relevant facts and documents to answer or inform the user's work. Pass `task` to get the context for one piece of work (the visual style Daoco would use, the logo, and matching document passages), or `sections` for the full visual identity or document list. Use `search_brand` to find passages in brand documents or core brand images, and to read a document's full text by its `documentId`. These reads use no workspace tokens.\n\nIf `get_brand_context` reports `setup`, the brand is still being set up; follow `daoco-brand-setup` instead of treating its context as complete.\n\nFor a personal brand, preserve the person's stated expertise, point of view, audience, and preferred voice. Do not invent credentials, personal experiences, endorsements, or first-person stories, and do not treat a belief Daoco inferred as one the person stated. When the person's opinions, stories, audience, or positioning are thin, Daoco can ask for them: `/beliefs` and `/stories` (personal brands), `/audience`, and `/positioning` start a short interview through `start_work`. Each run asks its questions and offers candidates, then ends; the person replies through `continue_work` on that thread with the same command and their answers, in their words. The result is proposed for the person to review in Daoco, not applied. For a business brand, preserve its offers, customers, positioning, and approved claims. The saved context and the user's request determine the voice; do not assume every personal brand speaks casually or every business uses \"we.\"\n\nDistinguish saved facts from your suggestions. If a material detail is missing, ask a focused question or state the gap. Do not turn a brand question into a paid work request. If the user asks to update the saved brand, delegate that request through `start_work` or the relevant existing thread and report the actual result. Daoco proposes brand changes for review in Daoco; a proposal is not a saved change.\n\n## Turn context into useful guidance\n\nAnswer the brand question rather than dumping every saved document. When the user asks how to write in their voice, extract the relevant traits and show a short application grounded in their material. Keep your example distinct from a saved brand rule.\n\nFor a voice review, compare the supplied text with the saved guidance. For a fuller check of a draft (would the audience recognize the problem, can every claim be supported), `/read-through` runs one in Daoco. Point to specific phrases, explain the mismatch, and suggest a revision without changing supported claims. Reading context and advising in this chat does not require starting a paid Daoco run. Creating durable marketing deliverables or saving changes does.\n\nIf saved documents conflict, identify the conflict and prefer a clearly dated or explicitly designated current source. Ask when that choice would materially affect the answer and the current source is unclear. Do not quietly merge contradictory positioning or treat a suggestion from this conversation as saved brand truth.\n"
}