Name: motion
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

motion

Motion integration. Manage Workspaces. Use when the user wants to interact with Motion data.

Quality

71%

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/motion/SKILL.md

Quality

Content

81%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 content is well-structured, highly actionable, and features a clearly sequenced connection workflow with explicit validation checkpoints. Minor trimming of marketing prose and resolving abstract placeholders would push it higher.

Suggestions

Trim the marketing-style opening paragraph ("primarily used by project managers, team leads, and executives...") to tighten conciseness.

Replace abstract placeholders (CONNECTION_ID, QUERY) with a concrete worked example showing a real intent and resolved connection id.

Resolve the "Step 2" reference: it is mentioned ("skip to Step 2") but no Step 2 section is defined, leaving a dangling navigation pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and assumes Claude's competence, but retains minor over-explanation like the marketing-style intro ("primarily used by project managers, team leads...") and the entity bullet list with no payoff, fitting the score-4 anchor.	4 / 5
Actionability	Concrete copy-paste-ready membrane CLI commands with flags and JSON examples cover the common cases, but placeholders like CONNECTION_ID and QUERY intent are left abstract, placing it just below the fully-complete score-5 anchor.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops ("poll again... to check if state moved to READY"), matching the score-5 anchor; no destructive/batch cap applies.	5 / 5
Progressive Disclosure	A single self-contained file with well-organized sections and clear headers, easy to navigate; it scores just below 5 because at ~157 lines some reference material (e.g., the proxy options table) could optionally live in a side file, but no nested or buried references exist.	4 / 5
	Total	17 / 20 Passed

Description

61%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 identifies a clear niche (Motion) with an explicit Use-when clause and minimal conflict risk, but its capability list is thin and generic. Strengthening the action inventory and trigger synonyms would lift the lower dimensions.

Suggestions

Replace the generic "Manage Workspaces" with 2-3 concrete actions (e.g., manage tasks, schedule meetings, query projects) to lift specificity.

Add natural trigger synonyms users would actually say ("Motion tasks", "Motion projects", "Motion scheduling") so trigger_term_quality reaches comprehensive coverage.

Make the when-clause more concrete by naming the objects users mention (tasks, projects, meetings) rather than the abstract "Motion data".

Dimension	Reasoning	Score
Specificity	"Manage Workspaces" is the only concrete action and it is minimal/generic, so it sits below the score-3 anchor that expects 1-2 concrete actions and above the score-1 entirely-vague anchor.	2 / 5
Completeness	It states both a what ("Motion integration. Manage Workspaces.") and an explicit when ("Use when the user wants to interact with Motion data"), but the when is generic rather than concretely triggered, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Motion data" provides one relevant trigger phrase but lacks common synonyms or natural variations, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Motion app with a dedicated trigger ("interact with Motion data") gives a clear niche with minimal overlap risk, matching the score-5 anchor; third-person voice is used so no specificity penalty applies.	5 / 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/motion/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.