Name: alphamoon
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

alphamoon

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/alphamoon/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 highly actionable with concrete CLI commands and a solid connection workflow including feedback loops, but it carries an unnecessary introductory paragraph and offers no validation guidance for destructive action runs. It is well-structured as a single self-contained file with no external references.

Suggestions

Trim the opening 'Alphamoon is a project management and collaboration platform...' paragraph and the empty 'When to use which actions' line to reduce padding.

Fill the empty Description column in the Popular actions table so action selection is unambiguous.

Add an explicit validation/check step before running destructive actions (e.g., delete-collection) — confirm the target id and expected outcome before invoking `membrane action run`.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-and-table driven and efficient, but the opening paragraph ('Alphamoon is a project management and collaboration platform...') and several prose explanations are padding Claude does not need, fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	Concrete, copy-paste-ready commands (membrane login, connection ensure, action run, request) with a flags table cover the common cases, but the Popular actions table has empty Description columns and several placeholders (CONNECTION_ID), leaving minor gaps that keep it below 5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-retry feedback loop, but running actions — including destructive ones like delete-collection — lacks explicit validation checkpoints, capping it just below 5.	4 / 5
Progressive Disclosure	No bundle files are present and the skill is self-contained, but it is organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with good navigation, fitting 'good structure; minor organization gaps'.	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 covers both what and when and is clearly distinct thanks to the named app, but its action list is generic and its trigger terms lack synonyms or concrete variations. Tightening the action verbs and expanding the 'when' clause with specific trigger phrases would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Alphamoon-specific actions (e.g., 'list collections, get OCR results, upload files') to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users would actually say, such as 'Use when the user wants to list Alphamoon collections, retrieve OCR results, or upload files to Alphamoon'.

Dimension	Reasoning	Score
Specificity	Names the domain (Alphamoon) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the '1-2 concrete actions but not comprehensive' anchor rather than the more specific level 4.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Alphamoon data'), but the 'when' could be more explicit with concrete trigger phrases, so it sits at level 4 rather than 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Alphamoon data' surfaces the core keyword 'Alphamoon'/'Alphamoon data', but offers no synonyms, variations, or file extensions, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'Alphamoon' gives it a clear niche with distinct triggers and minimal conflict 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/alphamoon/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.