mverab/slashstack-skills / skills/explain
explain
VerifiedUse when technical agent output needs beginner-friendly translation without losing exact details.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |