Name: ubiq-security
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

ubiq-security

Ubiq Security integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ubiq Security 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/ubiq-security/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 body is a lean, actionable guide to the Membrane/Ubiq integration with a well-sequenced connection workflow and clear section structure. Its main weaknesses are some marketing padding, a duplicated command, and a dangling 'Step 2' reference.

Suggestions

Trim the opening marketing paragraph and the redundant action-list command in 'Popular actions' to improve token efficiency.

Fix the 'skip to Step 2' reference by adding an explicit 'Step 2: Search and run actions' header or rewording the pointer.

Add one complete worked example (real connection id, a concrete action run, and a sample proxy request path) to lift actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-oriented content, but the marketing-style opening ("encryption-as-a-service... comply with security regulations") and the duplicated action-list command in 'Popular actions' are unnecessary padding that could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands with real flags (login, connection ensure, action run, request) cover the common cases; held back from 5 by generic placeholders like /path/to/endpoint and {"key": "value"} with no complete worked example.	4 / 5
Workflow Clarity	The connection flow is a clear state-machine sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; the dangling 'skip to Step 2' reference with no matching Step 2 header is a minor gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files to mismanage; the thin 'Popular actions' discovery content could live in a separate reference, keeping it just short of the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

66%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 brand-distinct and answers both what and when in third person, but its capability verbs are generic and the trigger phrases lack synonym coverage. It is solidly above average yet short of the most concrete, comprehensive examples.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Ubiq capabilities such as encryption, keypair/group management, or audit log access.

Broaden the 'Use when' clause with natural variations (e.g. 'encrypt data', 'manage encryption keys', 'access Ubiq audit logs') so users phrase the need in more ways.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of actions, but those actions are generic rather than concrete capabilities, fitting the 'domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Ubiq Security data"), but the 'when' could be more explicit/specific, matching the anchor for both present with room to sharpen.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Ubiq Security data" offers a reasonable trigger around the brand and 'data', but lacks synonyms or common variations users might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The brand-specific "Ubiq Security" trigger carves a clear niche with distinct triggers and minimal overlap risk with other skills, matching the top anchor.	5 / 5
	Total	15 / 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/ubiq-security/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.