Skip to content
Back to skills

Cli Recorder

ASecurity

Use when authoring a CLI session recording for the cli-recorder skill. Translates a user's intent ("video of installing kubectl") into a valid recipe.toml through interactive Q&A.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 10, 2026
ai-agentsgogit

Works with

  • cli

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned June 10, 2026

npx -y skills add marsmike/feinschmiede --skill cli-recorder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cli Recorder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cli Recorder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/marsmike-cli-recorder/badge)](https://www.skillsdirectory.com/skills/marsmike-cli-recorder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cli-recorder
description: Use when authoring a CLI session recording for the cli-recorder skill. Translates a user's intent ("video of installing kubectl") into a valid recipe.toml through interactive Q&A.
---

# CLI Recorder — Recipe Author

Help users turn an idea ("a video of installing kubectl on macOS", "a tour of git rebase -i") into a valid `recipe.toml` for the `feinschnitt record` command.

## When to use

- User says "create a recording for X" / "record a demo of Y" / "let's make a video of Z"
- User invokes `/record` or otherwise references this skill
- User has a finished video idea but no recipe file yet

## Hard gate

Do NOT run the recorder. Do NOT scaffold the surrounding Remotion video. Stop after the recipe is written and validated. The user runs `feinschnitt record` themselves once they're happy.

## Process

```
1. Discover intent           → What CLI? What's the audience? What's the takeaway?
2. Pick a profile            → claude-code | generic | interactive-tui
3. Sketch the steps          → 3-9 beats; each beat ≈ one screen of action
4. Resolve modal/interactive → which steps need dismiss keys, pattern waits, pauses
5. Tune cadence              → typing_wpm, idle compression, idle_time_limit
6. Write the recipe          → ${CLAUDE_PROJECT_DIR}/.recordings/recipes/<name>.recipe.toml
7. Show + validate           → display the file; offer a dry-run for verification
```

Apply **one question at a time** — prefer multiple choice over open-ended. The
storyboard is the step labels; sketch those before the `text` content. Validate
the written recipe against `schema/recipe.schema.json` before declaring done.

See [`references/steps.md`](references/steps.md) for the full per-step
procedure, anti-patterns, and examples of good step labels.

## See also

- [`references/steps.md`](references/steps.md) — per-step detail, anti-patterns, label examples
- `schema/recipe.schema.json` — full validation surface
- `profiles/*.toml` — what each profile presets
- `README.md` — recorder overview

Files in this skill

  • README.md3.5 KB
  • SKILL.md2 KB
  • profiles/claude-code.toml1.3 KB
  • profiles/generic.toml763 B
  • profiles/interactive-tui.toml974 B
  • recipes/claude-commands.recipe.toml1.8 KB
  • recipes/claude-first-session.recipe.toml3 KB
  • recipes/claude-start-stop.recipe.toml2.2 KB
  • references/steps.md5.2 KB
  • schema/recipe.schema.json5.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.