Name: wappalyzer
Rating: 53.6 (1 reviews)
Author: membranedev

wappalyzer

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

Quality

60%

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

Quality

Content

63%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 strongly actionable, well-sequenced guide to driving Wappalyzer through the Membrane CLI, with concrete commands and good connection-state feedback loops, but it carries some redundant padding and keeps reference-style material inlined rather than split into separate files.

Suggestions

Remove the repeated `action list` command in "Popular actions" (already shown in "Searching for actions") and tighten the introductory Wappalyzer background paragraph.

Fix the dangling "skip to Step 2" reference by either labeling the subsequent section as Step 2 or rewording to "skip to Running actions".

Move the proxy-request flags table and bulk action-discovery details into a separate reference file (e.g. references/proxy.md) referenced one level deep from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete membrane commands, but the opening paragraph explaining what Wappalyzer is and the repeated `action list` command (in both "Searching for actions" and "Popular actions") add unnecessary explanation/padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (login, connection ensure, action list/run, request with a full flag table), with only minor gaps like unresolved CONNECTION_ID/actionId placeholders keeping it below fully executable.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, but the dangling "skip to Step 2" reference (no labeled Step 2) is a minor navigation gap.	4 / 5
Progressive Disclosure	The single file is well-sectioned with clear headers, but all content is inlined with no external reference files, and the proxy-flags reference table and action-discovery details that could live in a separate file are kept inline.	3 / 5
	Total	14 / 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 includes an explicit "Use when" trigger and anchors on the distinct Wappalyzer brand, but its capability list is generic and abstract rather than naming concrete Wappalyzer actions like lookup or technology profiling.

Suggestions

Replace generic verbs with concrete Wappalyzer actions, e.g. "Look up the technologies used on a website, retrieve account results, and get technology profiles."

Add natural trigger synonyms/extensions users would say, e.g. "Use when the user wants to identify a site's tech stack, profile a website's technologies, or retrieve Wappalyzer lookup results."

Drop the padded "Manage data, records, and automate workflows" phrasing, which is vague and adds conflict risk with other data-integration skills.

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Wappalyzer domain but the actions are generic and abstract rather than concrete (no "extract," "lookup," or "profile" verbs), matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	It states both a what ("Wappalyzer integration. Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Wappalyzer data"), but the what is vague enough to stop short of the score-5 anchor.	4 / 5
Trigger Term Quality	"Wappalyzer" and "interact with Wappalyzer data" supply the key natural term, but the supporting keywords (data, records, workflows) are generic and lack common synonyms or variations users would actually say.	3 / 5
Distinctiveness Conflict Risk	The named Wappalyzer brand gives it a clear, distinct niche with minimal conflict risk, though the generic "manage data / automate workflows" phrasing leaves minor overlap risk with other 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/wappalyzer/SKILL.md
Commit: f484c82

Reviewed: 3 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.