Use when asked to work through, apply, resolve or review a template update pull request (the weekly `copier/update` branch opened by the copier-update workflow), after running `copier update --trust` by hand, or when a template update looks like it leaves no room for something this project needs.
Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, sizing a change before coding, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, sizes the change to one PR, links epic children as native sub-issues, and applies CONTRIBUTING.md before anything is posted.
Use when adding a domain configuration field, env var, Dockerfile extension, mcpb install-screen entry, or release-manifest stamp: the sentinel-based config and customization contract.
Use when writing or changing an MCP tool that can fail, refuse, find nothing or hit a conflict: choosing between returning a result and raising ToolError, writing a tool's error text, choosing log levels for tool outcomes, or when a tool call logs ERROR or a traceback for something that is not a server fault.
Use before adding or changing any logging call in src/: log levels, exception handling, the event_name key=value message grammar tests/test_logging_standard.py enforces, and what pvl-core's root-logger setup (standard-library logging rendered as Rich or JSON) does with a call that follows it or does not.
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
Use when a change depends on how something outside this repository actually behaves — a markdown dialect, a file format, git, a protocol, a vendor API — and docs/design/reference/ has no current reference for it, or the one it has is past its review date. Researches from primary sources and writes a dated, versioned, source-marked reference so the next agent reads instead of re-deriving. Works with any coding agent; parallel research is optional.
Use when work spans more than one pull request or epic, when the order of work is not yet decided, or when charting, refining or revisiting the roadmap index, epics and release package milestones. Use before implementation planning for work not yet refined into one ready feature.
Use before opening a pull request, marking one ready for review, or pushing further commits to a branch with an open pull request — or when asked to review a diff or a PR. Reviews the cumulative diff against the project's written commitments and reports evidence-grounded findings; works with any coding agent and needs no hosted model workflow.
Use when adding, renaming, or documenting an MCP tool: the registration checklist, the get_server_info tool, tool icons, and the public import-surface guard.
Use before adding, moving or substantially changing a page in docs/ or README.md, or a DOMAIN block in a template docs page: decides whether the knowledge belongs to this project or to the template, which existing page or designated place takes it, and what the change must link to.
Use when writing or changing a tool, parameter, resource or prompt description, a tool title or annotation, or a server-instructions snippet, and when reviewing such text: it decides which sentences the model can act on and where every other fact goes instead.
Use when adding a domain configuration field, env var, Dockerfile extension, mcpb install-screen entry, or release-manifest stamp: the sentinel-based config and customization contract.
Use before adding or changing any logging call in src/: log levels, exception handling, the event_name key=value message grammar tests/test_logging_standard.py enforces, and what pvl-core's root-logger setup (standard-library logging rendered as Rich or JSON) does with a call that follows it or does not.
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
Use when adding, renaming, or documenting an MCP tool: the registration checklist, the get_server_info tool, tool icons, and the public import-surface guard.
Use when adding a domain configuration field, env var, Dockerfile extension, mcpb install-screen entry, or release-manifest stamp: the sentinel-based config and customization contract.
Use before adding or changing any logging call in src/: log levels, exception handling, the event_name key=value message grammar tests/test_logging_standard.py enforces, and what pvl-core's root-logger setup (standard-library logging rendered as Rich or JSON) does with a call that follows it or does not.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.