agentleFS
Sign inStart free
harshil-1411harshil-1411/claude_plugin_video_studio/skills/doctor/SKILL.md

doctor

Skill0 starsChanged 48 days agoApache-2.0View on GitHub

Check whether this machine is ready to make videos with video-studio. Reports Node, node:sqlite, ffmpeg/ffprobe (libass, libx264), Chrome, the optional HyperFrames renderer, whisper.cpp, configured provider keys and the data directory, with a fix for each problem. Use when the user runs /video-studio:doctor, asks if their setup works, or a render fails for environment reasons.

  • 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

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

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 2

    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:

    Call the MCP tool mcp__plugin_video-studio_engine__doctor with no arguments.

    line 11
  2. Very specific:

    If the tool is not available, tell the user the engine MCP server did not start: check that Node.js 22.13+ is on PATH, then run /mcp to see …

    line 12
  3. Distinctive:

    Only warnings: local rendering works, with the listed features limited.

    line 21
  4. Distinctive:

    Do not try to install anything yourself unless the user asks.

    line 34

“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

Environment doctor

  1. Call the MCP tool mcp__plugin_video-studio_engine__doctor with no arguments. If the tool is not available, tell the user the engine MCP server did not start: check that Node.js 22.13+ is on PATH, then run /mcp to see the server's error, and /reload-plugins after fixing it. Stop there.
  2. Present the result as a short table: one row per check with its status (ok / warn / fail) and the detail. Keep ok rows terse.
  3. Below the table, list every fail and then every warn check with its fix, written as concrete commands for the user's platform (platform in the result).
  4. Summarize readiness in one sentence:
    • fail on node, sqlite, ffmpeg, ffprobe or data_dir: video-studio cannot render yet.
    • Only warnings: local rendering works, with the listed features limited.
    • All ok: ready.

Rules:

  • Provider keys are reported as present/missing only. Never ask the user to paste a key into the chat. To add keys, point them to /plugin → video-studio → Configure, where keys are stored in the OS credential store.
  • Missing provider keys are not errors; local and mock paths need no keys.
  • Chrome, hyperframes and whisper.cpp are optional: without HyperFrames the ffmpeg renderer draws every motion-graphic scene. If the user wants HyperFrames, give them the command from the hyperframes fix (cd "${CLAUDE_PLUGIN_DATA}" && PUPPETEER_SKIP_DOWNLOAD=1 npm i @hyperframes/producer@0.8.78 --prefix deps) to run themselves, then re-run the doctor.
  • Do not try to install anything yourself unless the user asks.

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