Agent skill

Slide Excellence

by pedrohcgs in pedrohcgs/claude-code-my-workflow

Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally).

MITAuto-check: notesDocuments & Office

Install Slide Excellence

skills CLI
$ npx skills add pedrohcgs/claude-code-my-workflow --skill slide-excellence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pedrohcgs/claude-code-my-workflow slide-excellence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/slide-excellence .claude/skills/slide-excellence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
slide-excellence
GitHub stars
1.7k
Token cost
~3.3k tokens
SKILL.md length
1,102 words
Files
1
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally).

  • Works in 6 steps: Identify the File → Pre-flight — Detect Conditions → Domain-reviewer customization check… → …
  • User says full review
  • SKILL.md covers Step 1: Identify the File, Step 2: Pre-flight — Detect…, Step 3: Domain-reviewer… and Step 4: Run Review Agents in…, plus 6 more sections
  • Calls python3

What it does

Slide Excellence is an agent skill from pedrohcgs/claude-code-my-workflow. Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally). Use when user says "full review", "excellence pass", "comprehensive check", "review everything", "pre-release review", "slide excellence", or before teaching / shipping a deck. Fanout wrapper — for a single lens, use /visual-audit, /pedagogy-review, or /proofread directly.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Slides and decks, Copy editing and proofreading and LaTeX. The repository describes itself as: A ready-to-fork Claude Code template for academics using LaTeX/Beamer + R. Multi-agent review, quality gates, adversarial QA, and replication protocols. The licence is MIT.

When your agent uses it

  • User says full review
  • Excellence pass
  • Comprehensive check
  • Review everything

Example prompts

  • “full review”
  • “excellence pass”
  • “comprehensive check”
  • “/slide-excellence”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Bash, Agent, Task

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Identify the File
  2. Pre-flight — Detect Conditions
  3. Domain-reviewer customization check (MANDATORY for .tex)
  4. Run Review Agents in Parallel
  5. Synthesize Combined Summary (reduce typed findings)
  6. Report Token/Time Budget

What it can do on your machine

Read from SKILL.md and the folder at commit ae72617. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Write
    • Bash
    • Agent
    • Task

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Slide Excellence loads about 3.3k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,102 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Write, Bash, Agent, Task

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pedrohcgs/claude-code-my-workflow at commit ae72617, republished under its MIT licence (© pedrohcgs). 1,102 words, ~3,321 tokens.

Download SKILL.mdSave it as .claude/skills/slide-excellence/SKILL.md (or your agent's skills folder).
name
slide-excellence
description
Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally). Use when user says "full review", "excellence pass", "comprehensive check", "review everything", "pre-release review", "slide excellence", or before teaching / shipping a deck. Fanout wrapper — for a single lens, use `/visual-audit`, `/pedagogy-review`, or `/proofread` directly.
allowed-tools
Read, Grep, Glob, Write, Bash, Agent, Task
argument-hint
[QMD or TEX filename] [--fast] [--skip-substance | --acknowledge-template-domain-reviewer]
context
fork

Slide Excellence Review

Run a comprehensive multi-dimensional review of lecture slides. Multiple agents analyze the file independently, then results are synthesized.

Which slide-review skill do I want?

  • /slide-excellence (this skill) — multi-agent fanout (visual + pedagogy + proofread, plus TikZ / parity / substance conditionally). Best for pre-teaching or pre-release checks.
  • /visual-audit — single lens, layout/overflow/font/spacing only. Fast.
  • /pedagogy-review — single lens, narrative/prerequisites/worked-examples/notation.
  • /proofread — single lens, grammar/typos/overflow/terminology.
  • /qa-quarto — adversarial Beamer ↔ Quarto parity (critic-fixer loop).
  • /devils-advocate — 5-7 pointed challenges, not a full review.

Important: this orchestrator does conditional dispatch — it only spawns the subagents that can actually produce useful output for the given file. It does not run tikz-reviewer on a file with zero TikZ, or quarto-critic on a deck without a counterpart.

Step 1: Identify the File

Parse $ARGUMENTS for the filename. Resolve path in Quarto/ or Slides/.

Determine the file type:

  • .tex → Beamer
  • .qmd → Quarto
  • .md → Markdown slides

Step 2: Pre-flight — Detect Conditions

Before spawning any agent, probe the file to determine which reviews make sense:

bash
FILE="$resolved_path"

# Has TikZ diagrams?
has_tikz=$(grep -c '\\begin{tikzpicture}' "$FILE" 2>/dev/null); has_tikz=${has_tikz:-0}

# For .qmd: is there a paired .tex in Slides/?
has_tex_pair="false"
if [[ "$FILE" == *.qmd ]]; then
  base="$(basename "$FILE" .qmd)"
  # Common Beamer suffixes: _Topic, _Lecture, exact match
  for candidate in "Slides/${base}.tex" "Slides/Lecture${base}.tex"; do
    if [ -f "$candidate" ]; then
      has_tex_pair="true"
      tex_pair="$candidate"
      break
    fi
  done
fi

# For .tex: is there a paired .qmd in Quarto/?
has_qmd_pair="false"
if [[ "$FILE" == *.tex ]]; then
  base="$(basename "$FILE" .tex)"
  for candidate in "Quarto/${base}.qmd" "Quarto/${base#Lecture}.qmd"; do
    if [ -f "$candidate" ]; then
      has_qmd_pair="true"
      qmd_pair="$candidate"
      break
    fi
  done
fi

# Measure the Quarto render once — the file itself, or a .tex file's Quarto pair.
# The report goes to Agents A and E. slide-qa exits 0 (clean) or 1 (a finding:
# overflow, clipped content, or a broken asset) with a fresh report, 2 if it could
# not run (it deletes old reports first).
qa_report=""; qa_target=""
if [[ "$FILE" == *.qmd ]]; then qa_target="$FILE"
elif [ "$has_qmd_pair" = "true" ]; then qa_target="$qmd_pair"; fi
if [ -n "$qa_target" ]; then
  quarto render "$qa_target" >/dev/null 2>&1
  "${SLIDE_QA_PYTHON:-python3}" scripts/slide-qa.py "$qa_target"
  if [ $? -ne 2 ]; then
    qa_report="quality_reports/audits/slide-qa/$(basename "$qa_target" .qmd)/report.md"
  fi
fi

# Has R code chunks or referenced R scripts?
has_r="false"
if grep -qE '```\{r|source\(.*\.R\)' "$FILE" 2>/dev/null; then
  has_r="true"
fi

Report the detection:

File:         path/to/file.tex
Type:         Beamer (.tex)
TikZ blocks:  3
Quarto pair:  Quarto/Lecture2.qmd (found)
R chunks:     none
Slide QA:     quality_reports/audits/slide-qa/Lecture2/report.md (or: could not run — reason)

Step 3: Domain-reviewer customization check (MANDATORY for .tex)

Before spawning the substance-review agent on a .tex file, verify .claude/agents/domain-reviewer.md has been customized for this project. The ship-state domain-reviewer is a template — running it unmodified produces generic "are assumptions stated?" feedback, not real domain review.

Detection heuristic (any of these → still template):

  • Contains the marker token AUTO-DETECT-TEMPLATE-MARKER anywhere in the file (present in the shipped template; removed/replaced when customized). Detection is a substring match — the marker can span lines.
  • Contains any <!-- Customize: ... --> or [Customize: ...] placeholder (both forms are checked).
  • The five lenses are identical to the shipped template's wording (diff against .claude/agents/domain-reviewer.md on the v1.3.0 tag — if zero lines changed, it's still template).

If the template marker is present:

⚠️  domain-reviewer.md has not been customized for your field.

Running it in its shipped state produces generic checks ("are assumptions
stated?") rather than field-specific review. Options:

  1. Customize .claude/agents/domain-reviewer.md — replace the 5 lenses
     with checks for your field (the file's EXAMPLES block shows two
     disciplines to copy from).
  2. Run slide-excellence with --skip-substance to proceed without the
     substance-review agent. Other reviewers still run.
  3. Run slide-excellence with --acknowledge-template-domain-reviewer to
     proceed anyway (you'll get generic feedback from the substance agent).

Stop here and return these options — this skill runs in a forked context and cannot wait for an answer. Do not run domain-reviewer on the uncustomized template; the user re-invokes with the flag they choose.

Step 4: Run Review Agents in Parallel

Spawn only the agents whose conditions hold:

Always-on for slides (.tex or .qmd):

  • Agent A: Visual Audit (slide-auditor) Overflow, font consistency, box fatigue, spacing, images. When $qa_report is set (a .qmd, or a .tex with a Quarto pair), pass it — measured overflow plus screenshots; if slide-qa could not run, say so in the summary. Save: quality_reports/[FILE]_visual_audit.md.

  • Agent B: Pedagogical Review (pedagogy-reviewer) 13 pedagogical patterns, narrative, pacing, notation. Save: quality_reports/[FILE]_pedagogy_report.md.

  • Agent C: Proofreading (proofreader) Grammar, typos, consistency, academic quality, citations. Save: quality_reports/[FILE]_proofread_report.md.

Conditional:

  • Agent D: TikZ Review (tikz-reviewer) — only if has_tikz > 0. Measurement-based collision audit (Bézier, gaps, boundaries, margins). Save: quality_reports/[FILE]_tikz_review.md.

  • Agent E: Content Parity (quarto-critic) — only if the file has a counterpart (has_tex_pair or has_qmd_pair). Frame count comparison, environment parity, content drift between .tex ↔ .qmd. Pass $qa_report when there is one. Save: quality_reports/[FILE]_parity_report.md.

  • Agent F: R Code Review (r-reviewer) — only if has_r == true. Code correctness for any embedded R chunks or referenced scripts. Save: quality_reports/[FILE]_r_review.md.

  • Agent G: Substance Review (domain-reviewer) — MANDATORY for .tex, OPTIONAL for .qmd, GATED by Step 3. Domain correctness via the 5-lens framework. Save: quality_reports/[FILE]_substance_review.md.

De-duplication: if one of these skills already produced a report for this file in the current session (e.g. /proofread ran first), reuse that report when it is newer than the file and list which reports were reused — this skill runs in a forked context and cannot stop to ask. To force a fresh pass, move the old report out of quality_reports/ (or touch the deck so it is newer) and re-invoke.

Step 5: Synthesize Combined Summary (reduce typed findings)

This is fan-out → reduce (orchestrator-protocol.md): each agent returns FINDINGs + a SCORECARD in the shared schema (orchestration-schemas.md), and this step stacks the typed scorecards rather than re-reading each report by eye. The Overall Quality Score is the gate predicate over summed CRITICAL/MAJOR/MINOR counts. (Conditional dispatch means a skipped lens contributes no findings, not zeros to average.)

Only include sections for agents that actually ran.

markdown
# Slide Excellence Review: [Filename]

**File:** [path]
**Type:** [Beamer / Quarto / Markdown]
**Detected:** TikZ=N | pair=[path or none] | R=[yes/no]
**Agents spawned:** [A, B, C, D, G] (skipped: E [no pair], F [no R])

## Overall Quality Score: [EXCELLENT / GOOD / NEEDS WORK / POOR]

| Dimension | Critical (`blocker`) | Major | Minor | Score/10 |
|-----------|----------|--------|-----|-----|
| Visual/Layout | | | | |
| Pedagogical | | | | |
| Proofreading | | | | |
| TikZ (if ran) | | | | |
| Substance (if ran) | | | | |

### Critical Issues (Immediate Action Required)
### Major Issues (Next Revision)
### Recommended Next Steps

Step 6: Report Token/Time Budget

After completion, print what was spawned:

Spawned N agents[; token usage: actual figure, if the harness reports it].
For cost-conscious reviews, run individual subagent skills directly
(/proofread, /visual-audit, /pedagogy-review).
Show full SKILL.md (449 more words)Show less

Flag Reference

FlagEffect
--skip-substanceDon't spawn Agent G (domain-reviewer). Useful if you haven't customized domain-reviewer.md yet.
--acknowledge-template-domain-reviewerProceed with the un-customized domain-reviewer anyway; you accept that the substance review will be generic.
--fastSpawn a single synthesis agent reading the file directly, rather than parallel subagents. Cheaper but less thorough.

Quality Score Rubric

ScoreCritical (blocker)MajorMeaning
Excellent00Ready to present
Good01-5Revise the majors first (the gate reads this as REVISE)
Needs Work0-56+, or any with criticalsSignificant revision — the gate blocks while any critical remains
Poor6+anyMajor restructuring

Any critical finding blocks, whatever the other counts — the same gate predicate as orchestration-schemas.md §3.

Why conditional dispatch matters

A reviewer that cannot produce useful output costs tokens and trust: tikz-reviewer on a TikZ-free deck returns nothing, quarto-critic without a counterpart file has no pair to compare, and an uncustomized domain-reviewer returns generic "are assumptions stated?" feedback that authors learn to ignore. Spawn only the lenses the file can use.

Findings are validated, not just written (v2.5)

This skill's reviewers emit findings under the machine-checked contract in finding-schema.json. Reports are JSON arrays.

Smoke-test the harness before spending review effort — a run that fans out reviewers and then cannot write a valid report has wasted the whole pass:

bash
echo '[]' | python3 scripts/validate-findings.py

Reviewer agents are read-only, so this skill writes the files. For each reviewer's final response: save the prose report to this skill's report path for that reviewer, copy its closing fenced json block to a scratch file, and fill the ids while validating:

bash
python3 scripts/validate-findings.py --fill-ids block.json > <report>.json.tmp \
  && mv <report>.json.tmp <report>.json || rm -f <report>.json.tmp   # exit 0 required; a failed run keeps no file
python3 scripts/validate-findings.py --check-quotes <report>.json   # each quote must be the file's own text (orchestration-schemas.md §1)

A reviewer that returned no json block, or a block that does not validate, has not reviewed: re-dispatch it once with the validator's error text, then report the lens as missing rather than reducing without it.

What the contract forces, and why:

  • rule — the documented rule or standard violated. A finding citing no rule is an opinion, and opinions do not gate a commit.
  • failing_case — a concrete configuration under which the claim breaks, or the exact missing hypothesis. "This could be clearer" does not validate.
  • id = sha1("<file>:<line>:<locus>") — deterministic, so dedup across rounds is exact and the two-strikes rule is checkable rather than eyeballed.
  • mechanical — true only for fixes that cannot change a result (typo, cross-reference, formatting, label). Never for an estimand, assumption, specification, inference procedure, sample definition, or reporting language: those return to the researcher.

Apply the per-lens evidence burdens and the "does NOT count" filters in orchestration-schemas.md §7 before verification, so known false alarms never reach the judge. The verifier pass is refute-biased and sets each finding's verdict (reviewers leave it unset): only verdict: "confirmed" findings ship; anything it cannot ground is dropped, not downgraded to a warning.

© pedrohcgs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/slide-excellence of pedrohcgs/claude-code-my-workflow.

Open the folder on GitHubat commit ae72617

Compare with similar skills

Slide Excellence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Slide Excellence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slide Excellence this skillpedrohcgs/claude-code-my-workflow1.7k—~3.3kAutomated safety check: NotesMIT
BeamerNoi1r/beamer-skill364—~13kAutomated safety check: NotesMIT
Slide Excellencebrycewang-stanford/Auto-Empirical-Research-Skills4.6k—~564Automated safety check: PassCustom licence
Brief Compliance Checkflonat/flonat-research146—~1.7kAutomated safety check: PassMIT
Compiledeckscunning1975/MixtapeTools4742 repos~3.1kAutomated safety check: PassNone
Scientific SlidesK-Dense-AI/claude-scientific-writer2.4k14 repos~5.4kAutomated safety check: NotesMIT

Similar skills

  • Beamer

    Noi1r/beamer-skill

    Beamer LaTeX slide workflow: create, compile, review, and polish academic presentations.

    364 GitHub stars~13k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Slide Excellence

    brycewang-stanford/Auto-Empirical-Research-Skills

    Multi-agent slide review (visual, pedagogy, proofreading). An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.

    4.6k GitHub stars~564 tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed
  • Brief Compliance Check

    flonat/flonat-research

    Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief.

    146 GitHub stars~1.7k tokensUpdated 11 days ago
    Documents & OfficeAuto-check passed
  • Compiledeck

    scunning1975/MixtapeTools

    Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy.

    474 GitHub starsUsed in 2 repos~3.1k tokens
    Documents & OfficeAuto-check passed
  • Scientific Slides

    K-Dense-AI/claude-scientific-writer

    Build slide decks and presentations for research talks. An agent skill from K-Dense-AI/claude-scientific-writer.

    2.4k GitHub starsUsed in 14 repos~5.4k tokens
    Documents & OfficeAuto-check: notes
  • Powerpoint Slides

    Noi1r/powerpoint-skill

    Create visually rich PowerPoint (.pptx) presentations from academic papers, research notes, or any content the user wants in slide format.

    124 GitHub stars~12k tokensUpdated 6 mo ago
    Documents & OfficeAuto-check: notes

More from pedrohcgs/claude-code-my-workflow

All 59 skills in this repo
  • Devils Advocate

    pedrohcgs/claude-code-my-workflow

    Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.

    1.7k GitHub starsUsed in 2 repos~641 tokens
    Auto-check passed
  • Vaccinate

    pedrohcgs/claude-code-my-workflow

    Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch.

    1.7k GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check: notes
  • Compile Latex

    pedrohcgs/claude-code-my-workflow

    Compile a Beamer LaTeX slide deck with XeLaTeX (3 passes + bibtex).

    1.7k GitHub starsUsed in 1 repo~492 tokens
    Auto-check: notes
  • Context Status

    pedrohcgs/claude-code-my-workflow

    Show current context status and session health. An agent skill from pedrohcgs/claude-code-my-workflow.

    1.7k GitHub starsUsed in 1 repo~613 tokens
    Auto-check: notes
  • Capture Environment

    pedrohcgs/claude-code-my-workflow

    Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt /…

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes
  • Checkpoint

    pedrohcgs/claude-code-my-workflow

    Save a structured state snapshot before stopping or handing off.

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes

Questions about Slide Excellence

What does Slide Excellence do?

Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally). Slide Excellence is an agent skill from pedrohcgs/claude-code-my-workflow. Multi-agent comprehensive slide review (visual + pedagogy + proofreading, plus TikZ / parity / substance conditionally).

When should I use Slide Excellence?

Slide Excellence fits situations like: user says full review; excellence pass; comprehensive check; review everything.

How do I install Slide Excellence in Claude Code?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill slide-excellence -a claude-code`. Or copy the skill folder (.claude/skills/slide-excellence in pedrohcgs/claude-code-my-workflow) into .claude/skills/slide-excellence in your project. Claude Code loads it when a task matches its description.

How do I install Slide Excellence in Codex?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill slide-excellence -a codex`. Or copy the skill folder (.claude/skills/slide-excellence in pedrohcgs/claude-code-my-workflow) into .agents/skills/slide-excellence in your project. Codex loads it when a task matches its description.

Can I use Slide Excellence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pedrohcgs/claude-code-my-workflow --skill slide-excellence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slide-excellence, .gemini/skills/slide-excellence, .github/skills/slide-excellence and .opencode/skills/slide-excellence in your project.

What does Slide Excellence need to run?

Going by SKILL.md and its folder, Slide Excellence needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Bash, Agent, Task.

Does Slide Excellence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Slide Excellence safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Slide Excellence use?

Slide Excellence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slide Excellence use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slide Excellence?

Skills that share tags, products or a category with Slide Excellence: Beamer (Noi1r/beamer-skill, 364 stars), Slide Excellence (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Brief Compliance Check (flonat/flonat-research, 146 stars) and Compiledeck (scunning1975/MixtapeTools, 474 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slide Excellence?

pedrohcgs (a GitHub user) maintains it in pedrohcgs/claude-code-my-workflow, which has 1,655 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on September 27, 2026.

Source: pedrohcgs/claude-code-my-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.