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

shotstack

Shotstack integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Shotstack 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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 an actionable, well-structured Membrane-CLI integration guide with concrete commands and a clear connection-polling workflow, slightly held back by an unnecessary introductory explanation of what Shotstack is.

Suggestions

Trim the opening paragraph explaining what Shotstack is and who uses it; Claude already knows the product domain from the description.

Resolve the dangling 'Step 2' reference by either labeling the next section 'Step 2' or rewording the 'skip to Step 2' lines to point at a concrete section.

Add a short validation note for render/status actions (e.g., poll render status until complete before declaring success) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples with brief explanations, but it opens by explaining what Shotstack is ('an API platform that allows developers to programmatically create and edit videos... used by businesses and individuals') — background Claude does not need and could be trimmed.	3 / 5
Actionability	Provides concrete, copy-pasteable CLI commands for every phase (install, login, connection ensure/get, action list/run, request proxy) with flags and --json output; minor gaps such as an undefined 'Step 2' reference keep it just below fully executable everywhere.	4 / 5
Workflow Clarity	The connection flow is a clear sequenced workflow with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and an explicit feedback loop (poll again after the user acts); a 'Step 2' is referenced but never labeled as a section, a minor validation/organization gap.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; sections are well-organized and clearly signaled (Overview, Working with Shotstack, Popular actions, Best practices), with only minor organization gaps versus a perfectly navigable structure.	4 / 5
	Total	15 / 20 Passed

Description

66%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 has an explicit 'Use when...' trigger and a named product niche, but its listed capabilities (Deals, Persons, Pipelines) read like a generic CRM and do not match Shotstack's actual video-rendering domain, weakening specificity and trigger quality.

Suggestions

Replace the CRM-style object list (Deals, Persons, Pipelines) with Shotstack's real capabilities (e.g., create/edit videos, render timelines, manage assets and clips) to align the 'what' with the product.

Add natural trigger phrases users would say, such as 'create videos', 'render video', 'video editing', or 'automate video production'.

Tighten 'Manage ... and more' into concrete verbs (Create, Render, Edit, Poll render status) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Shotstack integration') and a concrete list of managed objects ('Manage Deals, Persons, Organizations, Leads, Projects, Pipelines'), but the trailing '& more' leaves coverage non-comprehensive and the named actions are generic 'Manage' rather than specific verbs.	3 / 5
Completeness	Explicitly answers both 'what' (manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more) and 'when' ('Use when the user wants to interact with Shotstack data'); the 'what' could be more concrete, keeping it just below a 5.	4 / 5
Trigger Term Quality	Includes the natural product name and the phrase 'Use when the user wants to interact with Shotstack data', but misses common variations a user would actually say such as 'create/edit videos', 'render video', or 'video production'.	3 / 5
Distinctiveness Conflict Risk	Anchored to a named product (Shotstack) with a distinct, product-specific trigger phrase, giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/shotstack/SKILL.md
Commit: f484c82

Reviewed: 4 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.