agentleFS
jhy0285jhy0285/monofield/skills/weread-year-in-review-video-template/SKILL.md

weread-year-in-review-video-template

Skill6 starsChanged 6 months agoApache-2.0View on GitHub

WeRead-inspired HyperFrames video template for vertical annual reading reports, personal reading dashboards, book-note recaps, and shareable year-in-review stories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper texture, editorial Chinese typography, book-page metaphors, data highlights, and deterministic motion.

1 other project uses 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, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a vertical HyperFrames composition for annual reading reports: WeRead, Goodreads, Readwise, Notion reading logs, book clubs, or …

    line 40
  2. Distinctive:

    Keep the WeRead-inspired visual language:

    line 71
  3. Distinctive:

    Keep the composition deterministic:

    line 78
  4. Very specific:

    no infinite loops or repeat: -1

    line 81
  5. Distinctive:

    no dependency on scroll, hover, localStorage, or runtime class discovery

    line 82

≈ “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

WeRead Year in Review Video Template

Create a vertical HyperFrames composition for annual reading reports: WeRead, Goodreads, Readwise, Notion reading logs, book clubs, or personal learning recaps. The template turns reading time, active days, bookshelf assets, notes, keywords, and a reading persona into a shareable 9:16 video.

Resource Map

weread-year-in-review-video-template/
├── SKILL.md
├── assets/
│   └── template.html
├── references/
│   └── checklist.md
└── example.html

The rendered MP4 showcase used by example.html is hosted at https://repo-assets.open-design.ai/resources/videos/skills/weread-year-in-review-video-template/default-showcase.mp4.

Workflow

  1. Copy assets/template.html to index.html.
  2. Replace the default report data in the REPORT object:
    • owner/title
    • reading hours and active days
    • bookshelf and completion stats
    • note composition
    • interest keywords
    • reading persona and share line
  3. Preserve the 12-scene timeline unless the user asks for a shorter cut.
  4. Keep the WeRead-inspired visual language:
    • warm paper background
    • ink-blue typography
    • restrained WeRead green accents
    • book pages, bookmarks, highlights, note cards, and shelf metaphors
  5. Motion should feel like flipping through a reading journal. Avoid techy slide transitions, bouncy UI effects, and dashboard-loading motion.
  6. Keep the composition deterministic:
    • direct data-start, data-duration, and data-track-index attributes
    • no unseeded randomness
    • no infinite loops or repeat: -1
    • no dependency on scroll, hover, localStorage, or runtime class discovery
  7. Validate against references/checklist.md before emitting.

Output Contract

Emit one short orientation sentence, then a single HTML artifact:

<artifact identifier="weread-year-in-review-video-template" type="text/html" title="WeRead Year in Review Video Template">
<!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.