Agent skill

Scenarios

Prove kitcn fixture and scenario runtime the right way. An agent skill from udecode/kitcn.

Apache-2.0Auto-check passed

Install Scenarios

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install udecode/kitcn scenarios --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/scenarios .claude/skills/scenarios && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .claude/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install udecode/kitcn scenarios --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/scenarios .agents/skills/scenarios && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .agents/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install udecode/kitcn scenarios --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/scenarios .cursor/skills/scenarios && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .cursor/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/udecode/kitcn.git --path .agents/skills/scenarios

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install udecode/kitcn scenarios --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/scenarios .gemini/skills/scenarios && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .gemini/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install udecode/kitcn scenarios

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/scenarios .github/skills/scenarios && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .github/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add udecode/kitcn --skill scenarios -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install udecode/kitcn scenarios --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/udecode/kitcn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/scenarios .opencode/skills/scenarios && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "scenarios" agent skill from https://github.com/udecode/kitcn/tree/main/.agents/skills/scenarios into .opencode/skills/scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenarios", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: scenarios
GitHub stars: 450
Token cost: ~1.2k tokens
SKILL.md length: 478 words
Files: 1
Skills in repo: 33
Repo updated: Oct 1, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Prove kitcn fixture and scenario runtime the right way. An agent skill from udecode/kitcn.

Works in 4 steps: bun run scenario:prepare -- → bun run scenario:dev -- → Wait for ready logs. → …
Validating prepared scenario apps
SKILL.md covers Contract, Hard Rules, Canonical Commands and Proof Matrix, plus 2 more sections
Calls bun

What it does

Scenarios is an agent skill from udecode/kitcn. Prove kitcn fixture and scenario runtime the right way. Use when validating prepared scenario apps, auth smoke and browser lanes, or deciding whether a scenario key should use scenario:dev or scenario:check.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Convex + Better Auth + tRPC + Drizzle + TanStack Query + shadcn. The licence is Apache-2.0.

When your agent uses it

Validating prepared scenario apps
Auth smoke and browser lanes
Deciding whether a scenario key should use scenario:dev

Example prompts

“/scenarios”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

bun run scenario:prepare --
bun run scenario:dev --
Wait for ready logs.
Stop.

What it can do on your machine

Read from SKILL.md and the folder at commit c6010f5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scenarios loads about 1.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 478 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from udecode/kitcn at commit c6010f5, republished under its Apache-2.0 licence (© udecode). 478 words, ~1,210 tokens.

Download SKILL.mdSave it as .claude/skills/scenarios/SKILL.md (or your agent's skills folder).

name: scenarios
description: Prove kitcn fixture and scenario runtime the right way. Use when validating prepared scenario apps, auth smoke and browser lanes, or deciding whether a scenario key should use `scenario:dev` or `scenario:check`.
user-invocable: false

Scenarios

Use this skill for committed fixture checks and runtime proof of prepared scenarios.

Contract

Pick the proof path from the registered scenario key.
Use committed fixtures/* only as sources. The runnable app lives under tmp/scenarios/*.
Stop once the assigned proof path succeeds. Do not keep poking the app for sport.

Hard Rules

Never run committed fixtures/* in place.
Always prepare into tmp/scenarios/<name>/project.
fixtures:* owns committed snapshot sync/check.
scenario:* owns runnable temp apps.
Stop spawned dev processes once proof succeeds or fails.
If a temp app is stale after package or scaffold changes, rerun bun run scenario:prepare -- <name> once. If it still fails, debug the cause. Do not loop forever.
If a scenario has no real browser auth surface, do not invent one.
For bootstrap-heavy Convex lanes, bun run scenario:check -- <name> is the proof. Do not replace it with ad-hoc scenario:dev.

Canonical Commands

bash

bun run fixtures:sync
bun run fixtures:check
bun run scenario:prepare -- <name>
bun run scenario:dev -- <name>
bun run scenario:check -- <name>
bun run scenario:test -- <name>
bun run test:runtime
bun run test:auth -- <name|url>
bun run test:e2e -- <name|url>

test:auth and test:e2e assume the scenario is already running. scenario:test wraps the proof matrix below. test:runtime runs scenario:test -- all and is the default non-browser runtime gate. test:e2e is a separate auth browser lane and should be run only when auth surfaces changed.

Proof Matrix

Plain runtime proof

Use this path for:

next
vite
create-convex-bare
create-convex-nextjs-shadcn
create-convex-react-vite-shadcn

Run:

bun run scenario:prepare -- <name>
bun run scenario:dev -- <name>
Wait for ready logs.
Stop.

Or:

bun run scenario:test -- <name>

Auth demo proof

Use this path for:

next-auth
start-auth

Run:

bun run scenario:prepare -- <next-auth|start-auth>
bun run scenario:dev -- <next-auth|start-auth>
bun run test:auth -- <next-auth|start-auth>
Stop.

Or:

bun run scenario:test -- <next-auth|start-auth>

Why:

scenario:test -- <next-auth|start-auth> proves runtime + auth smoke only.
Browser auth proof belongs to the explicit test:e2e lane:
1. bun run scenario:prepare -- <next-auth|start-auth>
2. bun run scenario:dev -- <next-auth|start-auth>
3. bun run test:e2e -- <next-auth|start-auth>

Show full SKILL.md (190 more words)Show less

Auth backend proof without browser auth

Use this path for:

vite-auth

Run:

bun run scenario:prepare -- vite-auth
bun run scenario:dev -- vite-auth
Stop.

Or:

bun run scenario:test -- vite-auth

Why:

There is no /auth page or equivalent browser auth surface today.
Do not fake test:e2e.
Do not add test:auth here unless the registry grows a dedicated auth proof lane.

Bootstrap-heavy Convex proof

Use this path for:

convex-next-auth-bootstrap
convex-vite-auth-bootstrap
convex-next-all
create-convex-nextjs-shadcn-auth

Run:

bun run scenario:check -- <name>
Stop.

Or:

bun run scenario:test -- <name>

Why:

Fresh kitcn lanes already bootstrap during scenario:prepare through kitcn init -t <next|vite> --yes, then finish the bootstrap-heavy proof with in-place kitcn init --yes after plugin setup.
The raw Convex auth adoption lane still owns convex init plus kitcn add auth --preset convex --yes.
Raw Convex auth adoption is not a next-auth browser demo. Do not invent /auth.

Re-prepare Rule

Re-run scenario:prepare once when:

package or scaffold source changed
the temp app predates that change
the temp app is missing expected local env or generated files

Otherwise, reuse the prepared app.

Examples

`next-auth` or `start-auth`

bash

bun run scenario:prepare -- next-auth
bun run scenario:dev -- next-auth
bun run test:auth -- next-auth

Short path:

bash

bun run scenario:test -- next-auth

Browser lane:

bash

bun run scenario:prepare -- next-auth
bun run scenario:dev -- next-auth
bun run test:e2e -- next-auth

`vite-auth`

bash

bun run scenario:prepare -- vite-auth
bun run scenario:dev -- vite-auth

Short path:

bash

bun run scenario:test -- vite-auth

`convex-next-all`

bash

bun run scenario:check -- convex-next-all

Short path:

bash

bun run scenario:test -- convex-next-all

Files

Just SKILL.md in .agents/skills/scenarios of udecode/kitcn.

Open the folder on GitHubat commit c6010f5

Compare with similar skills

Scenarios next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scenarios compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Scenarios this skilludecode/kitcn	450	—	~1.2k	Automated safety check: Pass	Apache-2.0	7 days ago
Scenarioscenario-labs/skills	913	1 repos	~6.2k	Automated safety check: Pass	MIT	yesterday
Test Scenariosphuryn/pm-skills	27k	—	~866	Automated safety check: Pass	MIT	23 days ago
Right To Erasurethedaviddias/Front-End-Checklist	74k	—	~512	Automated safety check: Pass	MIT	2 days ago
OpenLogi Device Fixture ContributionAprilNEA/OpenLogi	23k	—	~1.2k	Automated safety check: Pass	Apache-2.0	4 days ago
Scenario War Roomalirezarezvani/claude-skills	28k	1 repos	~2k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Scenario
scenario-labs/skills
A skill your agent uses when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets.
913 GitHub starsUsed in 1 repo~6.2k tokens
Game DevelopmentAuto-check passed
Test Scenarios
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
27k GitHub stars~866 tokensUpdated 23 days ago
Testing & QAAuto-check passed
Right To Erasure
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
74k GitHub stars~512 tokensUpdated 2 days ago
Legal & ComplianceAuto-check passed
OpenLogi Device Fixture Contribution
AprilNEA/OpenLogi
Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.
23k GitHub stars~1.2k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Scenario War Room
alirezarezvani/claude-skills
Cross-functional what-if modeling for cascading multi-variable scenarios.
28k GitHub starsUsed in 1 repo~2k tokens
Testing & QAAuto-check passed
ClawHub Rights Correspondence
openclaw/clawhub
Drafts, previews, sends and records email for an existing ClawHub content rights case through the admin CLI, with a dry run and your sign-off before anything goes out.
9.5k GitHub stars~984 tokensUpdated today
Legal & ComplianceAuto-check passed

Questions about Scenarios

What does Scenarios do?

Prove kitcn fixture and scenario runtime the right way. An agent skill from udecode/kitcn. Scenarios is an agent skill from udecode/kitcn. Prove kitcn fixture and scenario runtime the right way.

When should I use Scenarios?

Scenarios fits situations like: validating prepared scenario apps; auth smoke and browser lanes; deciding whether a scenario key should use scenario:dev.

How do I install Scenarios in Claude Code?

Run `npx skills add udecode/kitcn --skill scenarios -a claude-code`. Or copy the skill folder (.agents/skills/scenarios in udecode/kitcn) into .claude/skills/scenarios in your project. Claude Code loads it when a task matches its description.

How do I install Scenarios in Codex?

Run `npx skills add udecode/kitcn --skill scenarios -a codex`. Or copy the skill folder (.agents/skills/scenarios in udecode/kitcn) into .agents/skills/scenarios in your project. Codex loads it when a task matches its description.

Can I use Scenarios in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add udecode/kitcn --skill scenarios -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenarios, .gemini/skills/scenarios, .github/skills/scenarios and .opencode/skills/scenarios in your project.

What does Scenarios need to run?

Going by SKILL.md and its folder, Scenarios needs the command-line tools its instructions call (bun).

Does Scenarios access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Scenarios safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scenarios use?

Scenarios is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scenarios use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scenarios?

Skills that share tags, products or a category with Scenarios: Scenario (scenario-labs/skills, 913 stars), Test Scenarios (phuryn/pm-skills, 27k stars), Right To Erasure (thedaviddias/Front-End-Checklist, 74k stars) and OpenLogi Device Fixture Contribution (AprilNEA/OpenLogi, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenarios?

udecode (a GitHub organization) maintains it in udecode/kitcn, which has 450 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 1, 2026.

Source: udecode/kitcn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Scenarios

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Scenarios

Contract

Hard Rules

Canonical Commands

Proof Matrix

Plain runtime proof

Auth demo proof

Auth backend proof without browser auth

Bootstrap-heavy Convex proof

Re-prepare Rule

Examples

next-auth or start-auth

vite-auth

convex-next-all

Files

Compare with similar skills

Similar skills

More from udecode/kitcn

Questions about Scenarios

`next-auth` or `start-auth`

`vite-auth`

`convex-next-all`