Name: amcards
Rating: 60 (1 reviews)
Author: membranedev

amcards

AMcards integration. Manage Cards, Users, Templates, Contacts, Groups. Use when the user wants to interact with AMcards data.

Quality

70%

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/amcards/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 with executable Membrane CLI commands and a solid connection-state workflow, but it includes a padded platform intro and bulk inline action reference, and lacks validation guidance for its destructive/batch operations.

Suggestions

Add a 'confirm before destructive/batch operations' checkpoint to the Running actions section (e.g. verify contact ID and confirm with the user before delete-contact or send-campaign) to lift workflow_clarity above 3.

Trim or move the 'AMcards is a digital business card platform...' intro and consider moving the Popular actions table to a references file to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening 'AMcards is a digital business card platform...' explains the platform unnecessarily and the 17-row Popular actions table is bulk inline reference that adds tokens beyond what Claude needs in the overview.	3 / 5
Actionability	Copy-paste-ready executable commands throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run ... --input', 'membrane request CONNECTION_ID /path' — cover the common cases with specific flags and JSON examples.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-polling, but the skill exposes destructive and batch actions (delete-contact, send-campaign) whose 'Running actions' workflow has no validation/verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no nested references, though the large inline actions table is reference material that could live in a separate file.	4 / 5
	Total	15 / 20 Passed

Description

71%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 in third person and names a distinct platform, but the trigger phrasing relies on a single proper noun with little keyword variation. Specificity is good though built on one generic verb.

Suggestions

Expand the trigger clause with concrete natural phrases, e.g. 'Use when the user wants to send cards, manage contacts, or run drip campaigns in AMcards.'

Replace the single generic verb 'Manage' with a few specific actions (create, list, send, delete) to lift specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete objects to manage — 'Manage Cards, Users, Templates, Contacts, Groups' — giving specific coverage, though 'Manage' is a single generic verb applied across all nouns, leaving minor gaps.	4 / 5
Completeness	Both 'what' (AMcards integration managing Cards/Users/Templates/Contacts/Groups) and 'when' ('Use when the user wants to interact with AMcards data') are present, but the 'when' clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with AMcards data' is relevant but keyword coverage is thin — essentially just the proper noun 'AMcards' with no synonyms or natural variations users might say.	3 / 5
Distinctiveness Conflict Risk	Names a specific named platform (AMcards) with distinct triggers, creating a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 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/amcards/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.