agentleFS
Sign inStart free
bloxy-studiosbloxy-studios/shorts-studio/skills/doctor/SKILL.md

doctor

Skill0 starsChanged 42 days agoMITView on GitHub

Check and repair the Shorts Studio runtime — FFmpeg features, Bun/Node, the project-local Python environment, whisper.cpp and models, pinned HyperFrames + Chrome, fonts, disk space and CPU/architecture compatibility (Intel or Apple Silicon). Use when setup fails, before a first edit, or when the user asks whether the plugin is ready.

  • Installs packages

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall, cancel and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 6 projects that use this

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • ibahgatSkill

    mode

    Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.

    Also in 3 projects that use this

  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 3 projects that use this

  • QinghongLinSkill

    editor

    Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Run "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" doctor and read every ✗ (required) and ○ (optional) line.

    line 31
  2. Very specific:

    If required items are missing, run "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" doctor --setup.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “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

Doctor

Rules: ${CLAUDE_PLUGIN_ROOT}/references/rules.md.

0. Engine check

The commands below run the Shorts Studio engine. Installed as the Claude Code plugin it is already present and shorts-studio is on the Bash PATH. If shorts-studio doctor is not found (for example, this skill was added with npx skills add), ask the user before installing anything, then:

  • Claude Code: /plugin marketplace add bloxy-studios/shorts-studio → /plugin install shorts-studio@shorts-studio.
  • Other agents: git clone --depth 1 https://github.com/bloxy-studios/shorts-studio ~/.shorts-studio/engine and read every ${CLAUDE_PLUGIN_ROOT} path below as ~/.shorts-studio/engine.

Then run shorts-studio doctor --setup once (project-local runtime; never sudo or global installs).

Steps

  1. Run "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" doctor and read every ✗ (required) and ○ (optional) line.
  2. If required items are missing, run "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" doctor --setup. It installs only into the plugin's runtime directory (uv-managed Python 3.12 venv, pinned HyperFrames 0.8.97 + gsap, pinned chrome-headless-shell, a static whisper.cpp build, and checksummed models). It never uses sudo, npm -g, or global pip. Tell the user what was installed and roughly how much disk it used.
  3. Optional models: --setup --models whisper-small.en (better English captions, ~488 MB), whisper-small (multilingual incl. Kiswahili, ~488 MB). Ask before downloading optional models on a slow or metered connection.
  4. System prerequisites that setup cannot install (FFmpeg, Node ≥ 22, Bun, uv, cmake/Xcode command line tools): explain the fix (e.g. brew install ffmpeg) and stop.

Known limits

  • FFmpeg builds without zscale cannot do proper HDR→SDR tone mapping; HDR sources use the documented fallback (docs/COLOR.md) and the report says so.
  • CPU-only machines are supported; HyperFrames renders are slow on Intel (~1–3 fps at 1080×1920), which the pipeline accounts for.

Completion check

doctor ends with "ready: all required checks pass", or you reported each remaining required item and the exact command or install the user must run.

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.

Check your setup, free