shotkit

You describe a video (brief, duration, aspect ratio) and can add a brand lock, a markdown file fixing palette, type and voice, which brand-lock-extractor can build from a site, PDF or screenshots; without one the skills fall back to a flagged template. storyboard-architect writes run.json, storyboard.md, shots.json and a separate on-screen text spec, visual-prompt-forge writes copy-paste prompts for six image and four video generators, and storyboard-html-preview builds one shareable page. After you generate frames elsewhere, visual-asset-critic checks each against its shot spec and brand lock, and the prompts are re-written only for shots marked for revision, with content hashes recorded so later changes can be detected. It stops at specs and prompts: it calls no generator APIs and renders no video.

• 01From the README

  The install command quoted from the repository README.

  $ git clone https://github.com/whystrohm/shotkit.git cd shotkit && ./install.shCopy

• 02skills CLI, for Claude Code, Codex and others

  The open skills CLI from Vercel Labs installs a skill from a GitHub repo into the folder each agent expects. It asks which skills and which agents you want, and it installs for the current project unless you add the -g flag, which installs for your user account. Add --list to see what a repo contains before you install anything.

  $ npx skills add whystrohm/shotkitCopy

• 03Claude Code, skills folder

  Copy the skill's folder, the one that holds SKILL.md, into ~/.claude/skills/ to use it in every project on your machine, or into .claude/skills/ in a repository to use it there and share it by committing it. Claude Code picks up changes to these folders during a session. If the folder did not exist when the session started, run /reload-skills.

• 04Claude Code, plugin marketplace

  Some repos publish a plugin marketplace, a .claude-plugin/marketplace.json file. Add it in Claude Code, then install a plugin from it with /plugin install plugin-name@marketplace-name. Plugins can bundle hooks and MCP servers along with skills, so read the details panel before you confirm.

  $ /plugin marketplace add whystrohm/shotkitCopy

• 05Codex, skills folder or $skill-installer

  Codex reads skills from .agents/skills in your working folder and its parent folders up to the repository root, and from $HOME/.agents/skills for every repository. Copy the skill's folder into one of them, or run $skill-installer inside Codex and ask it to install from the repo. Codex detects new skills automatically and needs a restart only if one does not appear.

The first command is quoted from the author's README. The others are the standard ways to install a skill from a GitHub repository. They are templates and may not apply here, for example if the repo has no plugin marketplace, so follow the README first.