Skip to content
cccskills
FreePublished on GitHubEnglish overview

wait-what

Ask the agent to explain its last message again with some context. The revised explanation uses ASD-STE100, a simplified technical English standard, and the vocabulary defined in the project's glossary.

OriginalShow the original description

Stop. That last message did not land: re-pitch it.

mattpocock/skills
AI rating80/ 100See how to install

Good for

  • Requesting a clearer explanation of the last message
  • Adding context when the discussion becomes hard to follow
  • Explaining with the project's agreed terminology

Overview

What it does

wait-what asks the agent to explain its previous message again when that explanation was hard to follow. It adds a little background and uses ASD-STE100 Simplified Technical English, a standard for simplified technical English. It also uses the shared project vocabulary defined in GLOSSARY.md to explain the conversation again.

When it helps

Use it when you have lost track of where the discussion has reached, or when the agent's last explanation did not make sense to you. It also helps when you want an explanation that follows the terminology used in your project. The purpose is to receive the same content again with added context and consistent terms.

Example requests

  • “I did not understand your last explanation. Please explain it again with a little more background.”
  • “Explain the current discussion using the terms in GLOSSARY.md and ASD-STE100 Simplified Technical English.”

Notes

The explanation uses the simplified technical English specified in the source. Its glossary is GLOSSARY.md. If the repository contains multiple glossaries, it follows GLOSSARY-MAP.md to select the appropriate one.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt explicitly asks for the previous explanation again, with context, specified English, and glossary terminology.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
BPartly lackingIt names the standard and glossary but provides no explanation structure or example output.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt only requests rewriting and glossary reference, with no instructions to transmit data or modify files.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt references GLOSSARY.md, related files, and an English standard but gives no guidance when they are unavailable.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (2)

  • SKILL.md396 B
  • agents/openai.yaml158 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Wait, I don't understand where you've got to here. Re-pitch that: give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from GLOSSARY.md (follow GLOSSARY-MAP.md to the right one if the repo has more than one).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ask-matt

FreeSummaryAI rating 90

Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.

  • Choosing a workflow from idea to implementation
  • Finding the right starting point for bug investigation
  • Planning a build that spans multiple sessions
mattpocock/skills296.5KUpdated Oct 13, 2026

chief-of-staff

FreeSummaryAI rating 60

Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.

  • Coordinating agents around a long-term goal
  • Continuing user dialogue during background work
  • Improving shared rules and working conditions
mattpocock/skills296.5KUpdated Oct 13, 2026

claude-handoff

FreeSummaryAI rating 90

Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.

  • Continue ongoing work with a fresh agent
  • Hand off work with a specific next focus
  • Organize document references for the next session
mattpocock/skills296.5KUpdated Oct 13, 2026

code-review

FreeSummaryAI rating 90

Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.

  • Reviewing changes on a branch or pull request
  • Checking changes since a chosen commit or tag
  • Checking compliance with documented coding standards
mattpocock/skills296.5KUpdated Oct 13, 2026

codebase-design

FreeSummaryAI rating 90

Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.

  • Simplifying a module's interface
  • Bringing scattered complexity into one module
  • Choosing where implementations can be swapped
mattpocock/skills296.5KUpdated Oct 13, 2026

diagnosing-bugs

FreeSummaryAI rating 80

Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.

  • Investigating an error that is hard to reproduce
  • Finding the cause of a performance slowdown
  • Testing an intermittent failure repeatedly
mattpocock/skills296.5KUpdated Oct 13, 2026

See all skills by mattpocock

Report a problem with this skill