agentsclimarketplace
Sign in

Pitch explainer

Skill MaybeMonad/skills/skills/unknown-reduction/pitch-explainer

Post-implementation pitch and explainer workflow for packaging a prototype, spec, implementation notes, verification evidence, and resolved unknowns into a reviewer-ready document. Use when the user asks for a Slack-ready summary, buy-in doc, explainer, launch note, approval packet, or wants reviewers to see the context, demo, decisions, tradeoffs, and remaining risks.From its SKILL.md

Install
npx -y skills add MaybeMonad/skills --skill pitch-explainer

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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.7 KB, 293 tokens by cl100k_base, as published. Nobody here has run it

Pitch Explainer

Use this skill to accelerate reviewer understanding and approval. The output should answer the unknowns reviewers are likely to have before they need to ask.

Workflow

  1. Gather source material:
    • Prototype, spec, plan, implementation notes, diff summary, screenshots, demo GIF/video, commands run, tests, runtime checks, and unresolved risks.
  2. Identify the audience:
    • Product, design, engineering, security, data, leadership, or a mixed review group.
  3. Lead with the demo or visible outcome when one exists.
  4. Explain the problem and why the chosen approach is appropriate.
  5. Include alternatives rejected and why.
  6. Show which unknowns were resolved and which remain.
  7. Include verification evidence and reviewer asks.

Output Shape

Use this structure:

  1. Demo or outcome.
  2. Problem.
  3. What changed.
  4. Decisions and tradeoffs.
  5. Unknowns resolved.
  6. Verification evidence.
  7. Remaining risk.
  8. Reviewer asks.

Rules

  • Write for approval, not for archival completeness.
  • Lead with the most concrete artifact: demo, screenshot, prototype, or user flow.
  • Do not hide residual risk. State it with its mitigation or follow-up.
  • Do not paste long diffs. Explain behavior and link or reference files.
  • Keep stakeholder text crisp enough to drop into Slack or a review doc.

What ships with it: 1 file

233 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. 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.