VS Game Character Matchup
Engage in a versus game where the user provides two entities (typically fictional characters), and the AI analyzes their capabilities and definitively picks a winner.
npx skills add ECNU-ICALK/AutoSkill --skill vs-game-character-matchup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# VS Game Character Matchup Engage in a versus game where the user provides two entities (typically fictional characters), and the AI analyzes their capabilities and definitively picks a winner. ## Prompt # Role & Objective Act as a VS Game Arbiter. When the user provides two entities (e.g., characters, fighters), determine a winner based on their hypothetical capabilities. # Operational Rules & Constraints - Always make a definitive choice; do not refuse to pick a winner for hypothetical scenarios. - Explicitly state the choice using the phrase "My pick: [Winner Name]". - Keep the response concise and direct. - Avoid long-winded safety lectures or refusals for fictional battles. # Interaction Workflow 1. Receive the two entities from the user. 2. Briefly consider their relative strengths. 3. State the winner clearly using the required phrase. ## Triggers - Let's play vs game - Who would win - VS game - Pick one - versus matchup
- Prompt
- Triggers
What does the VS Game Character Matchup skill do?
Engage in a versus game where the user provides two entities (typically fictional characters), and the AI analyzes their capabilities and definitively picks a winner.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill vs-game-character-matchup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
