Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Runs this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health.
$ npx skills add coleam00/skills --skill piv-validate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install coleam00/skills piv-validate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/piv-validate .claude/skills/piv-validate && rm -rf skills-srcUse ~/.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/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .claude/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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 install https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validateType 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.
$ npx skills add coleam00/skills --skill piv-validate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install coleam00/skills piv-validate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/piv-validate .agents/skills/piv-validate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .agents/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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.
$ npx skills add coleam00/skills --skill piv-validate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install coleam00/skills piv-validate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/piv-validate .cursor/skills/piv-validate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .cursor/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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 https://github.com/coleam00/skills.git --path .claude/skills/piv-validate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add coleam00/skills --skill piv-validate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install coleam00/skills piv-validate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/piv-validate .gemini/skills/piv-validate && rm -rf skills-srcUse ~/.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/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .gemini/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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.
$ gh skill install coleam00/skills piv-validateInstalls 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).
$ npx skills add coleam00/skills --skill piv-validate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/piv-validate .github/skills/piv-validate && rm -rf skills-srcUse ~/.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/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .github/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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.
$ npx skills add coleam00/skills --skill piv-validate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install coleam00/skills piv-validate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/piv-validate .opencode/skills/piv-validate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "piv-validate" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-validate into .opencode/skills/piv-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-validate", 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.
piv-validateRuns this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health.
Piv Validate is an agent skill from coleam00/skills. Runs this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health. Use before committing, before opening a PR, or after finishing a chunk of work to confirm zero regressions.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. The repository describes itself as: The agent skills I actually use to build software with coding agents. The PIV loop, planning, worktrees, and the meta-skills for building your own AI Layer. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 847be08. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Piv Validate loads about 781 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 383 words of instructions outside code blocks.
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.
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.
The full file from coleam00/skills at commit 847be08, republished under its MIT licence (© coleam00). 383 words, ~781 tokens.
.claude/skills/piv-validate/SKILL.md (or your agent's skills folder).Run every check this project has and report a single PASS/FAIL verdict.
⚠️ Make this yours first
This skill is a template. The command list below is a placeholder — replace it with the commands your project actually uses. That is the entire point of a custom checker: it is the one skill that cannot be generic, because it wraps your stack's CLIs.
Find your real commands in
package.jsonscripts,pyproject.toml,Makefile,justfile,docker-compose.yml, your CI workflow, or the README — then delete these and paste yours in.Two things to get right, because they are the usual reason a checker silently lies:
- Working directory. Many tools only discover their config from the current directory. If your config lives in
backend/pyproject.toml, the command iscd backend && uv run pytest, notuv run pytestfrom the repo root.- Cross-platform. Avoid POSIX-only idioms if anyone on the team is on Windows —
lsof,python3, and background-then-killare the common offenders.
Run the checks in order. Keep going after a failure so the report covers everything, and capture the output of any command that fails.
# REPLACE: your test command, run from the right directory
<your test command>Expected: all tests pass.
# REPLACE: e.g. mypy, tsc --noEmit, go vet
<your type-check command>Expected: no type errors.
# REPLACE: e.g. ruff check, biome check, eslint
<your lint command>Expected: clean.
A full-stack project has more than one of each. Add a section per surface — backend tests, backend types, backend lint, frontend tests, frontend types, frontend lint — so a single command covers the whole repo.
Only when the change touches routing, middleware, or startup; skip it when your test suite already exercises the app in-process.
# REPLACE: start your app, hit one endpoint, confirm the status code, stop it
<your run command>Prefer starting the server in a second shell over backgrounding and killing it from inside this skill — the background-and-kill idiom is not portable.
Report each check with a ✅ or ❌, then an overall verdict:
For every ❌, include the failing command and the relevant output. Do not fix anything here — this skill reports; fixing is a separate step.
© coleam00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/piv-validate of coleam00/skills.
Open the folder on GitHubat commit 847be08
Piv Validate 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Piv Validate this skillcoleam00/skills | 676 | — | ~781 | Automated safety check: Pass | MIT | |
| Go Pedantrychromedp/chromedp | 13k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| Trellis Checkanjiemo/SunnyBeach | 178 | 7 repos | ~666 | Automated safety check: Pass | Apache-2.0 | |
| WooCommerce Dev Cyclewoocommerce/woocommerce | 11k | 3 repos | ~431 | Automated safety check: Pass | Custom licence | |
| Adk Setupgoogle/adk-python | 22k | — | ~993 | Automated safety check: Notes | Apache-2.0 |
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
anjiemo/SunnyBeach
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks.
woocommerce/woocommerce
Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
blokadaorg/blokada
A skill your agent uses to validate risky dependency bumps end to end as a local or cloud-launched agent.
coleam00/skills
Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what…
coleam00/skills
Take a PRD and build a dark factory around it - a repository that takes work in as an issue and ships validated code out with nobody at the keyboard - one component at a time, into the user's actual…
coleam00/skills
Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals.
coleam00/skills
Audit any second brain, notes folder, or agent memory for facts that have quietly stopped being true, then fix the worst one so it stops recurring.
coleam00/skills
Build a personal signal engine from scratch - a system that reads every source someone cares about each day (changelogs and release notes, communities, feeds, videos, papers), makes a quick decision…
coleam00/skills
Create one or more git worktrees for parallel development, each on its own branch with gitignored config copied in, dependencies installed, and a health check, by fanning out a setup subagent per…
Categories
Runs this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health. Piv Validate is an agent skill from coleam00/skills. Runs this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health.
Piv Validate fits situations like: tasks that involve Linting and formatting.
Run `npx skills add coleam00/skills --skill piv-validate -a claude-code`. Or copy the skill folder (.claude/skills/piv-validate in coleam00/skills) into .claude/skills/piv-validate in your project. Claude Code loads it when a task matches its description.
Run `npx skills add coleam00/skills --skill piv-validate -a codex`. Or copy the skill folder (.claude/skills/piv-validate in coleam00/skills) into .agents/skills/piv-validate in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coleam00/skills --skill piv-validate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/piv-validate, .gemini/skills/piv-validate, .github/skills/piv-validate and .opencode/skills/piv-validate in your project.
Going by SKILL.md and its folder, Piv Validate needs the command-line tools its instructions call (uv). Our summary lists: Docker.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Piv Validate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 781 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Piv Validate: Go Pedantry (chromedp/chromedp, 13k stars), Kedro Babysit (kedro-org/kedro, 11k stars), Trellis Check (anjiemo/SunnyBeach, 178 stars) and WooCommerce Dev Cycle (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
coleam00 (a GitHub user) maintains it in coleam00/skills, which has 676 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.
Source: coleam00/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.