Name: continuum-security-slne
Rating: 55.2 (1 reviews)
Author: membranedev

continuum-security-slne

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

Quality

63%

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/continuum-security-slne/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 content is a solid, command-driven integration guide with clear sequencing and good actionability via the Membrane CLI. Its main weaknesses are a verbose inline entity enumeration and the absence of any reference files to offload the long list and flag table, which holds back conciseness and progressive disclosure.

Suggestions

Move the 60-item entity/relationship list and the proxy flag table into a `references/` file (e.g. `references/entities.md`), keeping only a brief pointer inline so the skill body stays lean.

Replace the generic `--intent "QUERY"` placeholder in examples with a realistic intent string (e.g. `--intent "list open vulnerabilities"`) so the commands are copy-paste-ready.

Add a short 'Verify' checkpoint after `membrane action run` (e.g. check the `output` field and HTTP status) to push workflow clarity toward a fully validated feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and little concept-over-explanation, but it pads with a 60-line bullet enumeration of entity names ('Project', 'Scan', 'Scan Type', ...) and somewhat lengthy auth/connection narration that could be tightened, matching the score-3 'mostly efficient with some unnecessary content' anchor rather than 4.	3 / 5
Actionability	It provides concrete, executable commands throughout (`npm install -g @membranehq/cli@latest`, `membrane action run <actionId> --connectionId=... --json`, a flag table) with minor gaps (e.g. `--intent "QUERY"` is a placeholder), fitting the score-4 'mostly executable guidance with minor gaps' anchor rather than fully copy-paste-ready score 5.	4 / 5
Workflow Clarity	The connect→wait→READY/CLIENT_ACTION_REQUIRED→search→run sequence is clearly laid out with state-based branches and polling guidance, and the `--wait` polling forms a feedback loop; it stops short of an explicit validate/retry checklist, matching score 4 rather than 5, and the operations are non-destructive so the batch/destructive cap does not apply.	4 / 5
Progressive Disclosure	The body has section structure and relies appropriately on dynamic CLI discovery rather than inlining API docs, but the long inline entity list and the proxy flag table are content that could live in a reference file, and no bundle files exist to offload it — matching the score-3 'some structure but could be better organized' anchor rather than 4.	3 / 5
	Total	14 / 20 Passed

Description

62%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 well-formed with both a clear 'what' and an explicit 'Use when' trigger, and the named product gives it decent distinctiveness. It is held back by generic action verbs and limited natural trigger-term coverage that lean on the product name rather than concrete security-domain keywords.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete security-lifecycle actions such as 'track vulnerabilities, manage findings, run scans, and map compliance controls'.

Add natural trigger keywords users would actually say (e.g. 'vulnerabilities', 'findings', 'scan results', 'compliance', 'IridoRrisk') so the description surfaces for those requests.

Make the 'Use when' clause more specific, e.g. 'Use when managing vulnerabilities, findings, scans, or compliance evidence in Continuum Security SLNE.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Continuum Security SLNE') and two generic action verbs ('Manage data, records, and automate workflows'), but the actions are broad rather than concrete like 'extract', 'fill', or 'merge', so it matches the 'domain + 1-2 actions, not comprehensive' anchor rather than 4.	3 / 5
Completeness	It states a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Continuum Security SLNE data'), but the 'when' is generic and could be more specific, fitting the score-4 anchor rather than the fully concrete score-5 example.	4 / 5
Trigger Term Quality	Includes the product name and 'data'/'records'/'workflows', but lacks natural synonyms a user would say (e.g. 'vulnerabilities', 'findings', 'scans', 'compliance') and any file extensions, so keyword coverage has relevant terms but misses common variations — matching the score-3 anchor rather than 4.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named product ('Continuum Security SLNE') makes it mostly distinct with only minor overlap risk against other security/SLNE skills; it is not the fully clear-niche score-5 because 'interact with data' is somewhat broad.	4 / 5
	Total	14 / 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/continuum-security-slne/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.