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

export

Skill0 starsChanged 42 days agoMITView on GitHub

Validate and package finished shorts: H.264 1080×1920 MP4s, previews, cover images, SRT/VTT/word JSON, the EditPlan, stems, source provenance, QA and editing reports, a manifest with checksums — to a local folder, or to an explicitly requested destination that has a working connector.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use menu, import and 6 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.
  • sasly2048Skill

    menu

    Point the user to cc-atlas's full interactive menu (dashboard, project comparison, session replay, team activity, anomalies, goals) — screens that need a real terminal.

    Also in 3 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 3 projects that use this

  • AnthropicSkill

    search

    Search across all connected sources in one query. Trigger with "find that doc about...", "what did we decide on...", "where was the conversation about...", or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker.

    Also in 4 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 4 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    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:

    Prefer approved renders (ss approve <project> --clip <id> --render rNNN).

    line 33
  2. Very specific:

    Default destination: exports/<date>-<project>/<clip>/ in the workspace.

    line 35
  3. Very specific:

    Read the manifest; report every file and the QA verdict per clip.

    line 39

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

Export

Rules: ${CLAUDE_PLUGIN_ROOT}/references/rules.md · CLI: ${CLAUDE_PLUGIN_ROOT}/references/cli.md. ss = "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio". Input: $ARGUMENTS

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. Prefer approved renders (ss approve <project> --clip <id> --render rNNN); --approved-only exports only those.
  2. ss export <project> [--clips a,b] [--approved-only] [--stems] [--dest local:DIR]. Default destination: exports/<date>-<project>/<clip>/ in the workspace.
  3. Remote destinations: only the one the user named, and only through an available connector (--dest drive:FOLDER fails clearly without one). Never upload raw source footage unless asked. Never publish/post.
  4. Read the manifest; report every file and the QA verdict per clip. A clip whose QA is blocked/draft is exported only if the user asked, and labelled as such.

Completion check

The manifest lists each clip's MP4 (+ checksum), preview, cover, subtitles, plan, report and QA; the delivered MP4's QA spec check passed; destinations other than local were explicitly requested.

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