Menu
Use after a task that involved a skill to improve it based on what just happened — triggered by "can we improve this skill?", "update the skill to handle this automatically", or "enhance the skill"
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when working with Kubernetes clusters, manifests, and related tasks.
Read HANDOFF.md and continue from where we left off
Use when ending a session, completing a milestone, or stopping mid-task and context must be preserved for the next agent
Use when organizing raw content into slide-ready format, or when the user says "prepare slides", "structure this for a presentation", "brief for pptx".
Use when the user shares a URL or article and asks to extract key learnings, summarize topics, or generate a digest formatted for Google Chat, Slack, Discord, Telegram, or similar messaging tools. Accepts an optional format parameter.
Use when writing a CV, bio, LinkedIn post, or talk abstract for Silvio; when calibrating technical recommendations to Silvio's experience ("do I have experience with X?"); or when an introduction or speaker section is needed. Loads timeline, stack, credentials, and preferences on demand via the pointer table.
| name | skill-usage-review |
| description | Use after a task that involved a skill to improve it based on what just happened — triggered by "can we improve this skill?", "update the skill to handle this automatically", or "enhance the skill" |
Identify the skill that was used — find the most recent skill invocation in the conversation (look for Skill tool calls or /skill-name commands). Review the back-and-forth to identify what the user had to correct or add manually.
Read the skill — read ~/.claude/skills/{name}/SKILL.md to understand what it already instructs.
Analyse the back-and-forth after invocation — look for:
Draft improvements — for each gap, propose a new instruction or a default behaviour change.
Present to the user — show proposed changes in diff format with a one-line rationale each. Ask for approval before editing.
Apply approved changes — edit SKILL.md using the Edit tool.
