Name: originalityai
Rating: 59.2 (1 reviews)
Author: membranedev

originalityai

Originality.ai integration. Manage Documents, Users, Workspaces. Use when the user wants to interact with Originality.ai data.

Quality

68%

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

Quality

Content

75%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 copy-paste CLI commands and a clear connection workflow featuring feedback loops, but it has some redundancy between action-listing sections, vague filler, and broken step cross-references that hurt conciseness and sequencing.

Suggestions

Merge the redundant 'Searching for actions' and 'Popular actions' sections, which both demonstrate `action list --intent=QUERY`, into one.

Fix the dangling cross-references: 'skip to Step 2' points to no labeled Step 2, and '1b' has no '1a' — relabel the connection workflow with consistent step numbers.

Remove the non-instructive filler line 'When to use which actions: Use action names and parameters as needed.'

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the redundant 'Searching for actions' and 'Popular actions' sections both demonstrate `action list --intent=QUERY`, the vague filler 'When to use which actions: Use action names and parameters as needed' adds nothing, and the product intro paragraph lightly over-explains, fitting anchor 3 over the trim anchor 4.	3 / 5
Actionability	Provides copy-paste ready, executable commands throughout (e.g., `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://originality.ai/" --json`, `membrane action run <actionId> --input '{"key": "value"}' --json`) covering install, auth, connect, search, run, and proxy, matching anchor 5's fully executable coverage.	5 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with explicit feedback loops for connection state (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but dangling 'skip to Step 2' references with no labeled Step 2 and a '1b' with no '1a' leave minor sequence gaps, fitting anchor 4 rather than the fully-checkpointed anchor 5.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files and well-organized section headers; no nested references exist, and content is appropriately sectioned, but at ~140 lines some material (detailed clientAction state handling, proxy flag table) could be split out, fitting anchor 4's 'good structure, minor organization gaps'.	4 / 5
	Total	16 / 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 covers both what and when with a product-specific niche, but relies on a single generic verb ('Manage') and omits the natural vocabulary (plagiarism, AI detection) users would actually say when needing this skill.

Suggestions

Replace the generic verb 'Manage' with specific actions (e.g., 'Scan content for plagiarism and AI generation, manage documents, users, and workspaces').

Add natural trigger terms users say, such as 'plagiarism detection', 'AI content detection', or 'scan for originality'.

Tighten the 'when' clause with concrete triggers (e.g., 'Use when the user wants to check content for plagiarism or AI-generated text').

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Documents, Users, Workspaces' name three concrete resource types but rely on a single generic verb ('Manage') rather than multiple distinct actions, matching anchor 3 (domain + concrete actions, not comprehensive) and falling short of anchor 4's 'several specific actions'.	3 / 5
Completeness	An explicit 'Use when the user wants to interact with Originality.ai data' clause provides the 'when', and 'Manage Documents, Users, Workspaces' provides the 'what', but the trigger is generic rather than concrete phrases, matching anchor 4 and not the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	Contains the product name 'Originality.ai' and entity terms 'Documents, Users, Workspaces' but omits the natural phrases users actually say for this product ('plagiarism', 'AI detection', 'scan content'), fitting anchor 3's 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Originality.ai' qualifier gives a clear niche with product-specific triggers, but the generic 'Documents, Users, Workspaces' entities carry minor overlap risk with other SaaS skills, fitting anchor 4 rather than the minimal-conflict anchor 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/originalityai/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.