Name: shortcut
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

shortcut

Shortcut integration. Manage data, records, and automate workflows. Use when the user wants to interact with Shortcut data.

Quality

61%

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

Quality

Content

61%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 actionable and well-structured with concrete Membrane CLI commands, but it is dragged down by an unnecessary introductory explainer, a misleading keyboard-shortcut overview section, missing validation for destructive operations, and a confusing step reference. Tightening these would materially improve it.

Suggestions

Remove or replace the "Shortcut Overview" section describing keyboard shortcuts and the generic intro paragraph; keep only what Claude cannot infer about the Shortcut/Membrane integration.

Add explicit validation/verification steps before destructive proxy requests (POST/PUT/PATCH/DELETE) and after create/update actions — e.g. re-fetch the created story to confirm, or require a dry-run/--json preview for mutations.

Fix the broken "skip to Step 2" cross-reference by labeling the workflow steps explicitly (Step 1 connect, Step 2 search/discover, Step 3 run) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with copy-paste commands, but the opening paragraph explains what Shortcut is (concepts Claude largely knows), the "Shortcut Overview" section describes iOS-style keyboard shortcuts unrelated to the app, and filler like "When to use which actions: Use action names and parameters as needed" adds tokens without value (plus a corrupted "রোডmaps" typo).	3 / 5
Actionability	It provides concrete executable commands throughout (membrane login, connection ensure, action list/run, request) plus a Popular actions table with real keys and flags explained; minor gaps remain in that no end-to-end worked example shows a real action run with input and parsed output.	4 / 5
Workflow Clarity	A sequence exists (install → login → connection ensure → poll for READY → search/run), and the polling state machine acts as a checkpoint, but the "skip to Step 2" reference points to no clearly labeled Step 2, and destructive operations (proxy DELETE/PUT/PATCH, create/update actions) lack validation/verification steps, which caps this dimension at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested or buried references and an external docs link, but it is over 50 lines with no file split, so the simple-skill 5 does not apply.	4 / 5
	Total	14 / 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 functional with an explicit Use-when trigger and a named product, but its action verbs are generic and it omits high-value synonyms (Clubhouse) and concrete object names (stories, epics, iterations). It reads as adequate but not comprehensive.

Suggestions

Replace generic verbs with concrete Shortcut operations, e.g. "Create and update stories, epics, iterations, and projects".

Add the former name and key objects as triggers, e.g. "Use when the user wants to manage Shortcut (formerly Clubhouse) stories, epics, sprints, or iterations".

Tighten the 'when' clause to enumerate concrete triggers (stories, epics, iterations, labels) rather than the vague "interact with Shortcut data".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Shortcut integration") and lists action verbs ("Manage data, records, and automate workflows"), but these are generic operations rather than concrete Shortcut actions like creating stories or epics, fitting the anchor that names the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Shortcut data"), with an explicit trigger clause; the 'when' is present but somewhat narrow and the 'what' is generic rather than comprehensive.	4 / 5
Trigger Term Quality	"Shortcut data" and "interact with Shortcut data" provide a relevant keyword, but common variations and synonyms are missing — notably the former product name "Clubhouse" and concrete objects users mention (stories, epics, iterations/sprints).	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("Shortcut") gives it a clear niche with low conflict risk, but the word 'shortcut' is also a generic English term, leaving minor overlap ambiguity (compounded by the body's keyboard-shortcut framing).	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/shortcut/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.