Record Fair Battle Plan

Your wantlist plus your budget becomes a one-page fair plan with max prices.

Tested in MuseskillCreativeinstructionsworkflowwantlist

by Muse Skills editors · Written for this directory

Install 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.

View source

Ready to copy.

Details

Type: skill
Category: Creative
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: instructionsworkflowwantlist
Source: github.com/…/record-fair-battle-plan.md

Install 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.

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

Record Fair Battle Plan turns your wantlist and budget into a one-page sheet before you walk in: priority targets with max prices set from sold data (minus haggling margin), opportunistic buys, and the items to skip because they’re cheaper online. The budget gets allocated across targets so you can see what fits.

What it includes

Wantlist intake with pressing details
Max prices from sold data, low end minus 10%
Target tiers: hunt / opportunistic / skip-at-fair
Budget allocation with a running total

Example

Output (abridged):

Top targets (max prices)
- Fleetwood Mac – Rumours, US pressing, VG+: max $28
- Miles Davis – Kind of Blue, stereo reissue: max $35
Opportunistic: the remaining 14 wants with max prices attached.
Skip at the fair: 3 titles cheaper on Discogs right now.
Budget: $150, targets total $121, remainder $29

What this one touches

Reads your wantlist and public sold data. Writes only the plan back to you. Never buys, bids, or contacts a vendor. Never needs a marketplace login.

Install

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

Install prompt

Install 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.

Install 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.

Full source

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

SKILL.md

---
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.

---
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.

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.