Name: orama
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

orama

Orama integration. Manage data, records, and automate workflows. Use when the user wants to interact with Orama 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/orama/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 highly actionable with executable Membrane CLI commands and a clear state-driven connection workflow including retry checkpoints. Its main weaknesses are some unneeded explanatory padding and a single-file structure that inlines material that could be progressively disclosed via reference files.

Suggestions

Trim concept explanations Claude already knows, e.g. the opening paragraph on what Orama is and the 'focus on integration logic rather than auth plumbing' framing.

Move the proxy flag reference table and the connection-state enumeration into separate reference files (e.g. references/proxy.md, references/connection-states.md) and link to them from SKILL.md for progressive disclosure.

De-duplicate the 'membrane action list --intent' example, which appears in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	Largely efficient with copy-paste commands, but retains several explanatory passages Claude doesn't need (what Orama is, 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed.	3 / 5
Actionability	Concrete, runnable CLI commands with documented flags throughout (login, connection ensure/get, action list/run, proxy request table), with only minor gaps like placeholder CONNECTION_ID/QUERY and a duplicated action-list example.	4 / 5
Workflow Clarity	Clear install → authenticate → connect → poll → discover → run sequence with explicit state-based checkpoints and a retry loop (CLIENT_ACTION_REQUIRED → user acts → re-poll), though it is not a destructive operation requiring the strict cap.	4 / 5
Progressive Disclosure	The file has good section headers but no bundle files exist and all content is inlined in one ~155-line document; content such as the proxy flag table and connection states could be split into referenced files.	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 correctly includes an explicit 'Use when' trigger and names the Orama product, giving it solid completeness and distinctiveness. It is weakened by generic action verbs ('manage data', 'automate workflows') that lack concrete capability specifics and by limited trigger-term variety.

Suggestions

Replace generic verbs with concrete capabilities Orama actually exposes, e.g. 'create and query full-text search indexes, insert and search records' instead of 'manage data, records'.

Add natural trigger variations and synonyms users might say, such as 'search', 'indexing', 'full-text search', or 'Orama database'.

Sharpen the 'when' clause with concrete trigger phrases, e.g. 'Use when the user wants to add in-memory search, index documents, or run typo-tolerant full-text queries.'

Dimension	Reasoning	Score
Specificity	Names the domain (Orama) and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete capabilities, matching the anchor for 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Orama data'); the trigger clause is present but could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product name 'Orama' and phrases like 'interact with Orama data', but lacks common synonyms and variations a user might say beyond repeating 'Orama'.	3 / 5
Distinctiveness Conflict Risk	Tied to the distinct product name 'Orama', giving it a clear niche with minimal overlap risk, though the generic verb phrases ('manage data', 'automate workflows') keep it just below fully distinct.	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/orama/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.