agentsclimarketplace
Sign in

One pager and slide outline

Skill nthnclrk/enablement-skills/skills/one-pager-and-slide-outline

Package a defined or approved narrative into a concise one-pager, an assertion-led slide outline, or both from supplied source material. Use for leave-behinds, briefing notes, internal memos, and stakeholder updates when the underlying strategy already exists. Route launch readiness or training design to product-launch-enablement, raw release translation to release-notes-to-seller-updates, message strategy to value-prop-and-positioning, and finished visual production to the user's presentation workflow.From its SKILL.md

Install
npx -y skills add nthnclrk/enablement-skills --skill one-pager-and-slide-outline

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

  • 11 stars11 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.9 KB, as published. Nobody here has run it

One-pager and slide outline

Package an existing narrative. Do not invent the strategy here.

One artifact, one job. Slide headlines are assertions, not topic labels.

Assertion. "Missed handoffs are now a Friday-ship risk, not an ops nuisance."

Topic. "Overview." "Our solution." "Next steps."

If the user needs positioning first, use value-prop-and-positioning. If they need a launch plan, use product-launch-enablement. This skill does not produce finished slides.

Confirm Inputs First

Ask only for what changes the artifact:

  1. Audience, channel, and whether it is internal, customer-facing, or partner-facing
  2. The single objective and the ask
  3. Source material and which claims are approved for that audience
  4. Output branch: one-pager, slide outline, or both
  5. Length or slide-count limit

Do not invent evidence or approved claims.

Read The Right Reference

Read references/narrative-outline-template.md for the one-pager flow and slide-headline rules. Skip it if the user already specified a house format.

Default Workflow

  1. Pick the branch before drafting. Do not produce both unless asked.
  2. Build a claim register: fact, interpretation, assumption, source, approval.
  3. Write one thesis and one ask. Everything else supports those two sentences.
  4. Change the information hierarchy for the job: executive decision, seller action, partner execution, or internal alignment. Do not only change tone.
  5. One-pager: assertion, context, problem, approach, proof, decision, next steps. One page.
  6. Slides: one assertion, one evidence cue, one speaker intent per slide.
  7. If both are requested, reuse the same evidence spine.
  8. Appendix only when it protects the core from clutter.
  9. Final pass: claims, audience safety, length, next action.

Output Contract

Always include the evidence map and any approval gaps.

  • One-pager only, slide outline only, or both, matching the request
  • Audience variants only when asked or when the audience actually changes the argument
  • No visual design, no slide production

Quality Bar

  • One dominant argument.
  • Slide headlines can be read as claims.
  • Every major claim has a source or an explicit gap.
  • The next action has an owner.
  • Internal-only proof never appears on a customer or partner artifact.
  • A reader can use it without reconstructing the source pile.

Keep looking

Skills are one crate of 627,801. 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.