Movie Sidekick

Answers questions about the film you are watching without spoiling what comes next.

Tested in MuseskillCreativeProduction and cast facts on requestA strict no-spoilers line at the scene you nameShort answers sized for mid-film questionsOpinions when you ask for themA fuller debrief once the film ends

by Muse Skills editors · Written for this directory

To install the Movie Sidekick skill, save the skill source below as ~/workspace/skills/movie-sidekick/SKILL.md, then tell Muse to use it whenever you are watching a film and ask about it.

--- SOURCE ---
---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

View source

Ready to copy.

Details

Type: skill
Category: Creative
Version: 1.0.0
Added: 4 Nov 2026
Author: Muse Skills editorsWritten for this directory
Includes: Production and cast facts on requestA strict no-spoilers line at the scene you nameShort answers sized for mid-film questionsOpinions when you ask for themA fuller debrief once the film ends
Source: github.com/…/movie-sidekick.md

To install the Movie Sidekick skill, save the skill source below as ~/workspace/skills/movie-sidekick/SKILL.md, then tell Muse to use it whenever you are watching a film and ask about it.

--- SOURCE ---
---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

Before you install

A shared skill carries somebody else's instructions. Read the source before you install it.
Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
Installing copies the setup into your own environment. It gives the author nothing.

What it does

What it includes

Half the fun of rewatching a film, or catching an older one for the first time, is the running commentary: who that actor is, whether a scene was shot on location, why a shot looks the way it does. This skill plays that companion role without the usual risk of an assistant blurting out the ending. You name the film and the scene you have reached, and that point becomes a hard boundary. Ask about cast, production, or context and get a short answer you can read at a glance. Ask for an opinion and get one, based only on what has happened so far. When the credits roll, the boundary lifts and the skill can debrief the whole film, ending included.

Example

You are watching the first Star Trek film and say so, adding that the Enterprise has just left drydock. You ask who directed it and whether the drydock sequence was a model or a set. The skill answers briefly: Robert Wise directed, and the sequence used a large miniature shot to feel slow and grand. You ask if a character who just appeared survives the film. The skill declines, notes your place in the story, and offers to answer once you are past the finale. After the credits, you say you finished, and it gives the fuller read: the pacing debate, the effects history, and that question answered at last.

What this one touches

Never reveals plot events past the point the user names, even when asked directly in the moment; it offers to answer after that scene instead. Never invents a production fact; if a detail cannot be verified, it says so. It reads nothing and contacts no one; it works from the film title and the scene the user describes.

Install

Copy this block and paste it into your Muse chat. Muse does the install and confirms when it's done.

Install prompt

To install the Movie Sidekick skill, save the skill source below as ~/workspace/skills/movie-sidekick/SKILL.md, then tell Muse to use it whenever you are watching a film and ask about it.

--- SOURCE ---
---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

To install the Movie Sidekick skill, save the skill source below as ~/workspace/skills/movie-sidekick/SKILL.md, then tell Muse to use it whenever you are watching a film and ask about it.

--- SOURCE ---
---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

Full source

This is the exact text Muse installs. Read it. That's the whole trust model.

SKILL.md

---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

---
name: movie-sidekick
description: A watch-along companion for a film in progress: production facts, cast facts, and opinions, with nothing revealed past the scene the user names. Use when the user says "watching", "movie sidekick", "who is that actor", "was this filmed", names a film they are partway through, or asks about a scene they just watched.
---

## Purpose
Make watching a film with an assistant feel like watching with a knowledgeable friend: quick answers about who is on screen, how a scene was made, and what to think of it, without ever ruining what comes next. The user names the film and where they are in it; everything the skill says stays behind that line.

## Workflow
1. Set the line: ask which film the user is watching and where they are, a scene description or a timestamp. Treat that point as the spoiler boundary for the whole session.
2. Answer in short form while the film runs: a cast fact, a production note, or a piece of context, kept brief so the user can glance and keep watching.
3. Update the line as the user reports new scenes. Facts about events up to the new point become fair game; anything past it stays off limits.
4. Give opinions only when asked, and base them on what has happened up to the line: a performance, a shot, a line of dialogue.
5. When the user says the film is over, lift the boundary and offer a fuller debrief: themes, ending questions, and what to watch next if they want it.

## Output Contract
- Mid-film answers are short: a few sentences at most, one fact or one opinion each.
- Every answer respects the spoiler boundary the user last set.
- Facts the skill cannot verify are flagged as uncertain rather than stated flatly.
- The end-of-film debrief is offered, not imposed, and comes only after the user confirms they finished.

## Operating Rules
- Never reveal, hint at, or confirm plot events past the user's named point, including twists the user guesses at. Offer to revisit the question once they pass that scene.
- Never use knowledge of the ending to color a mid-film answer, even vaguely.
- If the user's scene description is ambiguous, ask which scene they mean before answering anything plot related.
- Keep answers short during the film. Save long explanations for the debrief or for a direct request.
- If a production or cast fact cannot be checked, say it is unverified instead of presenting it as settled.

Costume Coordinator
Plans a group costume theme and assigns each person a look within your budget.
skillGroup costume theme shortlist matched to your people and occasionOne costume assigned to each person, with sizes and comfort notesBuy links for each piece, with a running budget tallyTimeline that leaves time for shipping, fitting, and fixesBackup plan when a piece is out of stock or does not fit
by Muse Skills editors · Written for this directory
ViewTo install the Costume Coordinator skill, save the skill source below as ~/workspace/skills/costume-coordinator/SKILL.md, then tell Muse to use it whenever you are planning a group or family costume theme for a holiday and want each person assigned a look within a budget. --- SOURCE --- --- name: costume-coordinator description: Plan a group or family costume theme for a holiday. Use when the user wants a theme, a costume assigned to each person, buy links, a budget tally, and a timeline that leaves time for shipping. --- ## Purpose Turn a holiday costume idea into a finished plan for the whole group. The skill picks a theme that fits the people involved, assigns one costume to each person, finds buy links for each piece, keeps a running tally against the budget, and builds a timeline that leaves time for shipping, fitting, and fixes before the day arrives. ## Workflow 1. Take the occasion, the people, and the budget: names, ages, sizes, and anything anyone will not wear. 2. Suggest two or three themes that fit the group, and let the user pick one. 3. Assign one costume to each person in the theme, matching the role to the person where it matters, such as the tallest person playing the tallest character. 4. Find a buy link for each piece, with a price, and tally the total against the budget. Flag the plan when it runs over, and suggest a swap or a homemade piece to bring it back. 5. Build a timeline working back from the event date: order by date, fitting and fix time, and a final check the day before. 6. Name a backup for each piece that could sell out or arrive in the wrong size. ## Output Contract - The chosen theme and a one line reason it fits the group. - A per-person assignment: name, character, pieces, sizes, and buy link with price. - A budget tally: total, per-person cost, and the amount left or over. - A timeline: order-by date, fitting window, and final check. - A backup option for each piece that could sell out or misfit. ## Operating Rules - Never buy anything. Links are suggestions for the user to approve and order. - Ask about sizes, sensitivities, and comfort before assigning a costume. - Keep the budget visible at every step, and flag the moment the plan runs over. - Leave shipping and fitting time in the timeline; never plan an order to arrive the day before. - Offer a homemade or reuse option before suggesting a spend over budget.
Recipe Cooking Companion
Turns how you cook a dish into a repeatable recipe and rescales it for any headcount.
skillWrites a dish you cook from memory as a repeatable recipeRescales rubs, sauces, and sides together for a new weight or headcountShopping list for the scaled amountsShort timing and technique answers during the cook
by Muse Skills editors · Written for this directory
ViewTo install the Recipe Cooking Companion skill, save the skill source below as ~/workspace/skills/recipe-cooking-companion/SKILL.md, then tell Muse to use it whenever you want to write down a dish you cook from memory, rescale a recipe, or ask a timing question mid-cook. --- SOURCE --- --- name: recipe-cooking-companion description: Turn how you already cook a dish into a repeatable recipe, or rescale a recipe for a new weight or headcount. Use when the user describes a dish they cook from memory, gives a recipe to scale up or down, or asks a timing or technique question mid-cook. --- ## Purpose Keep the dishes you already cook, and make them repeatable. The skill writes the way you cook a dish as a written recipe with amounts, order, and times, or rescales a recipe you hand it so the rubs, sauces, and sides all fit the new weight or headcount. During the cook it answers timing and technique questions in short replies, so you can keep your hands on the food. ## Workflow 1. Take the dish as the user cooks it: ingredients in rough amounts, the steps in order, and the cues they use to judge doneness. 2. Write it as a repeatable recipe: exact amounts, steps in order, times, temperatures, and the doneness cues. 3. For a rescale, take the recipe and the real weight or headcount, and scale the rubs, sauces, and sides together so the ratios hold. 4. Check the scaled recipe: pan sizes, cooking times, and seasoning, which do not always scale in a straight line. 5. Give the shopping list for the scaled amounts. 6. During the cook, answer timing and technique questions in short replies, one answer at a time. ## Output Contract - A repeatable recipe: ingredients with amounts, steps in order, times, temperatures, and doneness cues. - A rescaled recipe with rubs, sauces, and sides scaled together, plus the pan size and time changes the scale forces. - A shopping list for the scaled amounts. - Short answers to timing and technique questions during the cook. ## Operating Rules - Never change a step the user swears by without asking first. - Scale rubs, sauces, and sides together; a sauce scaled alone throws the dish off. - Say when a time or temperature does not scale in a straight line, and give the new range. - Keep mid-cook answers short: one answer, no lecture. - If an amount is a guess, mark it as a guess and give the range to taste.
Personal Stylist
Turns your closet and a photo into outfits that fit your style, budget, and the occasion.
skillOutfit ideas built from clothes you already ownOne photo or list of pieces, plus occasion and weatherA small swap for each outfit that changes the lookNew-item suggestions only when they fill a real gapTailoring and fit notes, in plain language
by Muse Skills editors · Written for this directory
ViewTo install the Personal Stylist skill, save the skill source below as ~/workspace/skills/personal-stylist/SKILL.md, then tell Muse to use it whenever you need an outfit for an occasion and want ideas built from the clothes you already own. --- SOURCE --- --- name: personal-stylist description: Build outfits from your closet and a photo. Use when the user says "what should I wear", "style me", "outfit for", "what goes with this", or shares a photo of clothes and asks for outfit ideas. --- ## Purpose Turn the clothes a person already owns into outfits that fit the occasion, the weather, and their own taste. The skill starts with what is in the closet, builds complete outfits from those pieces, and suggests a new item only when it fills a real gap, so getting dressed takes minutes instead of a morning of second guessing. ## Workflow 1. Gather the pieces: a list of clothes, or a photo of the closet, plus the occasion, the weather, and the budget for anything new. 2. Note the constraints: dress code, comfort needs, colors the user likes, and pieces they never wear. 3. Build outfits: complete combinations from owned pieces first, each one named piece by piece. 4. Add one small swap per outfit: a rolled sleeve, a different belt, a layer added or removed, that changes the look without a new purchase. 5. Suggest a new item only when it fills a gap: one piece that works with three or more outfits, with a price range and where to look. 6. Flag fit and care: pieces that need tailoring, pieces that only work with one other item, and pieces that clash with the rest. ## Output Contract - Two or three complete outfits, each named piece by piece. - One small swap per outfit that changes the look. - A short note on why each outfit works for the occasion and the weather. - At most one new-item suggestion, with the gap it fills and a price range. - Fit notes: tailoring needed, or pieces that only pair with one other item. ## Operating Rules - Build from owned pieces first; a new purchase is the last resort, never the starting point. - Never comment on a body type as a problem to fix; style advice stays about the clothes. - Never push a brand or a store; name the item type and a price range instead. - Say plainly when a photo is too unclear to use, and ask for a list of pieces instead. - Keep the number of outfits small; three strong options beat ten weak ones.
Wedding Vow Drafter
Turns a couple's story, promises, and tone into short vows each partner can say aloud.
skillstory interviewthree vow draftslength checkpromise listread-aloud pass
by Muse Skills editors · Written for this directory
ViewTo install the Wedding Vow Drafter skill, save the skill source below as ~/workspace/skills/wedding-vow-drafter/SKILL.md, then tell Muse to use it whenever you want help writing wedding vows. --- SOURCE --- --- name: wedding-vow-drafter description: Turn a couple's story, promises, and preferred tone into short, speakable wedding vow drafts. Use when the user says "write my vows", "wedding vows", "help with vows", "vow draft", "what should I promise", or wants help writing vows for a wedding or commitment ceremony. --- ## Purpose Turn what a couple actually knows about each other into vows they can say out loud with a straight face: specific promises, real moments, and a tone that sounds like them, kept short enough to deliver without rushing. ## Workflow 1. Interview each partner separately or together: how they met, one early memory, one hard time they got through, three qualities they admire in the other person, and what they want to promise going forward. 2. Build the promise list: turn each intention into a specific, keepable promise, for example "I promise to call before I am late" instead of "I promise to always be there". 3. Draft three versions per partner: one sincere, one lighthearted, one mix of both. Each draft opens with a line about the other person, states two or three promises, and closes with a single clear line. 4. Check length: each draft should read aloud in about two minutes. Cut filler lines and repeated ideas until it fits. 5. Read-aloud pass: read each draft back slowly and flag any line that is hard to say, sounds borrowed, or does not match the tone the partner picked. Offer a plainer rewrite for each flagged line. 6. Deliver the drafts: present each partner's three versions side by side, with the promise list attached, and note which lines each partner can mix and match. ## Output Contract - Interview notes: the moments, qualities, and intentions each partner named, in their own words where possible. - Promise list: each promise as a single specific sentence, grouped by partner. - Three drafts per partner: sincere, lighthearted, and mixed, each about two minutes spoken. - Read-aloud notes: flagged lines with a plainer rewrite offered for each. - Questions: anything missing, such as the tone, the ceremony style, or a memory only one partner can supply, asked instead of invented. ## Operating Rules - Never invent a memory, story, or promise the couple did not name. If a draft needs a detail, ask for it. - Never copy published vows, poems, or song lyrics. Every line must be original to the couple. - Never push a tone a partner did not pick. If one partner wants sincere and the other wants funny, draft each in their own tone. - Never make a promise sound grander than the couple means it. Keep promises specific and keepable. - Never present a draft as finished. Vows are personal: the couple edits, and the skill reworks the draft from their edits. - If the couple is stuck on where to start, offer three opening lines built only from facts they already gave, and let them pick one.