agentleFS
jhy0285jhy0285/monofield/skills/html-ppt-retro-quarterly-review/SKILL.md

html-ppt-retro-quarterly-review

Skill6 starsChanged 6 months agoApache-2.0View on GitHub

Retro Quarterly Review presentation template in a bold blue + orange editorial language. Use when users ask for a high-impact quarterly review / roadmap deck with heavyweight slab headlines, clean cream paper sections, structured grids, and fast premium motion pacing (3 slides, each hold under 3s in video mode).

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

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read active DESIGN.md first and map any requested token changes into CSS variables while preserving the retro blue/orange/cream visual …

    line 57
  2. Very specific:

    Start from assets/template.html.

    line 59
  3. Distinctive:

    Keep interactions and motion quality:

    line 61
  4. Distinctive:

    Keep output self-contained (single HTML, inline CSS + JS, no framework runtime).

    line 66
  5. Distinctive:

    If adapting copy/data, keep content realistic and internally consistent.

    line 67

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

Retro Quarterly Review Template

A high-contrast, print-inspired quarterly review template with three cinematic slides:

  1. Cover (hero title lockup)
  2. Three priorities (triptych grid)
  3. Roadmap timeline + KPI strip

Resource map

html-ppt-retro-quarterly-review/
├── SKILL.md
├── assets/
│   └── template.html
├── references/
│   └── checklist.md
└── example.html

Workflow

  1. Read active DESIGN.md first and map any requested token changes into CSS variables while preserving the retro blue/orange/cream visual grammar.
  2. Start from assets/template.html; do not rebuild from scratch.
  3. Preserve the three-slide information architecture and typographic hierarchy.
  4. Keep interactions and motion quality:
    • keyboard 1/2/3 quick jump
    • R restart
    • page indicator updates per scene
    • premium wipe transitions and staggered reveals
  5. Keep output self-contained (single HTML, inline CSS + JS, no framework runtime).
  6. If adapting copy/data, keep content realistic and internally consistent.
  7. Validate against references/checklist.md before emitting artifact.

Output contract

Emit one short orientation sentence and then the artifact:

<artifact identifier="retro-quarterly-review" type="text/html" title="Retro Quarterly Review">
<!doctype html>
<html>...</html>
</artifact>

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.