CtrlK
BlogDocsLog inGet started
Tessl Logo

stacks

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/stacks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with executable commands and a well-validated connection workflow. It is mostly concise and well-structured, with only minor padding and a small redundancy between the action-discovery sections.

DimensionReasoningScore

Conciseness

The body is mostly tight, command-driven content; minor trimmable padding appears in the intro paragraph, the Stacks Overview hierarchy, and the filler line "Use action names and parameters as needed."

4 / 5

Actionability

It provides copy-paste-ready executable commands for install, auth, connection ensure, state polling, action list/run, and proxy requests, plus a concrete flags table covering the common cases.

5 / 5

Workflow Clarity

The connection flow is a clear sequence with an explicit validation feedback loop (poll to READY, handle CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR); the minor gap is no post-run verification for potentially destructive actions or proxy mutations.

4 / 5

Progressive Disclosure

With no bundle files present, the single-file content is organized into clear, navigable sections; the only organization gap is mild redundancy between "Searching for actions" and "Popular actions".

4 / 5

Total

17

/

20

Passed

Description

57%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 pairs a what-statement with an explicit Use-when trigger and leans on a distinct platform name, but its capability verbs are generic. Replacing abstract actions with concrete Stacks operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with 2-3 concrete Stacks operations such as searching records, creating/updating Stacks entries, or triggering workflows.

Broaden trigger terms beyond the product name, e.g. "Use when the user wants to search, create, or update Stacks records or run Stacks workflows".

Tighten the when-clause to name the user intents (querying data, automating workflows) rather than the broad "interact with Stacks data".

DimensionReasoningScore

Specificity

It names the Stacks domain but the listed actions ("Manage data, records, and automate workflows") are generic rather than concrete, matching the anchor for naming a domain with minimal/generic actions.

2 / 5

Completeness

It states a "what" (manage data/records, automate workflows) and an explicit "Use when the user wants to interact with Stacks data" trigger; the when-clause is present but could be more specific, matching the both-present anchor.

4 / 5

Trigger Term Quality

"Stacks" and "interact with Stacks data" are relevant natural keywords, but coverage is thin with no synonyms or variations beyond the product name.

3 / 5

Distinctiveness Conflict Risk

"Stacks" is a specific named platform giving a distinct niche and low conflict risk, though the generic "manage data, records" phrasing leaves minor overlap with broad data skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.