AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

One Pager

skill-0xelitesystem-claude-skills-templates-one-pager · by 0xelitesystem

Turn raw notes, transcripts, or longform content into a tight one-page executive brief. Use whenever the user wants a one-pager, exec brief, briefing doc, or asks to compress longer content into a structured one-page summary. Triggers on phrases like "write a one-pager", "make this a brief", "summarize for an exec", "turn these notes into a brief", or when the user uploads notes or meeting transc…

No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-0xelitesystem-claude-skills-templates-one-pager

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-0xelitesystem-claude-skills-templates-one-pager)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of One Pager? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

One-Pager Writer

Converts raw input (notes, transcripts, source articles, research dumps) into a structured one-page brief.

Output structure

Always use these five sections in this order.

TL;DR

One sentence. The headline finding or recommendation. If the reader stops here, they should know what changed.

Context

Two to four sentences. What prompted this? What is the reader supposed to know to make sense of the rest?

Findings

Three to five bullets. Each is a specific, sourced claim. If a claim has a number, include the number. If it has a source, attribute it.

Recommendation

One paragraph. What should the reader do, decide, or believe? If there is a decision to make, state it. If the recommendation is conditional, state the condition.

Next Steps

Three to five concrete actions, each with an owner placeholder if known. Each action should be doable in a week or less.

Style rules

  • No em-dashes. Use commas, semicolons, or split into two sentences.
  • No filler openings. Skip "In today's...", "It is worth noting that...", "When it comes to...".
  • No banned vocabulary: delve, leverage as a verb, seamless, robust for non-statistical claims, navigate the landscape, paradigm shift, journey as a metaphor, unlock the power, harness the power, foster as a verb.
  • Concrete over abstract. "Revenue rose 18% in Q3" beats "significant revenue growth was observed".
  • Active voice. Name the actor.
  • Length cap: roughly 350 words total. If you exceed it, cut bullets, not sections.

When you do not have enough input

If the source content is too thin to fill all five sections honestly, do not invent content. Mark the thin section with [needs input: ] and ask the user one specific question per gap.

Output format

Render as plain markdown. Section headings as ###. No tables unless the user asks for one. No code blocks unless the source contains code worth quoting.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.