CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

amplication

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/amplication/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 Membrane CLI half of this body is a solid, executable guide with a genuinely well-handled connection state machine. It is dragged down by a ~180-line meaningless keyword dump that dominates the token budget, plus small coherence defects (undefined "Step 2" references, an empty "Popular actions" section, inconsistent CLI invocation).

Suggestions

Delete the "Amplication Overview" bullet list (lines 23-202) entirely — it is duplicated verb keywords with no informational value and consumes over half the skill's tokens; if any of it matters, it belongs in a single short sentence about what Amplication resources exist.

Fix the broken step references: define Step 1/Step 2 (or renumber) so "skip to Step 2" and the orphaned "#### 1b" resolve, and either populate "Popular actions" with real examples or remove the section.

Standardize on one CLI invocation form (e.g. always "membrane ..." after the install step) so commands are consistently copy-paste ready.

DimensionReasoningScore

Conciseness

Roughly 180 of the body's ~330 lines are a bare-verb bullet dump ("Scale", "Backup", "Monitor", "Automate"...) with many verbatim duplicates (Monitor appears 4 times, Alert 5 times, Build/Test/Deploy repeat), capped by the filler line "Use action names and parameters as needed." — over half the file is pure padding that earns no tokens.

1 / 5

Actionability

The CLI instructions are concrete and executable: install, login (including headless completion), connection ensure, polling with --wait, action list/run with JSON --input examples, and a complete proxy flag table. Minor gaps: inconsistent invocation ("membrane" vs "npx @membranehq/cli" vs "npx @membranehq/cli@latest") and a "Step 2" that is referenced but never defined keep it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The connection flow has an explicit feedback loop — ensure, poll with --wait, branch on READY / CLIENT_ACTION_REQUIRED (with clientAction sub-fields explained) / CONFIGURATION_ERROR, re-poll after the user acts — but the step numbering is incoherent ("skip to Step 2" with no Step 2, a "1b" with no "1a") and the "Popular actions" section is an empty header, which are minor validation/organization gaps rather than missing checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives inline in a single ~330-line file. Sections are headed (not monolithic), but the giant overview keyword list is inline content that should be cut or split out, and there are no references to signal — matching the anchor for having some structure while content that should be separate stays inline.

3 / 5

Total

12

/

20

Passed

Description

57%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 has a valid structure (what + explicit "Use when" trigger) and names a distinct platform, but its capability statement is generic. It reads as a templated integration blurb rather than a description of what one can concretely do with Amplication.

Suggestions

Replace the generic action verbs with concrete Amplication capabilities, e.g. "Create and manage entities, data models, roles and permissions, and deploy generated Node.js services and APIs."

Broaden trigger terms to the phrases users actually say: "Amplication", "entities", "data models", "resources", "backend generation", "deploy Amplication service".

State what the skill operationally is (driving Amplication through the Membrane CLI) so the what-clause is as explicit as the when-clause.

DimensionReasoningScore

Specificity

The description names the domain ("Amplication integration") but its actions — "Manage data, records, and automate workflows" — are generic verbs with no concrete capability, matching the anchor for naming the domain with minimal or generic actions rather than listing 1-2 concrete actions.

2 / 5

Completeness

Both parts are explicitly present: the what ("Amplication integration. Manage data, records, and automate workflows") and the when ("Use when the user wants to interact with Amplication data"). The when is explicit but narrow and the what is on the vague side, matching the anchor where both exist but the when could be more explicit or specific rather than the fully concrete trigger phrasing of a 5.

4 / 5

Trigger Term Quality

"Amplication", "data", and "records" are relevant keywords, but common natural phrasings users would say are missing ("entities", "data models", "services", "backend", "deploy", "Node.js"), so keyword coverage stops at some relevant terms without synonyms or variations.

3 / 5

Distinctiveness Conflict Risk

The named platform "Amplication" carves a clear niche and makes mistaken triggering unlikely, but the templated "X integration. Manage data" phrasing creates minor overlap risk with sibling integration skills, matching the mostly-distinct anchor rather than the clear-niche-minimal-conflict anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill