agentmods.dev

deck-from-report

deck-from-report is a skill for Claude Code, Codex from contextgo/contextgo. It costs 34 tokens per session (507 once invoked), scanned A, original, Apache-2.0.

A workflow for turning a long report or structured Markdown document into a presentation summary. It selects the main sections, useful data tables, important quotes, slide layouts, themes, and export settings.

In plain words
What is it for?
Use it to create a summary presentation from a report, including a chosen slide recipe, applied visual theme, and reproducible build output.
Why use it?
It helps condense a large document into a coherent deck while preserving coverage of the report’s main evidence and conclusions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 14repo 5mo ago A scan 34 tokens original Apache-2.0

Good fit Use it to create a summary presentation from a report, including a chosen slide recipe, applied visual theme, and reproducible build output.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/contextgo/contextgo/deck-from-report
View source ↗ contextgo/contextgo
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add contextgo/contextgo --skill deck-from-report
Clone the repo
git clone --depth 1 https://github.com/contextgo/contextgo

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for deck-from-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/contextgo/contextgo/deck-from-report/github.svg)](https://agentmods.dev/skills/contextgo/contextgo/deck-from-report)
Your own site
<a href="https://agentmods.dev/skills/contextgo/contextgo/deck-from-report"><img src="https://agentmods.dev/badge/skills/contextgo/contextgo/deck-from-report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for deck-from-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/contextgo/contextgo/deck-from-report"><img src="https://agentmods.dev/badge/skills/contextgo/contextgo/deck-from-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 507 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00507
Opus 5.5 $0.00014 $0.00203
Sonnet 5.5 $0.00007 $0.00101
Haiku 4.5 $0.00003 $0.00051

Measured 2mo ago against content hash b8443cb8fd28, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deck-from-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/process/resources/assistant/creative/visual-artifact-runner/skills/deck-from-report/SKILL.md · 65 lines

What it actually says

Deck From Report

Use this skill when the user provides a long-form report or markdown document and wants a summary deck.

Read ../../docs/input-contracts.md, ../../docs/layout-recipes.md, and ../../docs/quality-checks.md before drafting.

Use when

  • The input is a long-form report or structured markdown.
  • The expected output is a presentation deck distilled from that report.
  • The team wants citation-aware section coverage.

Do not use when

  • The input is a short brief (use deck-from-brief).
  • The input is a PDF document (use pdf-to-deck).
  • The user wants a flat handout (use the PDF or infographic recipes).

Workflow

1. Extract the report skeleton

Identify the executive thesis, the 3 to 7 most load-bearing sections, the data tables worth visualizing, and the quotes worth surfacing as callouts.

2. Pick the recipe

Default to deck.report-summary. Switch to deck.exec-summary when the user asks for a 5 to 8 slide condensed deck. Record the rejected alternatives.

3. Apply the theme

Resolve all theme tokens before drafting slide content. Honor any theme override the user provides.

4. Choose the export mode

Default to pptx-static. Use pptx-morph when the report contains narrative arcs that materially benefit from Morph transitions. Delegate Morph builds to morph-ppt per ../../docs/morph-integration.md.

5. Produce the artifact

  • generate the slide flow with section attribution back to the source
  • run pre-export QC
  • write the export file plus build-notes.md, assets.json, and failures.json
  • preserve traceability between each slide and the report section that produced it

Output

  • a deck artifact in the requested mode
  • a build note that records the chosen recipe, theme, mode, and section attribution
  • an asset inventory and a failure list
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 65 lines · 34 tokens per session scan A b8443cb8fd28

Subscribe to this mod's changes

deck-from-report is a skill published in the GitHub repository contextgo/contextgo (14 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 507 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Creative and mediaDocuments
Related

deck-from-report compared with skills from other repositories

deck-from-report next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
deck-from-reportcontextgo/contextgoSkill145mo agoApache-2.0A34Claude Code, Codex
orbit-notionnexu-io/open-designSkill106ktodayApache-2.0A117Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35ktodayApache-2.0A123Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skillsSkill49ktodayMITA48Claude Code
legal-holdanthropics/claude-for-legalSkill9.9ktodayApache-2.0A68Claude Code
ppt-reviewOrkas-AI/OrkasSkill9.1ktodayMITA2Claude Code, Codex
feishuHmbown/CodeWhaleSkill41k6d agoMITA33Claude Code, Codex