Name: miniorange
Rating: 61.6 (1 reviews)
Author: membranedev

miniorange

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

Quality

72%

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

Quality

Content

82%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, providing executable commands for the entire connection and action workflow with explicit state-based validation checkpoints and feedback loops. Minor weaknesses are some trimmable explanatory prose and an undefined 'Step 2' reference that slightly disrupts workflow continuity.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and a tight flag table, with only minor over-explanation such as the product-intro paragraph and repeated notes about --json, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Copy-paste-ready commands cover the full lifecycle (install, login, connection ensure, action list/run, request proxy) with clearly labeled parameter placeholders, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence includes explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-poll feedback loops, but the dangling 'skip to Step 2' reference and '1b' numbering are minor gaps keeping it just below anchor 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, well-labeled sections with no nested references, fitting the 'good structure; most content appropriately placed' anchor.	4 / 5
	Total	17 / 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 names the product and includes both a what and a when clause, but the capabilities are generic verbs and the trigger omits the concrete miniOrange use cases (MFA, SSO, authentication) that users would actually mention. It is solid but could be sharpened with more specific actions and trigger terms.

Suggestions

Replace generic verbs with concrete miniOrange capabilities, e.g. 'Configure MFA and SSO, manage users and licenses, and automate authentication workflows'.

Expand the trigger to include natural user phrases such as 'multi-factor authentication', 'single sign-on', or 'miniOrange users/licenses'.

Avoid the vague 'Manage data, records' phrasing, which overlaps with broad data skills and weakens distinctiveness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the miniOrange domain and several actions, but the verbs are generic rather than concrete like 'extract' or 'fill'. It lists more than minimal coverage but lacks specificity, fitting between anchors 2 and 3.	3 / 5
Completeness	Both "what" (manage data, records, automate workflows) and an explicit "when" clause are present, but the trigger could be more specific (e.g., naming MFA/SSO use cases), fitting the anchor where both exist yet "when" could be more explicit.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with miniOrange data" includes the core keyword "miniOrange" but omits natural variations users would say (MFA, SSO, authentication, single sign-on), matching the anchor for some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "miniOrange" gives a clear niche with minimal conflict risk, though the generic actions ("manage data, records") leave minor overlap with broad data-management skills, fitting between anchors 4 and 5.	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/miniorange/SKILL.md
Commit: f484c82

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