agentleFS
Sign inStart free
RudywizzRudywizz/rudywizz-motion/skills/history-video/SKILL.md

history-video

Skill4 starsChanged 9 days agoMITView on GitHub

Sepia documentary pack — year title cards, antique atlas route maps, the user's portraits/paintings drawn as engravings, handwritten letters with wax seals, old-film grade. Use when the user types /history-video or wants a history / documentary style video or reel.

  • Installs packages

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Read $RM/SKILL.md once for setup, the workflow (check stills → render → verify) and the full catalogue.

    line 17
  2. Very specific:

    Put the user's text in single quotes (write '\'' for an apostrophe inside it) so the shell never interprets it.

    line 18
  3. Very specific:

    Start from $RM/templates/history-short.json and adapt it:

    line 20
  4. Distinctive:

    Keep facts as the user gives them — do not invent dates or quotes.

    line 31

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

/history-video — documentary pack

Find the engine (the sibling rudywizz-motion skill folder) and a temp folder both bash and Node agree on:

RM="${CLAUDE_SKILL_DIR}/../rudywizz-motion"
[ -f "$RM/engine/cli.mjs" ] || RM=$(ls -dt "${CLAUDE_PLUGIN_ROOT}/skills/rudywizz-motion" ~/.claude/plugins/cache/*/rudywizz-motion/*/skills/rudywizz-motion ~/.claude/skills/rudywizz-motion .claude/skills/rudywizz-motion 2>/dev/null | head -1)
TMP=$(node -p "require('os').tmpdir()")
(cd "$RM" && node -e "require.resolve('playwright')" 2>/dev/null) || (cd "$RM" && npm install --no-audit --no-fund)   # first run only

Read $RM/SKILL.md once for setup, the workflow (check stills → render → verify) and the full catalogue. Put the user's text in single quotes (write '\'' for an apostrophe inside it) so the shell never interprets it.

Start from $RM/templates/history-short.json and adapt it:

BeatScene
Date + title{ "style": "history-title", "text": "1071 / Malazgirt / Anadolu'nun kapısı" }
Where{ "style": "map-route", "theme": "atlas", "route": ["Malazgirt", "Konya"], "camera": "tilt-reveal" }
Who{ "image": "<user's portrait or painting>", "look": { "type": "engrave", "reveal": 3 }, "camera": "push-in" }
Voice{ "style": "parchment-letter", "text": "…", "place": "…, 1897", "signature": "…", "seal": "…" }

Global look: { "grade": "sepia", "film": 0.6, "weave": 1, "grain": 0.07, "vignette": 0.5 }; transitions burn, ink, leak. Images should be the user's own or public-domain works; the engrave look works best on portraits with clear light and shadow. Keep facts as the user gives them — do not invent dates or quotes.

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.

Check your setup, free