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

validate

Skill0 starsChanged 47 days agoApache-2.0View on GitHub

Validate a video-studio VideoSpec (video-spec.json) against the schema and semantic rules, and explain each error with a concrete fix. Use when the user runs /video-studio:validate, after writing or editing a spec, or before rendering.

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use policy-init, close and 8 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.
  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 4 projects that use this

  • Hugging FaceSkill

    sprint

    Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.

    Also in 4 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    board

    Read, write, and browse the AgentHub message board for agent coordination.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user gave no path, use the current working directory as project_dir.

    line 17
  2. Distinctive:

    Always pass absolute paths.

    line 18
  3. Very specific:

    If ok is true, say so in one line and mention any warnings briefly.

    line 20
  4. Very specific:

    If ok is false, list each error as path: message and propose the fix.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 53 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

Validate a VideoSpec

  1. Work out what to validate:
    • A project folder (contains project/project.json): pass project_dir. The tool reads project/video-spec.json and cross-checks source/content-ir.json if present.
    • A single spec file: pass spec_path, plus content_ir_path if the user has a ContentIR to check evidence refs against.
    • If the user gave no path, use the current working directory as project_dir. Always pass absolute paths.
  2. Call mcp__plugin_video-studio_engine__spec_validate.
  3. If ok is true, say so in one line and mention any warnings briefly.
  4. If ok is false, list each error as path: message and propose the fix. Stages mean:
    • syntax: the file is not valid JSON/YAML.
    • schema: a field is missing, mistyped or out of range. Call mcp__plugin_video-studio_engine__schema_get with name: "video-spec" if you need the exact field definitions.
    • semantic: cross-field rules, such as scene durations summing to within 10% of target_duration_sec, unique scene ids, motion_graphic scenes needing deterministic props, no provider or model names in visual_requirements, and evidence refs that exist in the ContentIR.
  5. Offer to apply the fixes. If the user agrees, edit the spec, then validate again until it passes.

Scenes declare capabilities, never provider or model names; routing picks the provider.

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