Skip to main content
Glama

pr_skill

Load Premiere Pro task guidance: get the router for workflow order, script limits, and references, or read one reference on AI tools, multi-tool recipes, and gotchas.

Instructions

The Premiere agent skill. No doc: the router — order of work, what scripts cannot do in Premiere, which reference to read; read it at the start of any Premiere task beyond a single read or edit. doc: one reference — Premiere's AI tools (Generative Extend, Generative Media Tool, Object Mask, transcripts and Paper Edit, captions, Enhance Speech/Audio, Search, AI Assistant, Auto Reframe, Scene Edit Detection, Morph Cut), multi-tool recipes, gotchas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pr_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
docNoreference: audio | combos | generative | gotchas | layer-conform | masking | search-assistant | speech-text | timeline-automation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / doc / description
      Previous value: -"reference: audio | combos | generative | gotchas | masking | search-assistant | speech-text | timeline-automation"New value: +"reference: audio | combos | generative | gotchas | layer-conform | masking | search-assistant | speech-text | timeline-automation"
  2. Changed1 schema field changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It explains what content the router and references cover, but does not state whether the tool is read-only, whether it modifies anything, or what the return format and size are.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and mostly front-loaded, but the 'No `doc`: the router' construction is syntactically awkward and the long parenthetical AI-tool list makes it harder to scan. It is informative without much filler, but the structure could be clearer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter retrieval tool with no output schema, the description covers what each mode returns conceptually. However, with no annotations and no output schema, it should ideally state the return format and explicitly confirm that it does not modify the Premiere project.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds meaning beyond the enum-like doc field: omitting doc returns the router, while supplying doc returns exactly one reference. It also maps reference categories to concrete content such as AI tools, recipes, and gotchas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly establishes that this tool retrieves a Premiere agent skill, with distinct modes for the router (no doc) and one named reference (doc). It is specific about the resource and mode behavior, but does not explicitly differentiate it from sibling tools such as pr_do or pr_catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete when-to-use rule: read it at the start of any Premiere task beyond a single read or edit. It also explains the no-doc router versus doc reference choice, though it does not name sibling tools or state when another pr_* tool should be used instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.