Name: stackery
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

stackery

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

Quality

64%

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/stackery/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 content delivers concrete, executable Membrane/Stackery commands with a clear connection workflow and explicit state-based checkpoints. It is somewhat over-explanatory in places and long enough that some reference material could be split out, but it is well-structured and actionable overall.

Suggestions

Trim the introductory paragraph explaining what Stackery is and remove filler lines like 'Use action names and parameters as needed.'

Label the workflow steps explicitly (Step 1 install/auth, Step 2 connect, Step 3 search/run) so the 'skip to Step 2' references resolve cleanly.

Move the large resource-type bullet catalog into a references file and link to it from the overview to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but it explains concepts Claude can infer (an intro paragraph on what Stackery is, what Membrane handles) and includes filler like 'Use action names and parameters as needed', fitting 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) with a flags table and clearly marked placeholders, fitting 'mostly executable guidance; concrete code or commands with minor gaps' rather than fully filled examples at 5.	4 / 5
Workflow Clarity	The connect→poll→search→run sequence has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but 'Step 2' is referenced without a cleanly labeled Step 1, leaving minor navigation gaps that keep it below the fully polished anchor of 5.	4 / 5
Progressive Disclosure	Sections are well-organized with no nested references, but at ~155 lines the resource-type catalog and proxy/API detail could be split into a reference file; this fits 'good structure; most content appropriately placed; minor organization gaps.'	4 / 5
	Total	15 / 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 correctly identifies a distinct product niche and provides an explicit 'Use when' trigger, but its capability statement is generic ('Manage data, records, and automate workflows') rather than naming concrete Stackery actions. Trigger-term coverage is narrow, relying almost entirely on the single keyword 'Stackery'.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Stackery actions (e.g., 'Deploy and manage serverless stacks, environments, and resources').

Broaden trigger terms to include natural variations a user might say, such as 'serverless stacks', 'Stackery stacks', 'Stackery environments', or 'Stackery deployments'.

Tighten the when-clause to reference specific intents like 'creating or modifying Stackery stacks and resources'.

Dimension	Reasoning	Score
Specificity	The description names the Stackery domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete Stackery operations, matching the 'names domain but actions minimal or generic' anchor and falling below the concrete-action anchor of 3.	2 / 5
Completeness	It states both a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Stackery data'), satisfying the both-present anchor; the when is explicit though the what is generic, so it does not reach the fully concrete anchor of 5.	4 / 5
Trigger Term Quality	The natural trigger term 'Stackery' (and 'Stackery data') is present, but coverage lacks synonyms, variations, or file extensions, fitting 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	Stackery is a named platform with a distinct, product-specific trigger ('interact with Stackery data'), giving it a clear niche with minimal conflict risk against other skills.	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/stackery/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.