Name: signal-sciences
Rating: 55.2 (1 reviews)
Author: membranedev

signal-sciences

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

Quality

62%

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

Quality

Content

67%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, actionable guide to driving Signal Sciences through the Membrane CLI, with concrete commands and a clear connection-state workflow. It is held back from the top band by a redundant concept intro and a duplicated command, plus placeholder-only examples that lack a worked end-to-end run.

Suggestions

Trim the opening WAF concept paragraph and consolidate the duplicated `action list` command into a single section to tighten token efficiency.

Add one fully-worked end-to-end example with realistic values (a concrete connection id and action id) so the run/proxy flow is copy-pasteable without guessing placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening WAF concept-explanation ("a web application firewall (WAF) that protects applications...") states what Claude already knows, and the `action list` command is duplicated across "Searching for actions" and "Popular actions".	3 / 5
Actionability	It provides mostly executable, copy-paste-ready commands (install, login, connection ensure, action run, proxy) plus a flag table, with minor gaps from unfilled placeholders like `<actionId>` and `CONNECTION_ID` and no fully-worked end-to-end example.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with a state-handling feedback loop (poll until READY; re-poll after CLIENT_ACTION_REQUIRED), leaving only minor validation gaps.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle files, it is well-organized into Overview / Working with Signal Sciences / Best practices sections plus a clearly signaled official-docs link; it exceeds the 50-line simple-skill threshold, so it is not a 5, but structure and placement are good.	4 / 5
	Total	15 / 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 product and includes an explicit "Use when..." trigger, satisfying the completeness floor, but relies on generic action language rather than concrete Signal Sciences capabilities. Trigger term coverage is narrow, missing the natural synonyms (WAF, Fastly, firewall) users are likely to say.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Signal Sciences actions such as reviewing signals, managing rules, blocking requests, and working with sites and lists.

Expand the trigger to include natural synonyms a user would actually say, e.g. "Use when the user wants to work with Signal Sciences — its WAF signals, rules, sites, or request logs (Signal Sciences / Fastly WAF)."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Signal Sciences domain but the actions are minimal and generic, with no concrete capabilities like blocking requests, reviewing signals, or managing rules.	2 / 5
Completeness	Both a "what" (integration, manage data/records, automate workflows) and an explicit "Use when the user wants to interact with Signal Sciences data" trigger are present, though both remain somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	"Signal Sciences" and "data" are relevant natural keywords, but common variations and synonyms a user would say (WAF, Fastly, firewall rules, signals) are missing.	3 / 5
Distinctiveness Conflict Risk	"Signal Sciences" is a distinctive named product giving a clear niche with minimal conflict risk, but the generic action verbs (manage data, records) create 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/signal-sciences/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.