Slopcamera

Tutorials

Set up Slopcamera for Codex

Install the verified release and the Agent Skill so Codex can create visual media in a repository.

Codex can create diagrams, images, animations, and video through Slopcamera once two pieces are installed: the slopcamera command, which does the local media work, and the Slopcamera Agent Skill, which teaches Codex which operation to reach for.

You need Bun 1.3.14 or newer. Recording features need macOS; everything else runs on macOS, Linux, and Windows. No Slopcamera account exists, and nothing here asks for one.

Install the CLI

bun add --global https://github.com/hraness/slopcamera/releases/download/v3.2.6/hraness-slopcamera-3.2.6.tgz

Confirm the install:

slopcamera doctor --json

The doctor reports which parts of the multimedia engine are available on this machine. Diagram and video editing always are; native engines such as Blender install separately.

Install the Agent Skill for Codex

slopcamera skill install --target codex

Codex is the default target, so slopcamera skill install without --target does the same thing. A user-scope install writes ~/.codex/skills/slopcamera, which every Codex session can read. To keep the skill inside one repository, run this at its root instead:

slopcamera skill install --target codex --scope project

That writes .codex/skills/slopcamera in the repository. Pass --project <directory> to name a different root without changing directories, or --force to replace an existing install. The Codex target ships the same SKILL.md and task references as every other target, plus an agents/openai.yaml interface file whose default prompt invokes $slopcamera.

Start a new Codex session after installing. The skill loads version-matched guidance for choosing creative operations, so Codex knows to check a diagram before rendering it, to preview a cut before exporting it, and to keep sources editable.

Try it

Ask Codex in a fresh session:

Create a two-box diagram showing ingestion flowing into review, render it, and show me the dark PNG.

Codex should run slopcamera diagram init, edit the JSON source, run slopcamera diagram check --strict, then slopcamera diagram render, and open or report the resulting files. If it improvises with another tool instead, the skill did not load; start a new session or re-run the install.

What Codex can do next

  • Generate images, video clips, and narration through your own Vercel AI Gateway credential; see generate media.
  • Edit footage and deliver multiple aspect ratios; see edit video.
  • Direct spatial scenes and native films on a source build; see spatial scenes and native films.
  • Give Codex's MCP support the fixed diagram and image toolset instead of the skill; see MCP clients.

Troubleshooting

  • slopcamera: command not found: the global Bun bin directory is not on your PATH, or the install ran in a different shell. Re-open the terminal and re-run slopcamera doctor --json.
  • The skill is not loading: skills install per target. The Codex form installs to a .codex/skills directory; --target agents is the generic convention and --target claude is Claude Code. Re-run the command above, not a different target, then start a new session.
  • Install reports a legacy diagram skill: remove or move the old diagram directory inside the target's skills root, then re-run the install. Slopcamera will not place both skills side by side.
  • Generation asks for a key: model-backed operations use caller-owned Vercel AI Gateway access. Set AI_GATEWAY_API_KEY, or with a linked Vercel project use vercel env run -- <command> so the credential is injected for one command without being written to the project. This website never receives it.