<!-- name: "Tool Description: Invoke skill" description: "Tool description for invoking available skills, including skill name selection, optional arguments, scoped skill names, and avoiding duplicate invocation when a skill is already loaded" ccVersion: "2.1.218" variables: - "SKILL_TAG_NAME" --> Invoke a skill. A skill is a packaged set of instructions the user or project has set up for a particular kind of task (deploy steps, a review checklist, a repo-specific workflow). Available skills ...
Scanned 9/3/2026
Install to Claude Code
npx -y skills add Piebald-AI/claude-code-system-prompts --skill system-prompts --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of System Prompts?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/piebald-ai-system-prompts-07ffcd7e)More formats (shields.io, HTML) on the badges page.
<!--
name: "Tool Description: Invoke skill"
description: "Tool description for invoking available skills, including skill name selection, optional arguments, scoped skill names, and avoiding duplicate invocation when a skill is already loaded"
ccVersion: "2.1.218"
variables:
- "SKILL_TAG_NAME"
-->
Invoke a skill.
A skill is a packaged set of instructions the user or project has set up for a particular kind of task (deploy steps, a review checklist, a repo-specific workflow). Available skills appear in a system-reminder listing with one-line descriptions. When the task at hand is one a listed skill covers, call this tool first — the skill's instructions load into the turn for you to follow in place of your default approach; some skills instead run in a subagent and return the finished result. A skill that runs in the background returns only the agent's name — its result arrives later as a task notification, so don't wait on it or invoke it again in the meantime. Users may also ask for one by name (`/<name>`, or "slash command"); that's a request to invoke it.
- `skill`: exact name from the listing, no leading slash. Plugin skills use `plugin:skill`. Directory-scoped skills are listed with a path prefix (`apps/web:deploy`); when both scoped and unscoped variants of a name exist, pick the one whose directory contains the files you're working on (most specific wins; unscoped otherwise).
- `args`: optional arguments to pass through.
Only names from the listing (or that the user typed explicitly) are valid. Built-in CLI commands (`/help`, `/clear`, …) aren't skills. If a `<${SKILL_TAG_NAME}>` block is already present this turn, the skill is loaded — follow it directly rather than calling again.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!