[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVVAH5MM4AJSRVDMPDQASN":3,"skill-same:01M6JVVAH5MM4AJSRVDMPDQASN":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6JVVAH5MM4AJSRVDMPDQASN","archetypes-storytelling-arcs",null,"Use this skill when designing narrative content — landing pages, case studies, onboarding flows, marketing campaigns, sales decks, ad arcs. Trigger when picking how to frame a customer story, when writing a launch campaign, or when the user mentions \"this campaign feels flat\" or \"we need a better narrative.\" Sub-aspect of `archetypes`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002FSKILL.md",[18,23,28,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"archetypes storytelling arcs","archetypes","storytelling","campaigns","when","launch campaign","frame","flows","case","narrative","how to","trigger","pages","writing","campaign","use","sales","landing","read","marketing","how","customer","2026-11-10 10:12:30",false,"---\nname: archetypes-storytelling-arcs\ndescription: 'Use this skill when designing narrative content — landing pages, case studies, onboarding flows, marketing campaigns, sales decks, ad arcs. Trigger when picking how to frame a customer story, when writing a launch campaign, or when the user mentions \"this campaign feels flat\" or \"we need a better narrative.\" Sub-aspect of `archetypes`; read that first.'\n---\n\n# Storytelling arcs and the hero's journey\n\nStories are the most efficient way to convey emotional truth. A list of features is forgotten; a story of a user transformed by a product is remembered. Archetypes structure stories — the hero's journey is the most-cited template — and using them deliberately makes marketing, onboarding, and case studies dramatically more effective.\n\n## The hero's journey (Campbell, 1949)\n\nJoseph Campbell distilled cross-cultural mythology into a single recurring pattern. The full version has 17 stages; the simplified product-narrative version has roughly 8:\n\n1. **Ordinary world** — the user's status quo (their pain, their constraint).\n2. **Call to adventure** — the product is introduced.\n3. **Hesitation** — the natural skepticism, the reasons not to.\n4. **Mentor** — the product (or its team) offers guidance.\n5. **Crossing the threshold** — first use, signing up.\n6. **Trials** — the work of using the product.\n7. **Reward** — the outcome, the transformation.\n8. **Return \u002F sharing** — the user becomes an advocate.\n\nThis arc structures most successful marketing campaigns, customer case studies, and product launches.\n\n## Applying to product narratives\n\n### Customer case studies\n\nA typical case study before applying the arc:\n\n> \"Acme Corp uses our product. They report 40% productivity improvement.\"\n\nSame case study with the arc:\n\n> \"Acme Corp's marketing team was spending 4 days a week on reports — too much manual work, too little strategy. They tried our product as an experiment. After two weeks of integration, they automated 70% of their reporting workflow. Today, the team spends those reclaimed days on campaigns that have driven a 30% increase in qualified leads.\"\n\nThe arc gives the data emotional shape: pain → adventure → mentor → trials → reward.\n\n### Onboarding flows\n\nOnboarding can follow the arc:\n\n- Welcome screen acknowledges the pain (ordinary world).\n- Setup is the call (adventure).\n- Tutorial is the mentor.\n- First successful task is the threshold-crossing.\n- Building momentum is the trials.\n- Achievement screen is the reward.\n- \"Invite teammates\" is the return \u002F sharing.\n\n### Landing pages\n\nLanding pages often follow a compressed arc:\n\n- Hero section: the call.\n- Problem section: the ordinary world.\n- Solution section: the mentor (your product).\n- Social proof: testimonials of others who completed the journey.\n- CTA: cross the threshold.\n\n### Marketing campaigns\n\nA multi-touch campaign can play out across emails, ads, and content over weeks:\n\n- Week 1: name the problem (ordinary world).\n- Week 2: introduce the solution (call).\n- Week 3: address objections (hesitation).\n- Week 4: demo \u002F trial (mentor + threshold).\n- Week 5: success stories (reward).\n\n## Picking the user's role\n\nIn product narratives, who is the hero? Three typical positionings:\n\n### The user is the hero; the product is the mentor\n\nThe user's transformation is the story; the product enables it. Most user-facing marketing positions this way. The user sees themselves in the story; the product is the magical artifact.\n\n### The product is the hero\n\nLess common in modern marketing; more common in early advertising. The product itself is presented as the protagonist conquering the user's problem. Can feel inflated in modern contexts.\n\n### A different character is the hero\n\nCase studies often position a specific named customer as the hero. Their transformation is the story.\n\nThe user-as-hero positioning is generally most effective because it lets the prospect insert themselves into the story.\n\n## Other arc patterns\n\nThe hero's journey isn't the only arc:\n\n- **Three-act structure** (setup, confrontation, resolution) — used in films, drama, and many product demos.\n- **Problem-Agitation-Solution** (PAS) — common in copywriting.\n- **Before-After-Bridge** (BAB) — present current state, desired state, the path between.\n- **Story Brand framework** (Donald Miller) — a 7-part framework derived from Campbell's work, applied to brand messaging.\n\nEach is a structured way to give content emotional shape.\n\n## Anti-patterns\n\n- **All features, no narrative.** Bullet lists of features without the story of what they enable.\n- **Inflated narrative.** Treating routine product use as a hero's journey produces hyperbolic copy that erodes credibility.\n- **No transformation.** Stories that don't show change (\"Customer uses our product. End.\") fail to engage.\n- **Hero confusion.** Who is the protagonist? If unclear, the story flattens.\n- **Skipping the trials.** Stories that go directly from problem to triumph feel unrealistic; users know real adoption involves friction.\n\n## Heuristics\n\n1. **The \"what's the transformation?\" check.** Every effective narrative has a before\u002Fafter. If your story has no transformation, it's not yet a story.\n2. **The hero clarity test.** Read your narrative. Who is the protagonist? If you can't tell in 3 seconds, fix.\n3. **The trial honesty.** Skipping over the work makes the story unbelievable. Brief acknowledgment of the friction makes the triumph credible.\n\n## Related sub-skills\n\n- **`archetypes`** (parent).\n- **`archetypes-brand-voice`** — voice consistency reinforces narrative.\n- **`storytelling`** (cognition) — narrative as memory aid.\n- **`framing`** (cognition) — how the story is framed affects user judgment.\n","# Storytelling arcs and the hero's journey\n\nStories are the most efficient way to convey emotional truth. A list of features is forgotten; a story of a user transformed by a product is remembered. Archetypes structure stories — the hero's journey is the most-cited template — and using them deliberately makes marketing, onboarding, and case studies dramatically more effective.\n\n## The hero's journey (Campbell, 1949)\n\nJoseph Campbell distilled cross-cultural mythology into a single recurring pattern. The full version has 17 stages; the simplified product-narrative version has roughly 8:\n\n1. **Ordinary world** — the user's status quo (their pain, their constraint).\n2. **Call to adventure** — the product is introduced.\n3. **Hesitation** — the natural skepticism, the reasons not to.\n4. **Mentor** — the product (or its team) offers guidance.\n5. **Crossing the threshold** — first use, signing up.\n6. **Trials** — the work of using the product.\n7. **Reward** — the outcome, the transformation.\n8. **Return \u002F sharing** — the user becomes an advocate.\n\nThis arc structures most successful marketing campaigns, customer case studies, and product launches.\n\n## Applying to product narratives\n\n### Customer case studies\n\nA typical case study before applying the arc:\n\n> \"Acme Corp uses our product. They report 40% productivity improvement.\"\n\nSame case study with the arc:\n\n> \"Acme Corp's marketing team was spending 4 days a week on reports — too much manual work, too little strategy. They tried our product as an experiment. After two weeks of integration, they automated 70% of their reporting workflow. Today, the team spends those reclaimed days on campaigns that have driven a 30% increase in qualified leads.\"\n\nThe arc gives the data emotional shape: pain → adventure → mentor → trials → reward.\n\n### Onboarding flows\n\nOnboarding can follow the arc:\n\n- Welcome screen acknowledges the pain (ordinary world).\n- Setup is the call (adventure).\n- Tutorial is the mentor.\n- First successful task is the threshold-crossing.\n- Building momentum is the trials.\n- Achievement screen is the reward.\n- \"Invite teammates\" is the return \u002F sharing.\n\n### Landing pages\n\nLanding pages often follow a compressed arc:\n\n- Hero section: the call.\n- Problem section: the ordinary world.\n- Solution section: the mentor (your product).\n- Social proof: testimonials of others who completed the journey.\n- CTA: cross the threshold.\n\n### Marketing campaigns\n\nA multi-touch campaign can play out across emails, ads, and content over weeks:\n\n- Week 1: name the problem (ordinary world).\n- Week 2: introduce the solution (call).\n- Week 3: address objections (hesitation).\n- Week 4: demo \u002F trial (mentor + threshold).\n- Week 5: success stories (reward).\n\n## Picking the user's role\n\nIn product narratives, who is the hero? Three typical positionings:\n\n### The user is the hero; the product is the mentor\n\nThe user's transformation is the story; the product enables it. Most user-facing marketing positions this way. The user sees themselves in the story; the product is the magical artifact.\n\n### The product is the hero\n\nLess common in modern marketing; more common in early advertising. The product itself is presented as the protagonist conquering the user's problem. Can feel inflated in modern contexts.\n\n### A different character is the hero\n\nCase studies often position a specific named customer as the hero. Their transformation is the story.\n\nThe user-as-hero positioning is generally most effective because it lets the prospect insert themselves into the story.\n\n## Other arc patterns\n\nThe hero's journey isn't the only arc:\n\n- **Three-act structure** (setup, confrontation, resolution) — used in films, drama, and many product demos.\n- **Problem-Agitation-Solution** (PAS) — common in copywriting.\n- **Before-After-Bridge** (BAB) — present current state, desired state, the path between.\n- **Story Brand framework** (Donald Miller) — a 7-part framework derived from Campbell's work, applied to brand messaging.\n\nEach is a structured way to give content emotional shape.\n\n## Anti-patterns\n\n- **All features, no narrative.** Bullet lists of features without the story of what they enable.\n- **Inflated narrative.** Treating routine product use as a hero's journey produces hyperbolic copy that erodes credibility.\n- **No transformation.** Stories that don't show change (\"Customer uses our product. End.\") fail to engage.\n- **Hero confusion.** Who is the protagonist? If unclear, the story flattens.\n- **Skipping the trials.** Stories that go directly from problem to triumph feel unrealistic; users know real adoption involves friction.\n\n## Heuristics\n\n1. **The \"what's the transformation?\" check.** Every effective narrative has a before\u002Fafter. If your story has no transformation, it's not yet a story.\n2. **The hero clarity test.** Read your narrative. Who is the protagonist? If you can't tell in 3 seconds, fix.\n3. **The trial honesty.** Skipping over the work makes the story unbelievable. Brief acknowledgment of the friction makes the triumph credible.\n\n## Related sub-skills\n\n- **`archetypes`** (parent).\n- **`archetypes-brand-voice`** — voice consistency reinforces narrative.\n- **`storytelling`** (cognition) — narrative as memory aid.\n- **`framing`** (cognition) — how the story is framed affects user judgment.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fnarrative-frameworks.md","REFERENCE","参考文档",1770,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002Freferences\u002Fnarrative-frameworks.md",[93,103,111,119,127,135],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":102},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":102},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":102},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":102},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":102},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":102},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]