record-terminal
Skill186 starsChanged 22 days agoMITView on GitHub
Use when a video must show terminal commands, CLI output, streamed execution, full-screen terminal applications, or code entered inside a terminal session.
In this repository10 other files it gives its agents.
- boring-videoSkill
- develop-topicSkill
- setup-boring-video-skillsSkill
- to-articleSkill
- to-narrationSkill
- to-scenesSkill
- to-spec-beatsSkill
- to-storyboardSkill
- to-videoSkill
- verysmallwoods-videoSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 20
When no terminal style is specified, use the classic iTerm-like default in references/terminal-visual-style.md.
≈ “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.
Files
Record terminal
Recreate a real terminal run in HyperFrames. The terminal is an application replay, not a terminal-shaped text animation.
REQUIRED REFERENCE: Read
references/terminal-presentation.md
before planning or capturing the shot. Complete its runbook and capture gates
before following its pointer to ledger construction and HyperFrames replay.
User-provided terminal, shell, brand, font, or accessibility requirements replace the default styling as a coherent visual system. The evidence, event-order, prompt, and seek-safety contract remains unchanged.
When no terminal style is specified, use the classic iTerm-like default in
references/terminal-visual-style.md.
Registry components may implement that profile, but do not replace it with a
different visual treatment merely because a component exists.
Real screen-recorded footage is a separate branch. Use it only when the user explicitly requests captured footage; otherwise produce the evidence-backed HyperFrames replay.
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
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.