Creative

Trip plans, collections, and other projects Muse can research and organize for you.

9 of 9 skills

type

Bedtime Story Weaver
Turns a child's details into a short tale with a recurring hero.
skillinstructionsworkflowcontinuity-log
by Muse Skills editors · Written for this directory
ViewInstall the "Bedtime Story Weaver" skill. Its full source is below. Create it at ~/workspace/skills/bedtime-story-weaver/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: bedtime-story-weaver description: Weave a personalized bedtime story for a child, starring a recurring hero across nights. Trigger phrases: "weave a bedtime story", "tell a story with our hero", "continue last night's story". --- # Purpose Turn a child's details into a short, cozy tale starring a recurring protagonist who grows with the child. The hero persists across nights: names, friends, and favorite places carry over, so each new story feels like the next chapter of one ongoing adventure. # Workflow 1. Ask for the child (first name, age), the hero (name, species or kind, one personality trait), and tonight's theme or setting if the user has one. 2. Load the hero profile and continuity log from prior runs: who the hero knows, where they have been, what they learned. 3. Build tonight's outline: one small quest or problem, one helper character (new or returning), one gentle lesson, and a calm ending that winds the energy down. 4. Draft the story for reading aloud: 5 to 8 minutes of reading, simple sentences for younger ages, slightly richer language for older kids. 5. End with an optional soft cliffhanger: a hint of tomorrow's adventure that invites sleep, never suspense. 6. Update the continuity log with new characters, places, and lessons so the next story can reference them. # Output Contract The story text, ready to read aloud, followed by three lines: - Hero update: what changed for the hero tonight - Tonight's gentle point: the lesson, stated simply - Tomorrow's hint: one sentence, only if a cliffhanger was requested First run also returns the hero profile card for approval before the first story is written. # Operating Rules - Never write frightening, violent, or age-inappropriate content. If a theme is too dark, steer it gentle and say why. - Never introduce real people without the user's permission; use the hero and fictional friends. - Never keep personal details the user has not approved for the hero profile. Ask before adding anything new to the profile. - Keep the story length right for reading aloud: under ten minutes unless the user asks for more. - If the child is scared or restless mid-story, offer a shorter, calmer ending instead of pushing through.
Voice Matched Writer
Learns your voice from writing samples, then drafts new posts in it.
skillinstructionsworkflowvoice-profile
by Muse Skills editors · Written for this directory
ViewInstall the "Voice Matched Writer" skill. Its full source is below. Create it at ~/workspace/skills/voice-matched-writer/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: voice-matched-writer description: Learn a writer's voice from their samples, then draft new posts in it. Trigger phrases: "write this in my voice", "match my voice", "draft a post like me". --- # Purpose Write like yourself on a busy day. Voice Matched Writer builds a voice profile from writing samples you provide, then drafts new posts, captions, or updates that sound like you wrote them: your sentence rhythms, your vocabulary habits, your humor level, your openings and closings. The goal is a draft that needs light edits, not a rewrite. # Workflow 1. The user provides 5 to 15 samples of their own writing in the target form: posts, captions, scripts, newsletters. More than 15 dilutes the profile; fewer than 5 makes it generic. 2. Read the samples and extract a voice profile: sentence length patterns, favorite words and phrases, punctuation habits, rhythm, humor style, how pieces open and close, what the voice never does. 3. Save the voice profile. It persists until the user replaces it or adds more samples. 4. When the user asks for a draft, read their brief: topic, key points, length, platform, and anything to avoid. 5. Draft to the brief first, then apply the voice profile. Accuracy on the content always outranks style matching. 6. Deliver the draft with a short note on the two or three voice traits applied most strongly, so the user can judge whether the match feels right. # Output Contract Each draft comes with: - The draft itself, sized to the platform - The brief it answers, restated in one line - Two or three voice traits applied, named briefly The user edits or approves. Nothing publishes on its own. # Operating Rules - Never publish, post, schedule, or send a draft anywhere. Draft only, every time. - Never learn a voice from anyone else's writing. Samples must be the user's own, or work they have the right to reuse. - Never use the samples for anything besides building the profile, and never quote them back in new drafts. - If the samples show two or more distinct voices, say so and ask which one to keep before writing. - If the brief conflicts with the voice (a formal topic in a casual voice), flag the tension instead of forcing the match. - Keep the user's voice profile in their workspace, and treat it as private: never copy it to another user or skill.
Toast Writer
Turns a few real anecdotes into a short, warm toast or celebration speech.
Tested in Museskillinstructionsworkflowexamples
by Muse Skills editors · Written for this directory
ViewInstall the "Toast Writer" skill. Its full source is below. Create it at ~/workspace/skills/toast-writer/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: toast-writer description: Turn a few real anecdotes into a short, personal toast or celebration speech, timed to your slot and tuned to your tone. Trigger phrases: "write my toast", "help with my wedding speech", "draft a best man speech". --- # Purpose Write a toast or short celebration speech that sounds like you, not like a greeting card. It takes the occasion, the people, your real anecdotes, and the tone you want, then drafts a speech that fits your time slot and lands the ending on a genuine wish. # Workflow 1. Ask for the occasion (wedding, birthday, retirement, holiday dinner), the speaker's role (best man, parent, friend, host), and who is being toasted. 2. Ask for 3 to 5 real anecdotes or facts about the person, in the user's own words. If they get stuck, offer simple prompts: how you met, a funny moment, a quality you admire. 3. Ask for the tone: warm, funny, sentimental, or a mix. Ask for any lines, jokes, or topics that are off limits. 4. Ask for the time slot (for example, two minutes, five minutes) and convert it to a target word count at about 130 words per minute of speaking. 5. Draft the speech in this shape: a short opener naming the occasion, two or three anecdote beats in the user's tone, then a closing toast line that raises the wish. Keep sentences short enough to say out loud. 6. Note the estimated speaking time next to the draft. 7. Offer up to two revision passes on tone, length, or a single anecdote, then stop and hand the draft back. # Output Contract - Draft speech in paragraph form, with the final toast line set apart. - Estimated speaking time, based on 130 words per minute. - Revision options: tone, length, or one anecdote, two passes max. # Operating Rules - Never invent anecdotes, facts, or backstories about real people. If the user provides nothing, ask again; do not fill the gap with fiction. - Never name or roast anyone the user flagged as off limits. - Never publish, send, or read the speech to anyone. The draft stays with the user. - Keep the draft within 15% of the target word count. - Prefer concrete detail from the user's own stories over greeting-card lines.
Photo Caption Writer
Photo in, caption options out, matched to the platform.
Tested in Museprompt packprompt-text
by Muse Skills editors · Written for this directory
ViewInstall the "Photo Caption Writer" prompt pack. Its full source is below. Save it to ~/workspace/prompts/photo-caption-writer.md (create the folder if needed). Then confirm it is installed and show me the full text. --- SOURCE --- This prompt pack writes captions for a photo. Paste it into Muse along with the photo and where it's going. > Write 5 caption options for this photo, for [Instagram / > X / Facebook]. Mix the styles: one straightforward, one > funny, one minimal (under 6 words), one with a question to > drive replies, one storytelling (2-3 sentences). Rules: > match my voice, [describe it, or say "match the tone of my > last 3 posts"], no hashtags in the caption itself (list 5-8 > separately), no emojis unless I ask, and never invent details > about the photo that aren't visible, if you're unsure what > something is, keep it general.
Playlist Builder
Event plus vibe plus length: a sequenced playlist brief.
Tested in Museprompt packprompt-text
by Muse Skills editors · Written for this directory
ViewInstall the "Playlist Builder" prompt pack. Its full source is below. Save it to ~/workspace/prompts/playlist-builder.md (create the folder if needed). Then confirm it is installed and show me the full text. --- SOURCE --- This prompt pack builds a sequenced playlist brief. Paste it into Muse along with the event details. > Build me a playlist brief for [event]: [vibe], about [length]. > Structure it in arcs: the opener (first 3 songs set the > tone), the build (energy rises), the peak (the 20 minutes > everyone remembers), and the landing (wind down or last-call > energy). For each song: title, artist, and one line on why > it's here. Rules: sequence for flow, no jarring genre jumps > between adjacent songs, keep it to songs I'd actually know > or that fit the crowd ([describe the crowd]), and end with > 3 swap-in alternates in case the mood shifts.
Pantry Cook
Photo the fridge; get three things you can make tonight.
Tested in Museprompt packinstructionsrecipe-template
by Muse Skills editors · Written for this directory
ViewInstall the "Pantry Cook" prompt pack. Its full source is below. Save it at ~/workspace/prompts/pantry-cook.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "cook from my pantry", "what can I make with these ingredients", "suggest pantry dinners". --- SOURCE --- # Pantry Cook How to use: photo your fridge, pantry, or both, or paste a list of what you have. It suggests three dinners you can make right now, ranked by how little you are missing. Trigger phrases: "cook from my pantry", "what can I make with these ingredients", "suggest pantry dinners". ## The prompt Look at my ingredients and suggest 3 dinners I can make tonight. 1. List what you can see, grouped loosely: proteins, vegetables, carbs, dairy, sauces and seasonings. 2. Suggest 3 meals, ranked by fewest missing ingredients first. 3. For each meal: name, the 3-5 key steps (short), time estimate, and any missing ingredient clearly marked as "you'd need to buy: X". 4. At least one suggestion must use only what is visible: no missing ingredients at all. 5. Keep each recipe to 5 steps or fewer. No preamble about your love of cooking. Rules: never assume an ingredient that is not visible or listed. If the photo is unclear, ask about the 2-3 items that matter most instead of guessing.
Record Fair Battle Plan
Your wantlist plus your budget becomes a one-page fair plan with max prices.
Tested in Museskillinstructionsworkflowwantlist
by Muse Skills editors · Written for this directory
ViewInstall the "Record Fair Battle Plan" skill. Its full source is below. Create it at ~/workspace/skills/record-fair-battle-plan/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: record-fair-battle-plan description: Turn a wantlist, a budget, and a fair's vendor list into a one-page battle plan: priority targets with max prices so you never overpay. Trigger phrases: "plan my fair", "record fair plan", "prep for the fair". --- # Purpose Walk into a record fair with a plan instead of a vague hope. The skill takes the wantlist, the budget, and whatever is known about the fair, and produces a one-page sheet: what to hunt, what to pay, what to skip. # Workflow 1. Read the user's wantlist (artist, title, pressing details where known) and the total budget for the fair. 2. For each wantlist item, look up recent sold prices for the matching pressing. Set the max price at the low end of recent solds, minus 10% (fair haggling margin). 3. Rank the wants: top targets (rarely seen for sale, fairly priced max), opportunistic (buy only if under max), skip-at-fair (cheaper online: say so). 4. If a vendor list is available, note which vendors are most likely to carry the top targets (genre specialists first). 5. Divide the budget across the top targets; show the running total so the user sees what fits. 6. Write the one-page plan in the Output Contract shape. # Output Contract A single page: - **Top targets:** up to 5, each with max price and one line on why - **Opportunistic:** the rest of the wantlist with max prices - **Skip at the fair:** items cheaper or easier to find online, with the online price noted - **Budget:** total budget, allocated across top targets, remainder shown # Operating Rules - Max prices come from sold data, low end of the range, never asking prices. - Never inflate a max price because the user "really wants it". The number is the number. - If sold data is too thin for an item, mark it "no comp: set your own ceiling" rather than guessing. - The plan is advice only. It never buys, bids, or contacts a vendor.
Trip Planner
Builds a day-by-day itinerary with time blocks, cost estimates, and links to research.
Tested in Museprompt packprompt pack
by Muse Skills editors · Written for this directory
ViewInstall the "Trip Planner" prompt pack. Its full source is below. Save it at ~/workspace/prompts/trip-planner.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "plan my trip", "build a travel itinerary", "help me plan this trip". --- SOURCE --- # Trip Planner Fill in the slots below, then send the whole prompt. Trigger phrases: "plan my trip", "build a travel itinerary", "help me plan this trip". Plan a trip with these details: - Destination: [destination] - Dates: [start date] to [end date] - Budget: [total budget, or per-day budget] - Travel style: [pace and style, e.g. "relaxed, mid-range hotels, mostly walking" or "packed, budget hostels, public transit"] - Must-dos: [places, activities, or foods that must be in the plan] - Travelers: [number of people, and any constraints such as kids, mobility, or dietary needs] Build a day-by-day itinerary from the arrival date to the departure date. For each day: - Break the day into time blocks (morning, afternoon, evening), each with one main activity and its estimated duration. - Fit every must-do into a specific day and time block. Do not drop one without saying so and why. - Give a cost estimate for each paid activity, meal, and transit leg, in the destination's local currency and in the traveler's stated budget currency if different. - Include one link to research each paid activity or booking (the official site or a well-known booking platform), for the user to verify and book themselves. - Flag anything that needs advance booking (timed tickets, popular restaurants, transit passes) and how far ahead to book it. After the day-by-day plan, give a total cost estimate against the stated budget, and call out anywhere the plan runs over. State clearly, once, at the end: all prices are estimates from research, not live quotes, and the user must verify current prices and availability before booking anything. ## How to use Fill in the six bracketed fields with your trip details, then send the whole prompt to the assistant. Answer any follow-up question about a missing detail (an unclear budget, an ambiguous must-do) so the plan can fit it into a specific day.
Vinyl Vault
Catalogs your record collection from photos or lists and tracks its value.
Tested in Museskillinstructionsworkflowwantlist
by Muse Skills editors · Written for this directory
ViewInstall the "Vinyl Vault" skill. Its full source is below. Create it at ~/workspace/skills/vinyl-vault/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: vinyl-vault description: Catalogs a vinyl record collection from photos or pasted lists (artist, title, pressing, condition), keeps a wantlist, and estimates collection value from recent sold prices. Trigger phrases: "add these records", "catalog my vinyl", "what's my collection worth", "add to my wantlist". --- # Purpose Track a vinyl record collection: what you own, its condition, its estimated value, and what you want next. # Workflow 1. When the user adds records, accept a photo of album covers or spines, or a pasted text list. 2. For each record, extract or ask for: artist, title, pressing or edition (year, country, label if known), and condition (Mint, Near Mint, Very Good Plus, Very Good, Good, Poor). 3. If condition is missing, ask once. Do not guess a condition. 4. Append each new record to `collection.md` in the workspace, one row per record, with the date added. 5. When the user says a title, artist, or "wantlist", add it to `wantlist.md` with the date added. Remove an item from the wantlist when the same title appears in `collection.md`. 6. When the user asks for collection value, or once a month if the user has asked for a monthly report, look up recent sold prices for each pressing using the assistant's own web search. Match on artist, title, and pressing details. Use the median of the last 5 sold listings in the matching condition band. 7. If no sold listings match a pressing, mark that record "no comp found" and exclude it from the total. Do not estimate from an unrelated pressing. 8. Report the total, the count of records with no comp, and the 5 records that moved most in value since the last report, if a previous report exists. # Output Contract - `collection.md`: a table with columns Artist, Title, Pressing, Condition, Date Added, Last Estimated Value, Comp Date. - `wantlist.md`: a table with columns Artist, Title, Date Added, Notes. - A value report states: total estimated value, number of records counted, number excluded for no comp, and the top movers. - Every value in a report carries its comp date. A value never appears without one. # Operating Rules - Never buy, bid on, or list a record on any marketplace. - Never contact a seller, dealer, or marketplace on the user's behalf. - Never invent a pressing detail or a sold price. State "no comp found" instead. - Do not ask for payment details, login credentials, or an API key for any marketplace. Use only the assistant's own web search for comps. - A monthly report runs only when the user has asked for one, and it sends nothing when the collection has not changed and no new comps exist worth reporting.