Agent Skills - Framelane

What are Agent Skills?

Agent Skills are written guides for common Framelane jobs, such as a launch teaser, a talking-head cleanup or captioned shorts. Each one walks an agent through the job end to end with Framelane’s MCP tools: what to ask, what to build, how to check the result on frames the server renders, and how to hand the project over. They come in two kinds. A workflow carries one job from brief to delivery. A reference is read beside a workflow: the handbook, which every workflow builds on, and the style library. Shared craft modules on color, type, motion, layout, delivery and speech editing sit beside the skills, and each skill names the modules it relies on.

Skill	Kind	Bundle folder	What it covers
`handbook`	reference	`framelane`	The shared contract: the project loop, previews, review, handoff and export
`brief-to-video`	workflow	`framelane-brief-to-video`	A narrated video assembled from a written brief and the user’s own media
`caption`	workflow	`framelane-caption`	Timed captions from a real transcript
`explainer`	workflow	`framelane-explainer`	A motion-graphics explainer built from text, shapes and simple diagrams
`localize`	workflow	`framelane-localize`	A translated locale variant of an existing project
`onboard`	workflow	`framelane-onboard`	A tour of the workflows and a real, editable sample project
`reframe`	workflow	`framelane-reframe`	Faithful versions of a project for another aspect ratio
`review`	workflow	`framelane-review`	A check of server frames and lint, with targeted repairs when asked
`shorts`	workflow	`framelane-shorts`	Captioned vertical clips cut from a long recording
`styles`	reference	`framelane-styles`	Named visual styles, from dark keynote to silent film
`talking-head`	workflow	`framelane-talking-head`	A talking-head recording cleaned up, with titles, captions and B-roll
`teaser`	workflow	`framelane-teaser`	A short branded launch teaser

The skills use the open agent-skills format: a folder per skill, holding a SKILL.md whose frontmatter names the skill and says when to use it. The MCP server serves each skill under its own name. The installable bundle prefixes the names (the bundle folder above), because installed skills share a folder with every other skill on the machine.

Install the skills bundle

The bundle is published to the public GitHub repository ITIShq/framelane-skills once the production API serves the same skills. Each skill folder in it carries the craft modules it cites, copied into its references/craft/ folder. Where a skill names another as skills.<name>, that is the framelane-<name> folder (the handbook is framelane). Claude Code. Add the repository as a plugin marketplace, then install the plugin:

/plugin marketplace add ITIShq/framelane-skills
/plugin install framelane@framelane

The plugin installs the skills and adds the MCP server. Other agents. npx skills add ITIShq/framelane-skills installs the skills for the agents you pick, in the current project or, with -g, for your user. To install by hand, copy the folders under skills/ into ~/.codex/skills (Codex), ~/.cursor/skills (Cursor) or ~/.agents/skills. Voyager lists the skills it finds in ~/.claude/skills, ~/.codex/skills, ~/.agents/skills and ~/.cursor/skills. It does not read Claude Code’s plugin cache, so install with the skills CLI or copy the folders. Then connect the MCP server at https://mcp.framelane.io/mcp and sign in. With the Claude Code plugin the server is already configured: run /mcp, choose framelane and sign in. For other hosts, and for access with an API key, see Connecting.

MCP prompts

The MCP server publishes each workflow skill as a prompt with the skill’s name, such as teaser or talking-head. A prompt takes an optional brief argument, which is appended to the skill as the user’s brief. One more prompt, framelane, returns the handbook followed by an index of the workflows. Reference skills are not prompts; read them as sections.

`get_capabilities` sections

Hosts that do not show prompts read the same text through the get_capabilities tool:

Section	Returns
`skills`	One row per skill: name, description, kind, verification and sha256
`skills.<name>`	One skill’s full text, such as `skills.handbook`
`craft.<id>`	A shared craft module, such as `craft.typography`
`references.<skill>.<name>`	A file a skill refers to, such as the style guide `references.styles.swiss-motion`

Calling get_capabilities with no argument returns the index, which lists each of these sections with its size. Without an MCP client, GET https://api.framelane.io/v1/skills lists the skills and GET https://api.framelane.io/v1/skills/{name} returns one as markdown — no key required.

Capabilities

Before authoring anything, read GET https://api.framelane.io/v1/capabilities — no key required. It is derived from the same enums and models the API validates against, so it cannot drift: motions[] flags every preset with the surface it works on (element_entrance, element_exit, character, text_block), effects / transitions / blend_modes / easings list the full catalogs with a supported flag, element_schemas gives the per-element JSON Schema, and request_schema gives the composition level — groups, custom animations, motion blur, background gradient, transitions. MCP clients get the same document from the get_capabilities tool — call it with no argument for a small index of every section and its size, then section='request_schema' for the composition body and section='element_schemas.text' (or .video, .image, .shape, .audio) for one element type’s fields. See the MCP server page for the full tool list.

Guides

How-tos for the REST API are in the Guides: Author a video, Measure a reference, Render Video, Transcribe, Generate Social Clip, Batch Tasks and Webhook Setup.

​What are Agent Skills?

​Install the skills bundle

​MCP prompts

​get_capabilities sections

​Capabilities

​Guides