Name: threat-stack
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

threat-stack

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

Quality

66%

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

Quality

Content

75%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 a well-structured, highly actionable integration guide with concrete commands and a clear connection-readiness workflow including validation and feedback loops. Minor issues — an orphaned "Step 2" reference, a mislabeled "Popular actions" section, and a little over-explanation — keep it just short of exemplary.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and mostly lean, with only minor over-explanation such as the opening paragraph describing what Threat Stack is and a few conversational asides ("so you can focus on the integration logic rather than auth plumbing") that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands across install, auth, connection, action search/run, and proxy with a concrete flag table, but the "Popular actions" section only points to discovery rather than listing actual named actions, a minor gap.	4 / 5
Workflow Clarity	The connection workflow has explicit state validation (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll→act→re-poll feedback loop, but the orphaned "skip to Step 2" reference (with no defined Step 2 and a "1b" lacking a labeled "1a") is a minor sequencing gap.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with appropriate inline placement for a self-contained operational CLI skill and no external reference files needed; minor organization gaps (the thin "Popular actions" section, slightly off step numbering) keep it just below a 5.	4 / 5
	Total	16 / 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 has an explicit trigger clause and clear product anchoring, but its action language is generic rather than naming concrete Threat Stack capabilities. Tightening the "what" with specific feature actions and richer trigger keywords would notably improve it.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Threat Stack operations, e.g., "Query alerts, observations, and assets; retrieve alert and asset details; automate security response workflows."

Add natural trigger keywords users actually say — e.g., "Threat Stack alerts, observations, assets, intrusion detection, compliance violations" — so the skill matches when users mention those features.

Make the "what" more concrete (named actions tied to Threat Stack's alert/observation/asset model) to push completeness toward an explicit, comprehensive 5.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Threat Stack integration") but the actions are minimal and generic — "Manage data, records, and automate workflows" is business-speak rather than concrete Threat Stack operations, matching the anchor that names the domain with only generic actions.	2 / 5
Completeness	It provides both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Threat Stack data"), but the "what" is somewhat vague so it does not reach the fully concrete level of a 5.	4 / 5
Trigger Term Quality	"Threat Stack" and "interact with Threat Stack data" are relevant natural keywords a user would say, but the description omits specific feature terms (alerts, observations, assets) and their synonyms that users commonly mention, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Anchoring triggers to the specific named product ("Threat Stack data") makes it mostly distinct with minimal conflict risk, though the templated generic phrasing ("Manage data, records") leaves minor overlap risk with sibling integration skills.	4 / 5
	Total	13 / 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/threat-stack/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.