Name: stockly
Rating: 61.6 (1 reviews)
Author: membranedev

stockly

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/stockly/SKILL.md

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 a strong, executable guide to the Membrane→Stockly workflow with concrete commands, explicit connection-state handling, and a useful proxy fallback. Its few weaknesses are minor padding and one redundant actions section.

Suggestions

Trim the Stockly intro paragraph and the "rather than auth plumbing" aside to save tokens without losing clarity.

Merge or differentiate "Searching for actions" and "Popular actions" — they repeat the same `action list --intent` command.

Formalize the connection steps as a numbered Step 1/Step 2 sequence so the "skip to Step 2" references resolve unambiguously.

Dimension	Reasoning	Score
Conciseness	The body is dominated by tight, executable bash commands with only minor over-explanation (the Stockly intro paragraph and the "focus on the integration logic rather than auth plumbing" aside), placing it noticeably above the efficient-but-tightenable midpoint.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases — login, `membrane connection ensure`, `--wait` polling, `action list`/`action run`, and a proxy options table — giving fully executable, specific guidance.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear with explicit state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, though the "Step 1b/Step 2" framing is only loosely formalized.	4 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with clear headers and no nested references is appropriate for a CLI skill, with only a minor organization gap from the near-duplicate "Searching for actions" and "Popular actions" sections.	4 / 5
	Total	17 / 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 covers the essential what-and-when in third person and is clearly tied to the Stockly product, giving it a solid baseline. Its main weakness is generic action wording and thin natural-language trigger coverage.

Suggestions

Replace generic verbs with concrete Stockly capabilities, e.g. "Track stock levels, forecast demand, and manage watchlists and portfolios."

Expand the trigger clause with natural user phrasings, e.g. "Use when the user wants to query Stockly inventory, check stock levels, or update watchlists."

Add key domain terms users actually say (inventory, stockouts, SKU, watchlist) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Stockly domain plus a couple of actions, but the actions are generic ("manage data", "manage records") rather than concrete capabilities, fitting the domain-with-actions-but-not-comprehensive anchor.	3 / 5
Completeness	Both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Stockly data") are present, but the trigger could be more specific, so it sits below the fully concrete anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Stockly data" and "Stockly integration" provide some relevant keywords, but common synonyms and variations a user might naturally say are missing.	3 / 5
Distinctiveness Conflict Risk	Triggering is keyed to the named product "Stockly" with its own data, making it mostly distinct, though the broad "manage data, records" framing leaves minor overlap risk with other data-management skills.	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/stockly/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.