Name: stackshare
Rating: 63.2 (1 reviews)
Author: membranedev

stackshare

StackShare integration. Manage Stacks, Companies, Projects, Users. Use when the user wants to interact with StackShare data.

Quality

75%

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

Quality

Content

76%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 is highly actionable with comprehensive executable CLI examples and a logical flow. It loses points on workflow clarity for missing validation/feedback steps around destructive proxy operations, and has minor conciseness and organization nits.

Suggestions

Add explicit validation checkpoints after connecting (e.g., verify the connection exists) and after destructive proxy calls (e.g., re-fetch the resource to confirm the change), with a fix-and-retry loop.

Trim filler lines such as 'When to use which actions: Use action names and parameters as needed.' and tighten 'so you can focus on the integration logic rather than auth plumbing'.

Merge the redundant 'Popular actions' section into 'Searching for actions' to remove the duplicated action-discovery command.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with clean executable command blocks, but contains minor over-explanation and filler such as 'so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens', and the unhelpful line 'When to use which actions: Use action names and parameters as needed.'	4 / 5
Actionability	It provides copy-paste-ready CLI commands for every stage (install, login, connect, list, search, run, proxy) with concrete JSON input examples and a full flag-option table, covering the common cases.	5 / 5
Workflow Clarity	A clear install→login→connect→search→run sequence is present, but there are no explicit validation checkpoints, and the proxy section supports destructive methods (POST/PUT/DELETE) without any verify-or-rollback feedback loop, capping the score per the destructive-operations guidance.	3 / 5
Progressive Disclosure	With no bundle files present, the skill is a self-contained guide organized into well-labeled sections with easy header navigation; minor gaps like the redundant 'Popular actions' section and a thin entity overview keep it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clear, third-person, and distinctively scoped to StackShare with an explicit 'Use when...' clause. Its main weakness is that the action surface is summarized by one generic verb and the trigger guidance is a single phrase rather than varied concrete triggers.

Suggestions

Replace the single verb 'Manage' with several concrete actions (e.g., 'List, search, create, and update Stacks, Companies, Projects, and Users') to raise specificity.

Expand the 'Use when...' clause with multiple natural trigger phrases (e.g., 'Use when the user mentions StackShare, tech stacks, or wants to look up tools/companies on StackShare').

Dimension	Reasoning	Score
Specificity	The description names the domain ('StackShare integration') and lists concrete entities ('Manage Stacks, Companies, Projects, Users'), but relies on a single generic verb ('Manage') rather than enumerating several distinct concrete actions.	3 / 5
Completeness	It explicitly answers both 'what' (StackShare integration; manage Stacks/Companies/Projects/Users) and 'when' ('Use when the user wants to interact with StackShare data'), but the 'when' clause is a single generic phrase rather than a rich set of concrete triggers.	4 / 5
Trigger Term Quality	It includes the strong natural trigger 'StackShare' plus entity nouns and 'interact with StackShare data', giving good coverage, but omits common synonyms a user might say such as 'tech stack' or 'tools'.	4 / 5
Distinctiveness Conflict Risk	It targets a named third-party integration with product-specific entity triggers, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/stackshare/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.