Talk Story Structure , narrative patterns for conference talks and lectures
Story patterns for conference talks and lectures distilled from years of real decks: hooks from the audience's present, crosshead transitions, 3-part concept intros, closings without summary slides, timing estimates, AI-smell checks
- What
- Story patterns for conference talks and lectures distilled from years of real decks: hooks from the audience's present, crosshead transitions, 3-part concept intros, closings without summary slides, timing estimates, AI-smell checks
- Cost
- Free
- Needs
- none beyond a slide authoring setup (built to pair with Marp, but the story patterns apply to any slide tool).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: narrative patterns for building conference talks and lectures that hold a room: start from where the audience is (never from a definition), connect sections with crosshead slides written as the audience's inner questions, introduce concepts in three beats, close with a call to action instead of a summary slide, and estimate timing from real per-slide rates. Includes an AI-smell checker that counts repeated heading patterns so the deck does not read as machine-written. by @minorun365, listed here with credit to its creator. Honest caveats: the skill content is written in Japanese (the patterns themselves are language-independent); it assumes you build the talk as a story told aloud, not as a handout. Skill Harbor never reviews the code, review it yourself before use. Discovered via GitHub.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Prerequisites: none beyond a slide authoring setup (built to pair with Marp, but the story patterns apply to any slide tool). Install "Talk Story Structure , narrative patterns for conference talks and lectures" for me. It gives my agent @minorun365's story patterns distilled from years of real decks: audience-first hooks, crosshead transitions, 3-beat concept intros, closings without summary slides, timing estimates, and an AI-smell check on headings. Note: the skill text is in Japanese; the patterns apply regardless of talk language. Repository: https://github.com/minorun365/minorun-marp-skill/blob/main/skills/slide-story/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "slide-story". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing technical , just bring a talk topic and let the skill structure it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.