CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

amcards

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

Quality

74%

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/amcards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

This is a highly actionable integration skill with copy-paste-ready CLI commands, a concrete action catalog, and a well-handled connection state machine with polling and error states. Its weaknesses are the missing validation/confirmation guidance for destructive and batch actions (which caps workflow clarity) and a few padded or marketing-flavored sentences that could be trimmed.

Suggestions

Add a validation checkpoint before destructive or batch actions — e.g. "Before running delete-contact or send-campaign, confirm the target with the user and re-fetch the record with get-contact to verify it's the right one".

Fix the broken step numbering: "skip to Step 2" references a step that is never defined — label the setup steps explicitly (Step 1: connect, Step 2: search/run actions).

Trim filler such as "It helps users network and exchange contact information more efficiently" and the URL-normalization aside, and correct "This will burn less tokens" to "use fewer tokens".

DimensionReasoningScore

Conciseness

The body is dominated by efficient, copy-paste commands and tables, but contains minor over-explanation that could be trimmed: "It helps users network and exchange contact information more efficiently", the URL-normalization aside, and awkward phrasing like "This will burn less tokens". It is more efficient than the score-3 anchor's unnecessary commentary but not the lean every-token-earns-its-place level of 5.

4 / 5

Actionability

Every workflow step ships an executable command: "npm install -g @membranehq/cli@latest", "membrane login complete <code>", "membrane connection ensure \"https://amcards.com/\" --json", "membrane action list --intent \"QUERY\" --limit 10 --json", "--input '{\"key\": \"value\"}'", plus a 17-action catalog and a proxy flag table. Commands are copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

The setup sequence is clear with a well-specified connection state machine (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop, but the skill exposes destructive and batch operations ("Delete Contact", "Send Campaign", mailings) with no pre-action confirmation or validation guidance, which caps this dimension at 3 per the rubric. The dangling "skip to Step 2" reference to a step that is never labeled adds a further gap.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned SKILL.md (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices). The under-50-line exception for a 5 does not apply at ~155 lines, and content like the 17-row actions table and dangling step references keep it at "good structure with minor organization gaps" rather than fully clear one-level-deep navigation.

4 / 5

Total

16

/

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 has a solid structure with a clear what and an explicit "Use when" clause anchored to a distinctive app name, but it relies on one generic verb ("Manage") and a tautological trigger that only fires when the user already names AMcards. Adding concrete action verbs and natural synonyms like "digital business cards" would lift specificity, trigger quality, and completeness.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Send cards and campaigns, create and delete contacts, list templates and credit transactions".

Add natural trigger synonyms users would actually say — "digital business cards", "business card", "drip campaigns", "networking" — so the skill fires even when AMcards isn't named.

Expand the "Use when" clause to cover concrete scenarios, e.g. "Use when the user wants to send a digital business card, manage AMcards contacts, or run a drip campaign".

DimensionReasoningScore

Specificity

"Manage Cards, Users, Templates, Contacts, Groups" names the domain and five concrete objects, but the only verb is the generic "Manage" rather than several specific actions. It exceeds the minimal score-2 anchor (bare domain mention) but does not list the distinct concrete actions the score-4 anchor requires.

3 / 5

Completeness

Both parts are present: a clear "what" ("Manage Cards, Users, Templates, Contacts, Groups") and an explicit "Use when the user wants to interact with AMcards data" clause. Not a 5 because the "when" is circular — it only fires if the user already says "AMcards" — and lacks concrete trigger phrases like business cards or campaigns.

4 / 5

Trigger Term Quality

Relevant keywords like "Cards", "Contacts", "Templates", and "AMcards" are present, but common natural variations are missing — users would say "digital business cards", "send a card", "campaigns", or "networking", none of which appear. This matches the anchor for some relevant keywords without synonyms.

3 / 5

Distinctiveness Conflict Risk

"AMcards" is a distinct niche application name with minimal conflict risk, but the generic nouns "Cards", "Users", "Contacts", and "Groups" create minor overlap risk with other contact- or card-management skills. Mostly distinct rather than a fully clear niche.

4 / 5

Total

14

/

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

Reviewed

Table of Contents

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.