Name: amplication
Rating: 51.2 (1 reviews)
Author: membranedev

amplication

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

Quality

56%

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

Quality

Content

50%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 skill is highly actionable with concrete, executable Membrane CLI commands and a solid connection workflow, but its quality is dragged down by a large redundant keyword dump and missing validation for destructive operations.

Suggestions

Delete the ~150-word bullet keyword dump under Amplication Overview; it is pure padding that adds no guidance.

Add a validation/verification step after destructive `action run` or `membrane request -X DELETE/PUT` calls (e.g. re-query the resource to confirm the change) so the workflow clears the destructive-operation cap.

Trim explanatory prose that states what Claude already knows (e.g. what Amplication is, that Membrane handles auth) to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body opens with roughly 150 single-word bullet verbs (many duplicated, e.g. Monitor, Analyze, Optimize, Scale, Backup, Restore appearing twice) that explain nothing Claude does not already know and add severe padding.	1 / 5
Actionability	It provides copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) with concrete flags, JSON examples, and a full options table covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear poll-until-ready sequence with state checks and a feedback loop, but destructive operations like `action run` and `membrane request` (DELETE/PUT) lack validation checkpoints, capping the score.	3 / 5
Progressive Disclosure	There are no bundle files and the SKILL.md uses reasonable section headers, but the inline keyword dump is content that belongs nowhere and signals poor organization rather than a clean overview.	3 / 5
	Total	12 / 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 cleanly answers both what and when in a concise third-person voice, and the named platform keeps it distinct. It is held back by generic action verbs and thin trigger-term variation.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Amplication-specific actions such as creating entities, managing roles/permissions, or generating services.

Expand trigger terms with natural synonyms a user might say, e.g. "Amplication entities, data models, services, roles, or permissions".

Tighten the 'when' clause to name the concrete objects users interact with rather than the vague "Amplication data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of concrete actions, but the actions are generic verbs rather than a comprehensive, specific list.	3 / 5
Completeness	It states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Amplication data"), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	"Amplication data" and "interact with Amplication data" provide a relevant keyword but miss natural synonyms, variations, or file/extension terms a user might actually say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Amplication platform gives it a clear niche with minimal conflict risk against unrelated skills, with only minor overlap against generic data-management skills.	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/amplication/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.