Claude Skills by paulnsorensen

github.com/paulnsorensen

18 skillsA× 180 installs14 views

Python AuthoringAWrite, edit, refactor, or review Python in easy-cheese with concise stdlib-first code, Python 3.12, wedge .pyz packaging, and repository test and validation conventions. Use for Python changes under src/, scripts/, .github/scripts/, or tests/, especially when the user asks for Pythonic, succinct, de-slopped, dataclass-based, CLI, validator, or bundled-helper code.developmentpythonrustVotes: 0GitHub stars: 18
Skill AuthoringACodify the discipline-section guidance, the CSO description rule, and the size-budget checklist that easy-cheese skills follow when authoring or revising a skill. Use when writing a new skill or SKILL.md, adding a discipline section, or reviewing an existing skill against easy-cheese's authoring conventions.developmentpythongoVotes: 0GitHub stars: 18
AffinageATriage a PR's review comments, CI failures, and merge conflicts through the /age lens. Use when the user asks to address PR feedback, fix CI, or resolve conflicts. Do not use for a diff without a PR. Use /age instead.developmentpythongitVotes: 0GitHub stars: 18
AgeAReview a diff, PR, branch, or path across twelve dimensions. Emit a severity-grouped findings report. Use when the user wants a code review. Trigger on "review this", "/age", "is this safe to merge", or "find bugs". Also trigger on "spot security issues", "check for slop", "review my PR", or "what's wrong with this code". Review every requested dimension. Review all twelve dimensions by default. Do not apply fixes. Route them to /cure. Do not harden tests; route that work to /press.developmenttypescriptpythonVotes: 0GitHub stars: 18
BriesearchAResearches cited evidence from documentation, current web sources, repositories, local code, and Git hosting. Use when the user asks to research, compare, investigate, verify facts, find guidance, assess maintenance, or gather evidence before implementation.developmentrustgitVotes: 0GitHub stars: 18
CheeseARoute an idea, path, pull request, issue, failure, question, or bare `/cheese` to the correct workflow skill. Use this skill for `/cheese`, routing requests, help requests, or opening messages without a named workflow skill.developmentrustgitVotes: 0GitHub stars: 18
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
CookAImplement an approved spec or focused task through stale-safe source edits. Use this skill when the user says "implement this", "cook this spec", or "fix this bug". Use it for `/cook .cheese/specs/<slug>.md`. Also use it when the user says "go" with clear acceptance criteria. Run it alone for an unambiguous task. Use `--prototype` when the user says "prototype this", "go prototype it", or "spike this out" and wants to refine the result round by round. A spec helps but is not required. Do not ...developmentpythonrustVotes: 0GitHub stars: 18
CultureAPrimarily the agent's internal-thinking skill — invoke it silently to model a problem, identify trade-offs, and decide what to do, BEFORE asking the user anything or dispatching another skill. Only treat this as a user-facing skill when the user has explicitly opted out of code writes — phrases like "no writes", "just rubber-duck this", "let's only talk", "/culture"; there it records the session's ideas, decisions, and info to the durable knowledge lane. Do NOT use for shaping a written spec ...developmentgogitVotes: 0GitHub stars: 18
CureAApply selected fixes from an /age report, findings list, or CI failure. Run the project gates and hand a clean result to /plate. Use when the user wants selected findings resolved. Do not use for review, test authoring, or direct publication.developmentpythongitVotes: 0GitHub stars: 18
Easy Cheese SetupARegister the durable `cheese-durable` Hallouminate corpus. Repair the durable corpus when its configuration changes. Register the repository tenant. Repair the repository tenant when its configuration changes. Use this skill when the user requests durable corpus setup or repair. Use it when the user requests repository tenant registration. Also use it when the user invokes /easy-cheese-setup. Use the wiki skills for general Hallouminate wiki work. Use scripts/install.sh to install the MCP ser...developmentpythonbashVotes: 0GitHub stars: 18
Hard CheeseAChecks whether an author can explain a code change before review. Use when the user requests `/hard-cheese`, `/cheese --hard`, or an understanding check. Use it before a pull request or through the `--hard` pipeline flag. Do not use it for reviews, test hardening, or fixes.developmentpythongitVotes: 0GitHub stars: 18
MeltAResolve Git merge, rebase, or cherry-pick conflicts through a structural merge cascade. Run mergiraf first, Git rerere second, and kdiff3 last. Use this skill when conflicts exist or Git shows an incomplete operation. Trigger phrases include "melt the conflicts", "resolve the rebase conflicts", and "fix the cherry-pick". Do not use this skill for Git operations without conflicts. Use it after `/cook` or `/cure` when a merge step blocks progress.developmentpythonrustVotes: 0GitHub stars: 18
MoldATurn a high-leverage design decision into a validated spec through grounded dialogue. Use it when a leverage trigger fires (auth, irreversible effects, concurrency, contracts, destructive ops, a new slice, a cross-slice dependency, an invariant gap) or when the user asks for a spec or design. Typical phrases include "let's design X", "shape this into a spec", "what should the API for Z look like", and "/mold". A feature ask with zero fired triggers is a `/cook` mini-spec, not a mold; route it...developmentpythongoVotes: 0GitHub stars: 18
PasteurizeADiagnose and fix a hard bug. Build a reliable reproduction, name the cause, add a regression test, and apply the minimum fix. Use when the user reports a bug, a failure, a flaky test, a performance regression, an error, or a wrong result whose cause is unknown. Use when the user pastes a symptom, a stack trace, or failing test output. Use for "why is X broken", "it stopped working", "it got slower", or "this looks wrong". Do not use for a review-only diff, for feature design, or for a fix who...developmentpythongoVotes: 0GitHub stars: 18
PlateATurn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits, pushes, pull request creation, and stack changes. GitHub inspection, reviews, comments, CI, issues, releases, and repository administration are outside this skill. Use the gh CLI d...developmentpythonshellVotes: 0GitHub stars: 18
PressARun the tests-only adversarial pass after `/cook`. Report each defect as a finding for a Cook correction. Use this skill when the user says "press the changes", "harden this", "press before /age", or "/press". Do not edit production code.developmentpythonVotes: 0GitHub stars: 18
UltracookARetired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.developmentVotes: 0GitHub stars: 18
WheypointAMark the current conversation as a durable handoff so a new agent can resume the work. Use when the user wants to preserve state for a later or parallel session. Triggers include "hand this off", "write a handoff", "drop a wheypoint", "checkpoint this", "compact the conversation", and "/wheypoint". Also use for "wrap up" or "I need to clear context" during a task. Do NOT use for phase handoffs from `/cook`, `/press`, `/age`, or `/cure`.developmentpythonbashVotes: 0GitHub stars: 18