secret-santa-generator
Skill1 starsChanged 3 months agoMITView on GitHub
Generate Secret Santa assignment lists from participant names and optional exclusion pairs. Use when the user asks to organize a Secret Santa, assign recipients, resolve duplicate names, or validate exclusion constraints.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anger-translatorSkill
- cache-moneySkill
- codebase-memoirSkill
- codex-reviewSkill
- goalpostSkill
- grand-tourSkill
- identity-theftSkill
- relocate-sessionSkill
- right-stuffSkill
- rubicon-wordpress-version-labSkill
- second-lookSkill
- showdownSkill
- star-chartSkill
- work-evidence-researchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 21 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this skill when the user:
- Distinctive: line 52
Every person gives to exactly one other person.
- Distinctive: line 53
Every person receives from exactly one other person.
- Distinctive: line 54
No one is assigned to themselves.
- Distinctive: line 57
Never silently remove duplicate names.
- Distinctive: line 58
If fewer than two valid participants remain after cleanup, explain why and ask the user to revise.
- Distinctive: line 59
If exclusions make a valid assignment impossible, explain why and suggest removing one or more exclusion pairs.
- Distinctive: line 63
If a name appears more than once:
- Distinctive: line 64
Stop before generating assignments.
- Distinctive: line 66
Ask whether the duplicate is accidental or refers to different people.
- Distinctive: line 67
If it is intentional, ask for a designator so the names can be distinguished.
- Distinctive: line 77
Verify that no self-assignments or exclusion violations exist.
- Distinctive: line 78
If the assignment is invalid, retry with a different shuffle.
- Distinctive: line 79
If repeated retries fail, explain that the constraints are impossible and ask the user to revise the exclusions or participants.
- Distinctive: line 97
If the user wants it, also provide the results as:
- Distinctive: line 103
Before presenting results, confirm:
- Distinctive: line 104
Every participant appears exactly once as a giver
- Distinctive: line 105
Every participant appears exactly once as a recipient
- Distinctive: line 106
No one is assigned to themselves
- Distinctive: line 107
No exclusion rule is violated
- Distinctive: line 109
If validation fails, do not present the result as final.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Secret Santa Generator
Generate a randomized Secret Santa assignment list from participant names and optional exclusion rules.
When To Use
Use this skill when the user:
- Wants to organize or run a Secret Santa
- Needs a randomized giver-to-recipient assignment list
- Has exclusion pairs that must not be matched
- Wants duplicate names resolved before assignments are generated
- Wants results as plain text, CSV, or JSON
Inputs
Accept participant names in any mix of these formats:
- One name per line
- Comma-separated
- Semicolon-separated
- Pipe-separated
- Tab-separated
- Space-separated
Accept exclusions in any of these formats:
EXCLUDE: Mum & Dad, Alice & BobEXCLUDE:followed by one pair per line- Flexible spacing around delimiters
Within an exclusion pair, the names may be separated by:
&|+/andvs-,
Trim leading and trailing whitespace from every name.
Rules
- Every person gives to exactly one other person.
- Every person receives from exactly one other person.
- No one is assigned to themselves.
- Exclusions are symmetric. If
Acannot give toB, thenBcannot give toA. - Ignore blank entries.
- Never silently remove duplicate names.
- If fewer than two valid participants remain after cleanup, explain why and ask the user to revise.
- If exclusions make a valid assignment impossible, explain why and suggest removing one or more exclusion pairs.
Duplicate Names
If a name appears more than once:
- Stop before generating assignments.
- Tell the user which name is duplicated and how many times it appears.
- Ask whether the duplicate is accidental or refers to different people.
- If it is intentional, ask for a designator so the names can be distinguished.
- Confirm the resolved names before continuing.
Assignment Workflow
- Normalize and deduplicate the input.
- Parse exclusions.
- Validate that at least two participants remain.
- Randomly shuffle the participant list.
- Assign each person the next person in the shuffled list, wrapping around at the end.
- Verify that no self-assignments or exclusion violations exist.
- If the assignment is invalid, retry with a different shuffle.
- If repeated retries fail, explain that the constraints are impossible and ask the user to revise the exclusions or participants.
Output Format
Present results clearly and consistently.
Recommended plain-text format:
Alice -> CharlieBob -> DianaCharlie -> AliceDiana -> Bob
Then include a short summary:
- Participant count
- Pairing count
- Exclusion count
- Validation status
If the user wants it, also provide the results as:
- CSV
- JSON
Safety And Validation
Before presenting results, confirm:
- Every participant appears exactly once as a giver
- Every participant appears exactly once as a recipient
- No one is assigned to themselves
- No exclusion rule is violated
If validation fails, do not present the result as final.
Examples
User: "Set up a Secret Santa for Alice, Bob, Carol, and Dave. Bob and Carol are married, so don't pair them." Result: A valid randomized assignment that respects the exclusion rule.
User: "Run a Secret Santa for our 12-person team, list attached." Result: Parse the names, validate the set, and generate assignments.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

