Name: stackhawk
Rating: 60 (1 reviews)
Author: membranedev

stackhawk

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

Quality

70%

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/stackhawk/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 highly actionable with concrete, copy-paste-ready commands and a well-structured connection workflow that includes polling and state-based feedback loops. Minor trimming of the introductory DAST explanation and a validation note after action runs would push it to excellent.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the opening paragraph explaining what DAST/StackHawk is and who uses it covers concepts Claude already knows and could be trimmed, fitting the score-4 anchor.	4 / 5
Actionability	It provides copy-paste-ready bash commands for install, login, connection, action discovery, action execution, and proxy requests with a full flags table, covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with polling checkpoints and a READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR feedback loop, but there is no validation guidance after running actions, matching the score-4 anchor.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections (Install, Auth, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, though the single-file body exceeds the 50-line simple-skill threshold so it sits at score 4 rather than 5.	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 names the StackHawk niche and includes an explicit trigger clause, but its capability verbs are generic rather than concrete DAST-specific actions. Tightening the action list and adding natural synonyms would lift it from mid-range to strong.

Suggestions

Replace generic verbs with concrete StackHawk/DAST actions, e.g. "Run StackHawk scans, triage vulnerabilities, and manage applications and organizations."

Add natural trigger terms users would say — DAST, vulnerability scanning, scan results, application security testing — alongside "StackHawk".

Make the "Use when" clause more specific, e.g. "Use when the user wants to run or review StackHawk DAST scans, manage scan targets, or triage vulnerabilities."

Dimension	Reasoning	Score
Specificity	The description names the domain ("StackHawk integration") but the actions — "Manage data, records, and automate workflows" — are generic and not concrete StackHawk-specific operations like running scans or triaging vulnerabilities, matching the score-2 anchor.	2 / 5
Completeness	It states both a "what" (manage data, records, workflows) and an explicit "when" ("Use when the user wants to interact with StackHawk data"), but the trigger guidance is generic and could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	It includes the core keyword "StackHawk" and a trigger clause, but misses natural synonyms and variations a user would say (DAST, vulnerability scanning, scans, security testing), fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Repeatedly naming the specific tool "StackHawk" gives it a clear niche with minimal conflict risk, though the generic "manage data, records, and workflows" phrasing leaves minor overlap with adjacent 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/stackhawk/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.