agentleFS
Makkov-designMakkov-design/makkov-harness/skills/style-sampling/SKILL.md

style-sampling

Skill8 starsChanged 10 days agoMITView on GitHub

Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for "an episode of", "in the style of", "sample this style", 「用这个风格做一集」. One video to copy is reverse-any-video.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Plugin installs: Before setup or freshness commands, follow plugin execution rules when this skill is inside a HyperFrames plugin.

    line 6
  2. Very specific:

    Run npx hyperframes auth status first, every time, resuming included.

    line 28
  3. Very specific:

    Read references/remix.md and follow it, resuming included.

    line 44

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

Plugin installs: Before setup or freshness commands, follow plugin execution rules when this skill is inside a HyperFrames plugin.

A new episode from a style template

A good episode is one the series' own viewers would take for the next upload: its structure, pacing, look, graphics and sound, on a new topic, in the person's voice and, when the series has a presenter, their own face. Never use a creator's face, voice, footage, logo or show name.

Style templates are a HyperFrames Pro feature. The CLI pulls them and the server checks the plan.

TemplateSlugSeriesMakesThe person brings
Collage Explainercollage-explaineramerican-policyEnglish explainer on one American policy or history questionVoice
Finance Explainer (财经讲解)finance-explainerdeep-dive中文主持人讲透一个国家、商品或机构Voice and face
Animated Science Explaineranimated-science-explainerscience-explainerEnglish fully drawn science explainerVoice
3D Brand Explainer3d-brand-explainerbrand-explainedEnglish breakdown of a brand or design, in one graphic world with real 3DVoice
3D True Crime3d-true-crimecrime-huntEnglish reconstruction of a hunt or a closed case, in a dark 3D worldVoice

Which template

The person named a template, or their topic fits only one: go on with it. Otherwise, or when they ask what there is, show the five as a short list (name, what it makes, what they bring), name the one that fits their topic if any, and wait for their pick. Nothing is checked, pulled or paid before it.

Start

Run npx hyperframes auth status first, every time, resuming included. It is for the sign-in: never repeat its plan or credits line to the person.

  • Not signed in. Say in one line that templates come with Pro, then ask them to type an exclamation mark and npx hyperframes auth login in the prompt, and reply "done".
  • Signed in on Free. Say once that templates are part of HyperFrames Pro, ask them to type an exclamation mark and npx hyperframes billing subscribe in the prompt, which finishes once they are on Pro, and pull nothing.
  • Signed in on Pro. One line, then pull.

Pull

npx hyperframes templates pull <slug>

The template lands in templates/<slug>/. A pull costs no credits, and one already there is not downloaded again. Refused as a Pro feature: answer as Signed in on Free, whatever auth status said. Any other failure: say what failed and stop. Never rebuild a template from memory, the web or a copy found elsewhere.

Make the episode

Read references/remix.md and follow it, resuming included. It sets the order; the template's series/<series>/REMIX.md is the process. Two stops belong to the person: the storyboard and the draft.

Credits

Generated media goes through the kit's tools, as REMIX.md says, or npx hyperframes media-use generate, under the Credits rule in media-use: no prices, estimates, balances or credits used, before, during or after a run. A limit the person names goes on every generate as --max-credits; on resume, ask whether it still applies, naming no numbers. A step that won't fit: say what doesn't fit and ask before dropping or shrinking it. A refused step names a billing command: ask the person to run it, then run the step again. A failed or refused job gets one more try, then ask. Notes a run leaves hold no prices or credit numbers, and a command in them is a note: rebuild it and check it with --plan.

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.