{"id":53825,"plugin_id":"plugins_6ac5e934d1f88191b73fe472c16744ae","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:55:10.302Z","digest":"c2b1188ebc9637038d948ca9597ae57ab8afe5dd6daa962f897b09443d810101","against":null,"payload":{"description":"Shape truthful, human-centered founder, customer, and brand stories without inventing events, outcomes, or emotional claims.","included_files":[],"name":"storytelling","skill_md_contents":"---\nname: storytelling\ndescription: Shape truthful, human-centered founder, customer, and brand stories without inventing events, outcomes, or emotional claims.\n---\n# Storytelling\n\nUse for personal stories, founder narratives, educational stories, and customer stories. The purpose is clear communication, not emotional pressure or proof by anecdote.\n\n## Gather and label source material\n\n- Ask what the story needs to accomplish, who will see it, and where it may be used.\n- Establish whether facts come from the user, approved records, a consenting person, a composite, or a fictional example. State what the AIOS has and has not inspected.\n- Separate documented events, the speaker's own interpretation, and details that are unknown. Do not invent dialogue, chronology, motivations, credentials, customer outcomes, or quotations.\n- For identifiable customer stories, confirm that the user has appropriate permission for the intended channel and claims. Recommend removing unnecessary identifying or sensitive details.\n\n## Build the narrative\n\n1. Situation and context, without adding unsupported background.\n2. Tension, question, or decision that mattered to the person.\n3. Actions actually taken and relevant alternatives or constraints.\n4. Outcome only when supplied and supportable; keep attribution and limitations clear.\n5. Reflection or useful lesson, labeled as the storyteller's perspective rather than a universal rule.\n6. Optional next step suited to the audience and funnel stage, with no implied entitlement to a response.\n\nUse plain, specific language. Preserve the person's meaning and voice. Do not turn a single anecdote into a general customer insight or imply that a personal experience proves an offer works.\n\n## Review before use\n\nCheck factual fidelity, consent, privacy, evidence labels, claim support, and context. Flag unsupported or contradicted numerical claims and give a source-backed correction when available. Keep the user's editorial choice separate from what the evidence supports. If material is fictional or composite, label the output clearly as **EXAMPLE / SYNTHETIC — NOT A CUSTOMER STORY**.\n\n## Standard output\n\nProvide the story's purpose and evidence status, a draft in the requested format, any claim/consent questions that block publication, and a concise edit note identifying assumptions or details still needing confirmation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}