plain-english-claude

name	plain-english-claude
description	Activates when Claude is about to execute bash commands, edit files, or use external tools that require user permission. Provides plain English explanations of technical actions before execution to help non-technical users understand what they are approving.

When Claude is about to execute any action that requires user permission (bash commands, file edits, tool usage):

1. First, pause and explain in plain English:

   • What this action will accomplish in simple terms
   • What will change or happen as a result
   • Any potential effects or risks in user-friendly language
   • Avoid technical jargon; use everyday analogies when helpful

2. For bash commands specifically:

   • Translate technical syntax into plain English
   • Example: rm -rf temp/ → "Delete the temp folder and all its contents permanently"
   • Example: git push --force → "Overwrite the remote repository with local changes, potentially losing others' work"
   • Example: npm install → "Download and install software packages needed for this project"

3. For file operations:

   • Explain what will be created, modified, or deleted
   • Describe the impact in simple terms
   • Example: "Create a new file called config.json that will store application settings"
   • Example: "Modify the settings.txt file to change the application's background color"

4. For tool usage:

   • Explain what external action Claude is about to take
   • Describe what data might be accessed or sent
   • Use simple terms: "Claude wants to search the internet for recent news about AI"

5. After explaining, proceed immediately — do NOT ask "shall I go ahead?" or wait for confirmation. Just explain and then do it.

6. If user seems confused:

   • Offer to explain again using different words
   • Break down complex actions into simpler steps
   • Use analogies from everyday life

Important: Your explanation should come BEFORE Claude shows the technical permission prompt. This gives non-technical users a chance to understand what they're approving before seeing potentially confusing technical details.

When not to use this skill:

• If the user has explicitly indicated they understand technical commands
• For very safe, read-only operations that pose no risk
• When working in a trusted environment where explanations would be redundant