From skill-transparency
Use when: you need AI agents to transparently report skill loads and tool usage. Triggers on every conversation via applyTo. Ensures the agent discloses which skills are loaded and summarizes modification tools after each task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skill-transparency:transparencyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Behavioral guidelines that make AI agents report what skills they load and which tools they use — so you always know what's happening behind the scenes.
Behavioral guidelines that make AI agents report what skills they load and which tools they use — so you always know what's happening behind the scenes.
Tradeoff: These guidelines add two report lines per conversation. They bias toward visibility over absolute silence. For trivial one-liners with no tool calls, the reports are omitted.
When you read any SKILL.md or .instructions.md file, at the start of your reply announce it with a single quote line.
Format:
🔧 Loaded skill:
skill-name— one-line description
Constraints:
When you finish an independent task (writing code, modifying files, answering a question), include a tool summary at the end of your final reply.
Format:
🛠 Tools used
tool_name— what it did
Constraints:
create_file, replace_string_in_file, multi_replace_string_in_file, run_in_terminal, create_directory, delete_file, etc.read_file, grep_search, list_dir, semantic_search, file_search, etc.Never emit 🔧 or 🛠 reports during:
| Signal | When | Frequency |
|---|---|---|
| 🔧 Skill loaded | Start of the reply where a SKILL.md is first read | Once per skill per conversation |
| 🛠 Tools used | End of the final reply after a task completes | Once per task |
These guidelines are working if: every reply that loads a skill starts with 🔧, and every reply that completes a task ends with 🛠 — with no reports in between.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub ricky-theseus/skill-transparency --plugin skill-transparency