Name: osano
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

osano

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

Quality

64%

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/osano/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 Osana through the Membrane CLI, with a clear connection-state workflow and validation checkpoints. Its main weakness is conciseness padding in the intro and best-practices sections.

Suggestions

Trim the explanatory prose in the intro and best-practices (e.g. drop 'This ensures legal compliance and builds trust with users regarding their data' and 'auth plumbing') to lift conciseness.

Remove or fold the redundant 'Popular actions' section, which repeats the action list/search instructions already covered under 'Searching for actions'.

Add a brief validation note for action results (e.g. checking the output/error fields before treating a run as successful) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command lists, but the intro pads with 'builds trust with users regarding their data' and best-practice notes carry fluff like 'burn less tokens' and 'auth plumbing', matching anchor 3 rather than the trimmed anchor 4.	3 / 5
Actionability	It provides concrete executable commands throughout (install, login, connection ensure, action run, request proxy with a full flag table), with only minor placeholder gaps like CONNECTION_ID and QUERY, matching anchor 4.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, fitting anchor 4; the redundant 'Popular actions' section is the minor gap keeping it from 5.	4 / 5
Progressive Disclosure	It is a single self-contained file with clear section headers and no nested references, giving good structure and easy navigation; with no external file references the structure matches anchor 4 rather than the one-level-deep reference pattern of anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

61%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 clearly names the Osana niche and includes a usable 'Use when' trigger, but its action language is generic and its trigger terms lack synonyms or extensions. It is distinct and complete enough to guide selection, just not richly specified.

Suggestions

Replace the generic verbs with concrete Osana actions (e.g. 'manage consent notices, handle subject rights requests, search and run Osana actions') to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'consent management', 'GDPR/CCPA compliance', 'subject rights requests', or 'cookie consent'.

Mention the Membrane CLI interaction model briefly in the description so the integration mechanism is signaled up front.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Osana domain but the actions are generic rather than concrete verbs; this matches anchor 2 and falls short of the 1-2 concrete actions needed for anchor 3.	2 / 5
Completeness	It states both a what ('Osana integration. Manage data, records, and automate workflows') and a when ('Use when the user wants to interact with Osana data'), but the when clause is generic rather than packed with concrete trigger phrases, fitting anchor 4 not anchor 5.	4 / 5
Trigger Term Quality	The only natural keywords are 'Osana' and 'data' ('Use when the user wants to interact with Osana data'), with no synonyms or common variations, matching anchor 3 rather than the broad coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Osana is a specifically named platform and the trigger 'interact with Osana data' carves a clear niche with minimal overlap risk, matching anchor 5.	5 / 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/osano/SKILL.md
Commit: f484c82

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