one-pager-and-slide-outline
Skill14 starsChanged 8 months agoMITView on GitHub
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.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- account-brief-builderSkill
- battlecard-builderSkill
- call-insights-to-objectionsSkill
- call-review-coachSkill
- case-study-extractorSkill
- certification-program-builderSkill
- content-gap-analysisSkill
- content-governance-systemSkill
- deal-inspection-coachSkill
- discovery-and-demo-structureSkill
- discovery-rubric-auditorSkill
- enablement-house-styleSkill
- enablement-impact-storySkill
- enablement-metrics-and-instrumentationSkill
- enablement-program-designSkill
- enablement-routerSkill
- executive-briefing-builderSkill
- field-feedback-synthesizerSkill
- forecast-risk-briefSkill
- manager-coaching-cadenceSkill
- mutual-action-plan-builderSkill
- objection-library-builderSkill
- onboarding-program-builderSkill
- onboarding-to-value-playbookSkill
- partner-enablement-packageSkill
- pipeline-stage-definition-and-exit-criteriaSkill
- product-launch-enablementSkill
- proposal-rfp-orchestratorSkill
- qbr-ebr-builderSkill
- quarterly-enablement-plannerSkill
- release-notes-to-seller-updatesSkill
- renewal-and-expansion-enablementSkill
- revenue-enablement-contextSkill
- roleplay-scenario-builderSkill
- talk-track-builderSkill
- value-prop-and-positioningSkill
- win-loss-synthesisSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use slide headlines to carry the argument where the evidence supports a claim.
- Very specific: line 16
If the user needs positioning first, use value-prop-and-positioning.
- Distinctive: line 22
Ask only for what changes the artifact:
- Distinctive: line 30
Do not invent evidence or approved claims.
- Distinctive: line 34
Read references/narrative-outline-template.md for the one-pager flow and slide-headline rules.
- Distinctive: line 40
Write one thesis and one ask.
- Distinctive: line 44
If both are requested, reuse the same evidence spine.
- Distinctive: line 52
Keep source and approval notes separate from the reader-facing copy.
- Distinctive: line 56
No visual design, no slide production
- Distinctive: line 62
Every major claim has a source or an explicit gap.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
One-pager and slide outline
Turn supplied messaging into a one-pager or slide outline that helps its audience understand the evidence and take the intended action.
Use slide headlines to carry the argument where the evidence supports a claim. Navigation, instructions, and genuine questions may use other heading forms.
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.
Inputs
Reuse supplied context first. If a missing company fact would change the result, check the relevant sections of .enablement/context.md when available. Preserve source dates and approval limits.
Ask only for what changes the artifact:
- Audience, channel, and whether it is internal, customer-facing, or partner-facing
- The single objective and the ask
- Source material and which claims are approved for that audience
- Output branch: one-pager, slide outline, or both
- Length or slide-count limit
Do not invent evidence or approved claims.
Supporting material
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.
Procedure
- Pick the branch before drafting. Do not produce both unless asked.
- Build a claim register: fact, interpretation, assumption, source, approval.
- Write one thesis and one ask. Everything else supports those two sentences.
- Change the information hierarchy for the job: executive decision, seller action, partner execution, or internal alignment. Do not only change tone.
- One-pager: lead with the point the reader needs, then include the context, proof, and action necessary to support it. Fit the requested page limit; preserve a supplied structure when it works.
- Slides: one assertion, one evidence cue, one speaker intent per slide.
- If both are requested, reuse the same evidence spine.
- Appendix only when it protects the core from clutter.
- Final pass: claims, audience safety, length, next action.
Sending or publishing the material requires explicit approval of the audience and final copy.
What to return
Keep source and approval notes separate from the reader-facing copy. For a light edit, preserve accurate content and the author's voice; report only material evidence or 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

