agentsclimarketplace

Grill me

Skill humantypo/memtoad/skills/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Reads project diary first to surface relevant constraints. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".From its SKILL.md

Install
npx -y skills add humantypo/memtoad --skill grill-me

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 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

2.1 KB, as published. Nobody here has run it

Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.

Phase 0: Load project context

Before asking any questions, read these three files in order:

  1. diary/architectural_decisions.md
  2. diary/lessons_learned.md
  3. diary/session_context.md

After reading, output 1–2 sentences naming any constraints, decisions, or patterns from the diary that are directly relevant to the stated task. This lets the user correct misreadings before the interrogation begins. If nothing in the diary bears on the task, skip this acknowledgment and proceed silently.

How to ask questions

Use the AskUserQuestion tool for every question you ask. Never pose questions as plain text in your response — always use the multiple-choice popup so the user can quickly select an answer or type a custom one.

Ask one question at a time. Wait for the user's answer before moving to the next question. This keeps the conversation focused and prevents overwhelm.

For each question, provide 2–4 concrete multiple-choice options representing the most likely answers or directions. Think about what the user would realistically choose — generic options like "Yes" / "No" aren't helpful unless the question is genuinely binary. The user always has the "Other" field available to write something custom.

Flow

  1. After receiving an answer, briefly acknowledge the decision (1–2 sentences max), then immediately ask the next question via AskUserQuestion.
  2. If a question can be answered by exploring the codebase or files, explore them yourself instead of asking the user.
  3. Continue until all branches of the design tree are resolved.
  4. When finished, provide a concise summary of all decisions made.

Keep looking

Skills are one crate of 608,666. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.