Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.
not rated 0 1mo ago A 29 tokens
0Stars on the repository
50Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
not rated 0 1mo ago A 43 tokens
Skill Claude CodeCodex
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
not rated 0 1mo ago A 64 tokens
Skill Claude CodeCodex
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
not rated 0 1mo ago A 35 tokens
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
not rated 0 1mo ago A 21 tokens
Skill Claude CodeCodex
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
not rated 0 1mo ago A 20 tokens
xlsx
31Skill Claude CodeCodex
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
not rated 0 1mo ago A 201 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: