Name: appmachine
Rating: 58.4 (1 reviews)
Author: membranedev

appmachine

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

Quality

67%

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

Quality

Content

68%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, dominated by concrete, executable Membrane CLI commands covering auth, connection, action discovery/execution, and proxying. Its weaknesses are minor redundancy across sections and the absence of validation guidance before running potentially data-modifying actions.

Suggestions

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated `action list` command.

Add an explicit validation/verification step before running mutating actions (e.g., run a read/query action first to preview the affected records, or confirm destructive operations with the user).

Trim the introductory paragraph about Appmachine's target audience, or move it to a reference file, since it does not guide execution.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the 'Popular actions' section duplicates the action-list command from 'Searching for actions' and the marketing-style intro paragraph about who uses Appmachine adds little actionable value.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case (install, login, connection ensure, polling, action list/run, proxy request) with flags and JSON-output patterns.	5 / 5
Workflow Clarity	The connection setup has a clear state-machine sequence with polling checkpoints (BUILDING/READY/CLIENT_ACTION_REQUIRED), but running actions on external data is a potentially destructive/batch operation with no pre-execution validation or verification step, which caps this dimension.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no bundle files needed for a CLI integration, but it is monolithic in one file with minor redundancy between 'Searching for actions' and 'Popular actions'.	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 is well-formed with a clear third-person 'what' and an explicit 'Use when' trigger anchored to a distinctive named platform. Its main weakness is generic action verbs and a narrow trigger phrase that omits core Appmachine concepts like apps, builds, and publishing.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Appmachine actions such as 'Build and publish apps, manage data sources, and configure user roles'.

Broaden the trigger to cover natural phrasings users would say, e.g. 'Use when the user wants to build, publish, or manage Appmachine apps, data sources, users, or roles.'

Add file/extension or entity synonyms (apps, data sources, roles, plans) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Appmachine integration') and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill'.	3 / 5
Completeness	It answers both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when...' clause), but the when clause is a single, somewhat generic trigger rather than concrete scenarios.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Appmachine data' surfaces relevant keywords (Appmachine, data, records) but misses common variations such as 'app', 'build', 'publish', or 'roles'.	3 / 5
Distinctiveness Conflict Risk	'Appmachine' is a uniquely named platform, giving the skill a clear niche with minimal risk of triggering for unrelated skills.	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/appmachine/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.