Name: amply
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

amply

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

Quality

61%

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

Quality

Content

61%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 action-rich with concrete Membrane CLI commands and a well-handled connection state machine, but it carries some explanatory padding and lacks validation checkpoints for destructive operations (proxy DELETE, mutating actions). Structure is good with minor navigation nits.

Suggestions

Trim the intro background paragraph and the 'so you can focus on the integration logic rather than auth plumbing' line; Claude does not need Amply explained.

Add a verification/feedback step after running actions or proxy requests (e.g., check the response status/output before considering the operation complete) to satisfy the destructive-operation validation requirement.

Fix the dangling 'Step 2' reference by labeling the target section, and label '1a' alongside the existing '1b' for coherent navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary prose such as the Amply background paragraph ('Amply is a platform that helps companies manage and optimize their cloud infrastructure spend...') and 'so you can focus on the integration logic rather than auth plumbing.' Not a 4 because the padding is more than minor; not a 2 because the bulk is action-oriented and tight.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready commands (install, login, connection ensure, action run/list, request) plus a flags table. Not a 5 because the 'Popular actions' heading delivers only a discovery command instead of actual examples, and placeholders like CONNECTION_ID/<actionId> leave minor gaps.	4 / 5
Workflow Clarity	A clear sequence exists with a strong feedback loop for connection state (poll until READY, inspect clientAction, re-poll). However, the proxy supports destructive methods (DELETE) and action-running can mutate data with no verification/validation checkpoint, so the destructive/batch cap of 3 applies. Not a 4 because validation for the core destructive operations is missing.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no need for external reference files (actions are discovered dynamically via the CLI). Not a 5 because of minor organization gaps: the text references 'Step 2' which is not a labeled header, and '1b' appears without a corresponding '1a'.	4 / 5
	Total	14 / 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 answers both 'what' and 'when' explicitly and leverages a distinct product name for low conflict risk. It is held back by generic action language and limited trigger-term coverage.

Suggestions

Replace generic verbs with specific concrete actions (e.g., 'query cloud spend, manage employee and company records, run document templates') to lift specificity.

Expand the 'Use when...' clause with concrete trigger phrases a user would naturally say (e.g., 'when the user mentions Amply, cloud spend, or wants to query Amply records').

Add common synonyms and the product domain (cloud cost / FinOps) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the Amply domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concretely enumerated. Not a 2 because it does name 1-2 actions beyond the domain; not a 4 because the actions lack specificity and coverage is thin.	3 / 5
Completeness	Explicitly states both what ('Amply integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Amply data.'). Not a 5 because the 'when' clause is generic and lacks concrete trigger phrases listing the specific tasks.	4 / 5
Trigger Term Quality	Includes relevant keywords (Amply, data, records, workflows) and a trigger clause, but misses common variations or synonyms a user might naturally say. Not a 4 because coverage is not broad enough to qualify as 'good keyword coverage with only a few missing'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Amply' creates a clear niche with low conflict risk, but the generic verbs ('manage data, records, automate workflows') create minor overlap with other data-management skills. Not a 5 because the action language is not distinctive enough to eliminate overlap risk.	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/amply/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.