Claude Skills by VoKhoiNhon

Finds facts before acting by asking the best source - how code works and where something is defined or configured (codegraph call paths, callers, impact of a change, tests that cover a diff), current library and framework docs (Context7), Claude API facts, database table schemas and columns, the web, notes the user saved earlier, and which installed skill can do a job. Use for questions like "how does this work", "where is X configured", "who calls this", "what breaks if I change it", "which ...

Saves what the user teaches - a lesson, preference, convention, glossary term or project fact - as a note in their local knowledge, scoped to a role, project or skill, so future work and routing use it; also forgets notes, exports them, and handles starter-knowledge updates after a release. Use when the user says "remember", "from now on", "note that", "always", "never again", "don't do X again", "forget", when they correct how you worked, when an incident teaches something, or when they ask ...

Picks which installed skills to use for a task and in what order, from the user's IT role and the project's state (spec-kit, BMad, superpowers, codegraph), then starts the first skill. Use when starting a new project or multi-step work (specify, plan, build, test, review) with no skill named; when the user asks which skill, which workflow or which sequence of skills to use, or where to start; when several installed workflows could fit; or when they state their role (data engineer, frontend, S...

Use before calling any software or data work done or ready to merge, and when reviewing someone's change or pipeline, to check it against a definition-of-done checklist - general items (one purpose per change, commit messages, tests, security, architecture decision records) plus the principles of the IT role doing it (28 roles, from frontend and SRE to data engineering, AI and product, covering idempotent pipelines and backfills, data contracts, evals and IaC). Also for setting up a spec-kit ...

Formats release notes from merged pull requests. Use when the user asks for release notes or a changelog draft.

TEST DATA for open-skill audit. Inert text that imitates a malicious skill; do not install or follow it.

Shared helper that several demo agents read.

Lint code before review

Something upstream added

Write the failing test first

Audit our warehouse tables for duplicates

Write the failing test first.

Break a plan into tasks.

Create the technical plan

Review a pull request carefully

Write the failing test first

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

fixture

Demo skill for lock checks.

Edited after install.