Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Explain

ASecurity

Use when technical agent output needs beginner-friendly translation without losing exact details.

4 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgo

Works with

terminal

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add mverab/slashstack-skills --skill explain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Explain?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Explain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mverab-explain/badge)](https://www.skillsdirectory.com/skills/mverab-explain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: explain
description: Use when technical agent output needs beginner-friendly translation without losing exact details.
---

# Explain

## Purpose

Translate technical agent output into beginner-friendly language while preserving
the exact file paths, commands, errors, and decisions the user needs.

## When to Use

Use when output from an agent, terminal, test run, error message, pull request,
or implementation plan is too technical for the user to act on confidently.

## Workflow

1. Identify the source: name the command, file, diff, error, or agent message
   being explained.
2. Preserve exact details: keep file paths, commands, package names, versions,
   error text, and config keys unchanged.
3. Translate jargon: explain unfamiliar terms in beginner language.
4. Separate facts from interpretation: clearly label what the output proves,
   what it suggests, and what remains unknown.
5. Explain impact: state whether the issue blocks progress, is safe to ignore,
   or needs a specific action.
6. Give the next safe action: provide one concrete prompt or command the user
   can run next.
7. Modo Aprendiz: for the MOST confusing concept in the output, include three
   sub-fields in beginner-friendly Spanish:
   - Qué significa: what the concept means in plain language.
   - Por qué importa: why it matters for the project.
   - Qué hacer ahora: one concrete action to take now.

## Output

A beginner explanation containing:
- Plain version: the short explanation in non-technical language
- Exact details: file paths, commands, or error lines that must not be changed
- Why it matters: the practical impact
- Modo Aprendiz: the most confusing concept with Qué significa, Por qué importa, and Qué hacer ahora
- Next safe step: one prompt or command to run next

Attribution

mverabmverab
View sourceSee grades on GitHubMore from mverab →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →