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

stackify

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

Quality

63%

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/stackify/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 CLI commands and a clear connect-to-run workflow, but it carries some marketing fluff, a broken step-numbering scheme (references to a nonexistent Step 2), and only an implicit error-recovery path. Some inlined reference material (clientAction schema, options table) could be split into a bundled reference file.

Suggestions

Fix the step numbering: either add an explicit "Step 1 / Step 2" structure or remove the dangling "skip to Step 2" and "1b" labels.

Trim marketing phrasing (e.g. "so you can focus on the integration logic rather than auth plumbing") to keep the body lean.

Add an explicit error-recovery feedback loop for CONFIGURATION_ERROR/SETUP_FAILED (check error field -> remediate -> re-run ensure) instead of the one-line "check the error field" note.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (terse commands plus a compact options table), but marketing-style padding like "so you can focus on the integration logic rather than auth plumbing" and explanatory asides ("This is the fastest way to get a connection...") could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready, executable commands with flags throughout (connection ensure, action list/run, request with a full flag table), covering the common cases with only minor placeholders (CONNECTION_ID) the user must substitute.	4 / 5
Workflow Clarity	A clear connect -> poll-state -> search -> run sequence exists with state-based branching, but step numbering is broken ("skip to Step 2" with no Step 2, a "1b" with no 1a) and error recovery is a bare "check the error field" rather than an explicit fix-and-retry feedback loop.	3 / 5
Progressive Disclosure	Sections are well-organized (Install, Authentication, Connecting, Searching, Popular actions, Best practices) for a single-file skill, though the inlined clientAction schema and request-options table are bulk that a reference file could carry; no bundle files exist, so structure alone drives the score.	4 / 5
	Total	14 / 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 clearly identifies the Stackify niche and includes an explicit use-when clause, but its capability list is generic ("manage data, records, automate workflows") rather than reflecting Stackify's actual surface (error tracking, metrics, transactions). Trigger terms lean on the product name alone without the natural monitoring/APM vocabulary users would say.

Suggestions

Replace generic actions with Stackify-specific ones, e.g. "Query error groups, errors, metrics, transactions, and servers; automate monitoring workflows."

Expand the use-when clause to mirror natural phrasing: "Use when the user wants to investigate errors, view metrics, monitor servers, or automate Stackify workflows."

Mention file formats or signal keywords (APM, error tracking, logs) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Stackify domain plus a couple of actions, but the actions are generic rather than the concrete capabilities the integration actually exposes (errors, metrics, transactions, servers), so it is not comprehensive.	3 / 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 Stackify data"), but the "what" is vague and the "when" could be more specific about which tasks trigger it.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Stackify data" surfaces the product name and "data", but it omits the natural terms a user would actually say (error tracking, monitoring, metrics, logs, APM), leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	"Stackify integration" names a specific product with a clear niche trigger ("interact with Stackify data"), making it highly distinguishable and very unlikely to fire for the wrong skill.	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/stackify/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.