skills/marketing/brand-storytelling/SKILL.md
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
npx skillsauth add pedronauck/skills brand-storytellingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user craft compelling narratives that make their brand memorable using techniques from 30 product leaders and storytelling experts.
When the user asks for help with brand storytelling:
Andy Raskin: "This structure is about defining a movement—that's very different from 'I'm going to solve your problem.'" Frame your brand as the leader of a shift toward a new way of winning.
Brian Chesky: "One of the first things we do is figure out what the story is. The story often dictates the product. A story is a helpful way to develop a cohesive product." Define the narrative before finalizing features.
Matthew Dicks: "Every story is about a singular moment—I call it five seconds. A moment of transformation or realization. 98% of the story provides context to make that moment clear." Identify the single moment of change.
Merci Grace: "Every pitch should start in the middle of the action, like Mission Impossible. Tom Cruise is always doing crazy shit before the actual mission. It gets attention." Skip the boring setup—hook them immediately.
Jason Feifer: "Success stories aren't interesting. Problem-solving stories are. Frame your story around a specific challenge you faced and the counterintuitive way you solved it."
Mike Maples Jr: "The customer is the hero (Luke Skywalker), the founder is the mentor (Obi-Wan) providing the tools. Position your product as the lightsaber—the tool the hero needs."
Lulu Cheng Meservey: "Make it memorable. Make people want to say it of their own volition. Use analogies, colorful mental images, jokes. Replace adjectives with anecdotes people can repeat at dinner."
Camille Ricketts: "Effective storytelling paints an emotional picture of the vision. Convey the emotional quality of the mission, not just technical details, to enlist hearts and minds."
Christina Wodtke: "A beginning, middle, and end. Intrigue with a hook—a mystery, secret, or surprise. The middle delivers the message. Always end with success and celebration."
Yuhki Yamashata: "The goal is 'memification'—synthesize insights so they're catchy enough for execs to cite in meetings. Use metaphors to explain complex concepts."
For all 50 insights from 30 guests, see references/guest-insights.md
tools
Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.
development
Executes real-user QA sessions through public interfaces using personas, journeys, exploratory charters, test tours, edge-case probes, CFR checks, and browser evidence. Reads qa-report artifacts from <qa-output-path>/qa/ when present, captures issues/screenshots/reports under the same output tree, and classifies bugs by user impact. Use when validating a release candidate, migration, refactor, or user-facing change against production-like behavior. Do not use for AI implementation audits, task-status reconciliation, CI gate runs, integration/security/performance templates, or flaky-test triage; use agent-output-audit for those.
development
Transform outside-of-diff review files into properly formatted issue files for a given PR. Use when converting review files from ai-docs/reviews-pr-<PR>/outside/ into issue format in ai-docs/reviews-pr-<PR>/issues/. Automatically determines starting issue number and preserves all metadata (file path, date, status) from original review files. Don't use for inline-diff review files, non-PR review artifacts, or creating GitHub issues directly.
development
Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.