agentleFS
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/academic-slides/SKILL.md

academic-slides

Skill56 starsChanged 3 months agoMITView on GitHub

Plan, create, and review academic presentations for conference talks, thesis defenses, seminars, lab meetings, and paper-to-slide workflows.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check tools, packages, credentials, network access, and runtime capabilities before execution.

    line 29
  2. Distinctive:

    Create or improve an academic presentation and its talk narrative.

    line 33
  3. Distinctive:

    Use the presentation tooling available in the runtime or repository.

    line 40
  4. Distinctive:

    Keep methods and results legible.

    line 41
  5. Distinctive:

    Add rehearsal timing, likely questions, and a backup-slide plan.

    line 42
  6. Distinctive:

    Avoid dense paper paragraphs, tiny figures, and unsupported decorative visuals.

    line 56
  7. Distinctive:

    Never claim a slide or deck was rendered when only an outline was produced.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rylai Codex-Hermes-Claude Edition | Maintained and adapted by Rylai

Runtime Compatibility

  • Codex: install under ~/.agents/skills/academic-slides.
  • Hermes: install under ~/.hermes/skills/academic-slides or expose the bundle through skills.external_dirs.
  • Claude Code: install under ~/.claude/skills/academic-slides or <project>/.claude/skills/academic-slides.
  • Claude.ai and Cowork: upload and enable the matching per-skill ZIP.
  • Resolve bundled files relative to this skill directory; do not depend on paths from another machine.
  • Check tools, packages, credentials, network access, and runtime capabilities before execution.

Academic Slides

Create or improve an academic presentation and its talk narrative.

Workflow

  1. Confirm audience, setting, duration, slide count, source paper, and required output.
  2. Define one main claim and an evidence sequence that fits the allotted time.
  3. Build a slide outline with action titles, visual intent, and speaker purpose.
  4. Use the presentation tooling available in the runtime or repository.
  5. Keep methods and results legible; move secondary detail to backup slides.
  6. Add rehearsal timing, likely questions, and a backup-slide plan.
  7. Render and visually inspect the deck before delivery.

Bundled Guidance

  • assets/talk-outline-template.md: planning worksheet.
  • references/talk-structure.md: narrative structures by talk type.
  • references/slide-design.md: hierarchy and density rules.
  • references/slide-creation.md: implementation and QA workflow.
  • references/delivery-and-qa.md: rehearsal, timing, and Q&A preparation.

Quality Bar

  • Titles should state takeaways rather than topic labels.
  • Avoid dense paper paragraphs, tiny figures, and unsupported decorative visuals.
  • Never claim a slide or deck was rendered when only an outline was produced.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.