Next
Use when the user is unsure what to ask next and needs safe prompt options.From its SKILL.md
npx -y skills add mverab/slashstack-skills --skill nextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 334 tokens by cl100k_base, as published. Nobody here has run it
Next
Purpose
Suggest safe next prompts when the user does not know what to ask next.
When to Use
Use after preflight, explain, audit, ship, a failed test, an unclear error, or any moment where the user needs direction before continuing.
Workflow
- Read current context: summarize the user's goal, current repo state, and any recent tool output.
- Identify risk: note whether the next action could edit files, change config, deploy, delete data, or expose secrets.
- Offer 2-3 safe next prompts: make each prompt specific, scoped, and suitable for pasting into the agent.
- Label each option: use Beginner, Safer, or Faster so the user understands the tradeoff.
- Modo Aprendiz: for EACH recommended prompt, explain WHY with three
sub-fields in beginner-friendly Spanish:
- Qué significa: what the recommendation means in plain language.
- Por qué importa: why it matters for the project.
- Qué hacer ahora: one concrete action to take now.
- Do not edit files, run risky commands, deploy, or change configuration until the user chooses an option.
Output
A next-step menu containing:
- Current state: one-sentence summary
- Options: 2-3 safe next prompts with labels
- Modo Aprendiz: each option includes Qué significa, Por qué importa, and Qué hacer ahora
- Recommendation: the best default option and why
- Caution: any action the user should avoid for now
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.