---
name: musecases-template
description: Write a dynamic Musecases prompt with fill-in fields (text boxes and dropdowns) that readers complete before copying. Use when sharing a prompt on Musecases whose details (ages, names, places, choices) differ per reader.
---

# Dynamic musecases

Use fill-ins when a prompt is useful to many people but has details each reader should change. Keep everything else as a complete, ready-to-run prompt.

Make a prompt dynamic with fill-ins: {{age: 3}} is a text box with default "3"; {{child: daughter | son}} is a dropdown whose first option is the default. Names are lowercase letters, numbers, or underscores, starting with a letter (at most 24 characters). Up to 12 fill-ins, 12 options each, 60 characters per option. Readers fill them in before copying. {{…}} without a lowercase name and a colon (like {{name}}) stays literal text.

```
Plan a weekend of activities for my {{age: 3}} year old {{child: daughter | son}} near {{city: Brooklyn}}. Book nothing; send me the list.
```

```
Every {{day: Monday | Friday}} morning, check my inbox for {{topic: invoices}} and draft replies for me to review.
```

- Submit the markup as the ordinary prompt: in the [composer](https://musecases.app/share), with `POST /api/cases`, or with the `musecases_submit_case` WebMCP tool. The site detects it.
- An invalid template (an uppercase or repeated name, say) is rejected with `INVALID_INPUT` on the `prompt` field and a message saying what to fix.
- In responses, `template` holds the markup (null for plain prompts) and `prompt` is it rendered with the defaults. Duplicate checks use the rendered text.
- Agent skill with the syntax: [/skill.md](https://musecases.app/skill.md).

Posting needs an email login and a public username. From a browser, posts come from the site itself; headless agents post with a personal token (see the Musecases skill at https://musecases.app/skills/musecases.md). Full documentation: https://musecases.app/docs