slides.write

slides.write is a skill for Claude Code from causify-ai/helpers. It costs 11 tokens per session (421 once invoked), scanned A, original, Apache-2.0.

A lecture-slide writing guide for graduate-level academic courses. It turns a topic or source file into a specified number of Markdown slides and includes instructions for teaching style and visuals.

In plain words
What is it for?
Use it to create course slides from a topic or document, choose an appropriate slide count, and include academic formatting and visual guidance.
Why use it?
It provides a consistent structure for explaining technical material to students. It also defines where the finished slide file should be saved.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Good fit Use it to create course slides from a topic or document, choose an appropriate slide count, and include academic formatting and visual guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/causify-ai/helpers/slides.write
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 causify-ai/helpers --skill slides.write
Clone the repo
git clone --depth 1 https://github.com/causify-ai/helpers

Made for: Claude Code.

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 slides.write

README.md
[![agentmods](https://agentmods.dev/badge/skills/causify-ai/helpers/slides.write/github.svg)](https://agentmods.dev/skills/causify-ai/helpers/slides.write)
Your own site
<a href="https://agentmods.dev/skills/causify-ai/helpers/slides.write"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/slides.write/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 slides.write

Your own site · 80×15
<a href="https://agentmods.dev/skills/causify-ai/helpers/slides.write"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/slides.write.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 421 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 3
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
  • medium Agent Snooping · line 29
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00011 $0.00421
Opus 5.5 $0.00004 $0.00168
Sonnet 5.5 $0.00002 $0.00084
Haiku 4.5 $0.00001 $0.00042

Measured 28d ago against content hash 7383de2d81eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slides.write 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 28d 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.

.claude/skills/slides.write/SKILL.md · 49 lines

What it actually says

Goal

  • Given content or topic from the user, write a given number of slides

Workflow

Role

  • Your role is specified in .claude/skills/role.ai_researcher.md

Input

  • The user will provide:
    • Information, a topic, or a file <TOPIC> about the topic to describe
    • (Optional) Number of slides <NUM_SLIDES> otherwise assume <NUM_SLIDES> = 3
  • If the user has passed you a file <TOPIC> read it

Format

  • For all formatting rules, templates, and structural guidelines, see .claude/skills/slides.rules.md

Create Slides

  • Create <NUM_SLIDES> slides
  • Each slide needs to start with a * <TITLE> format
  • Open with a standalone * Roadmap slide and close with a standalone * Summary slide (before * References, if the deck has one); see .claude/skills/slides.rules.md ## Roadmap Slide / ## Summary Slide. These two do not count against <NUM_SLIDES>

Add Visuals

  • Follow the instructions from .claude/skills/figure.rules.md

Save Result

  • Do not print anything on the screen
  • Save the result in an output file <OUTPUT_FILE>
    • If there was no input file then create a new file <TOPIC>.slides.md in the current dir
    • If a file <FILE> was provided then create a file like <FILE>.slides.md
    • If the destination file already exists, delete it and create a new one

Verification

  • Make sure that the new slides render correctly, e.g.,
    > gen_slides.py -i <OUTPUT_FILE> --notes_to_pdf_args="--skip_action open_pdf"
    
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. 28d ago Changed · +4 lines 7383de2d81eb
  2. 1mo ago Changed · +6 lines · -4 tokens per session 738a0d0aabda
  3. 1mo ago First seen · 39 lines · 15 tokens per session scan A 6589be2a972b

Subscribe to this mod's changes

slides.write is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 421 once invoked, about $0.0000 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-09-03.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

exam-forecast

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

anthropics/claude-for-legal · 73 tokens

lean-formalize

Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…

wanshuiyin/Auto-claude-code-research-in-sleep · 81 tokens

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

yc-software/qm · 25 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens