davila7

Use for the 5 Whys, or when the user wants the root cause of a failure: "why did this happen?", "this keeps breaking", "write the postmortem", "find the real cause". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off…

Use for a pre-mortem, or before committing to a plan, launch or migration: "what could go wrong?", "stress test this plan", "how might this fail?", "risks before we ship". Assumes failure, lists causes, ranks them and sets mitigations. Skip for explaining a…

Use when the user describes a problem, decision or stuck situation but names no method: "how should I approach this?", "help me think this through", "we can't decide", "where do I start?". Picks the best-fit thinking method and runs it. Skip for plain…

Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open…

Maximum-efficiency dev mode: terse zero-fluff prose + YAGNI/ladder-first code. Use when user says "chisle mode", "activate chisle", "chislify", "be efficient", "be minimal", "no fluff", "yagni", or invokes /chisle. Deactivate: "stop chisle" / "normal mode".

Find open US healthcare jobs (nursing, CNA, allied health, therapy, imaging, pharmacy, physicians and more) and the hourly pay employers post, using CareJobs.Now's free MCP server or its public JSON endpoints. Use when someone asks for healthcare or nursing…

You MUST use this whenever something is broken, before proposing or making any fix, including quick fixes and when the user is in a hurry: a bug, a failing or red test, a build or CI failure, a crash, a performance problem, unexpected behavior. Finds the root…

You MUST use this when asked to review code: a pull request, a branch, a commit, staged or uncommitted changes, or "check this before I merge". Scopes the review to the diff, reads the surrounding code, hunts for real bugs (correctness, security, data loss,…

Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".

Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.

Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.

Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.

Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.

Generate a conventional commit message for the current staged git changes. Use when the user wants to commit, asks for a commit message, or asks what to write for a commit.

Builds an interactive HTML dashboard visualizing the Agent Skills ecosystem by fetching live data from github.com/agentskills/agentskills. Use this skill whenever the user wants to explore, research, or visualize Skills architecture, the SKILL.md spec,…