amcards-automation

Automate Amcards tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/amcards-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to effectively guide skill selection. It names specific products but fails to explain what concrete actions are possible or when the skill should be used. The procedural instruction about searching tools belongs in the skill body, not the description.

Suggestions

Add specific concrete actions (e.g., 'Send greeting cards, manage contacts, schedule card deliveries') instead of generic 'automate tasks'

Add a 'Use when...' clause with natural trigger terms like 'send cards', 'greeting cards', 'Amcards', 'card automation'

Remove the procedural instruction about searching tools and replace with user-facing capability descriptions

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Amcards tasks' without specifying what tasks or actions are possible. 'Search tools first for current schemas' is a procedural instruction, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('Automate Amcards tasks') and there is no 'when' clause or explicit trigger guidance. The instruction about searching tools is procedural, not a usage trigger.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Amcards', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or user-facing trigger terms.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Amcards, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation skills.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that efficiently guides Claude through Amcards automation via Rube MCP. The workflow is clear with appropriate validation checkpoints, and the content respects token budget. The main weakness is that examples use placeholder syntax rather than fully concrete, executable patterns with real field names.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with at least one concrete example showing actual Amcards-specific arguments

Add a complete end-to-end example showing a specific Amcards task (e.g., sending a card) with real tool slugs and arguments to improve actionability

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Amcards or Composio are.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameter structures, but uses pseudocode-style examples rather than fully executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and known pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides efficient navigation.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 29 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.