Name: frameio
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

frameio

Frame.io integration. Manage Projects, Teams. Use when the user wants to interact with Frame.io data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/frameio/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, copy-paste Membrane CLI commands and a clear connection workflow that includes state-based polling feedback loops. It loses points for an unnecessary product-intro paragraph, missing validation guidance around destructive actions, and an all-inline structure with no reference files for the bulky action and flag tables.

Suggestions

Trim the opening product-description paragraph; Claude does not need Frame.io explained, so start directly with the integration/CLI setup.

Add a pre-check or confirmation guidance for destructive actions (e.g. delete-asset) — such as confirming the asset id and listing children before deletion — to strengthen workflow validation.

Move the popular-actions table and proxy flag table into reference files (e.g. references/actions.md, references/proxy.md) and link them from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with CLI-specific commands Claude would not already know, but it opens with a paragraph explaining what Frame.io is ("cloud-based video collaboration platform... filmmakers and video editors") and includes light prose padding, fitting the mostly-efficient-but-could-be-tightened anchor rather than the lean 4-anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands with real flags across the full flow (`npm install -g @membranehq/cli@latest`, `membrane connection ensure --json`, `membrane action run --input`, `membrane request`), covering install, auth, connect, search, run, and proxy — matching the fully-executable-comprehensive anchor.	5 / 5
Workflow Clarity	Clear sequenced flow (install → auth → connect → search → run) with state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and `--wait` polling), but lacks explicit pre-validation guidance around destructive actions like delete-asset, fitting the clear-sequence-with-minor-validation-gaps anchor rather than the explicit-validation 5-anchor.	4 / 5
Progressive Disclosure	No bundle files exist; all content lives inline in a single ~150-line file with good section headers, but the 16-row popular-actions table and the proxy flag table are inline reference material that could be split into separate files, fitting the some-structure-could-be-better-organized anchor.	3 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and correctly pairs a what-statement with an explicit Use-when trigger, anchored to the distinct Frame.io brand. It is held back by the generic verb "Manage" and limited keyword/synonym coverage, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Manage Projects, Teams, Review Links, and assets; create comments and folders."

Broaden trigger terms with natural phrasings users might say, e.g. "Use when the user wants to interact with Frame.io data — review links, comments, projects, teams, or assets."

Dimension	Reasoning	Score
Specificity	Names the domain ("Frame.io") and a couple of entity-level actions ("Manage Projects, Teams"), but "Manage" is generic and coverage is not comprehensive — matching the domain-plus-1-2-actions anchor rather than the 4-anchor's several specific actions.	3 / 5
Completeness	Explicitly answers both what ("Frame.io integration. Manage Projects, Teams.") and when ("Use when the user wants to interact with Frame.io data"), with the when clause present but slightly generic — matching the both-present-but-could-be-more-specific anchor rather than the 5-anchor's concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant natural keywords ("Frame.io", "Projects", "Teams", "interact with Frame.io data") but lacks synonyms or common variations a user might phrase differently, fitting the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	Frame.io is a distinct branded niche with minimal conflict risk, but the generic "Manage Projects, Teams" entity wording carries minor overlap risk with closely related collaboration/project skills, fitting the mostly-distinct anchor rather than the fully-distinct 5-anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/frameio/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.