beaconstac-automation

Automate Beaconstac 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/beaconstac-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 the platform (Beaconstac) but fails to explain what specific tasks can be automated or when Claude should choose this skill. The operational instruction about searching tools first doesn't help with skill selection.

Suggestions

Add specific capabilities: list concrete Beaconstac actions like 'create QR codes', 'manage digital business cards', 'track analytics', or 'update campaigns'

Add explicit trigger guidance: 'Use when the user mentions Beaconstac, QR code campaigns, digital business cards, or proximity marketing'

Include natural user terms: add keywords users would actually say like 'QR codes', 'business cards', 'NFC tags', or 'beacon marketing'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Beaconstac tasks' without specifying what concrete actions can be performed. No specific capabilities are listed beyond generic 'tasks'.	1 / 3
Completeness	The 'what' is extremely vague ('automate tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger.	1 / 3
Trigger Term Quality	Includes 'Beaconstac', 'Rube MCP', and 'Composio' as domain-specific terms, but lacks natural user language. Users likely wouldn't say 'Rube MCP' or 'Composio' - they'd mention QR codes, digital business cards, or specific Beaconstac features.	2 / 3
Distinctiveness Conflict Risk	'Beaconstac' provides some distinctiveness as a specific platform, but 'automate tasks via MCP' is generic enough to potentially conflict with other Composio/MCP-based 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 teaches Beaconstac automation through Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget by avoiding unnecessary explanations. The main weakness is that tool call examples are structural templates rather than fully executable examples with realistic parameter values.

Suggestions

Provide at least one complete, realistic example with actual Beaconstac-specific parameters (e.g., creating a QR code or managing a campaign) rather than generic placeholders

Show a concrete example response from RUBE_SEARCH_TOOLS to illustrate what 'schema-compliant args' look like in practice

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 Beaconstac or Composio are.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameter structures, but the examples are pseudo-code style rather than fully executable. The tool calls show structure but lack complete, copy-paste ready examples with realistic values.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error prevention guidance.	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: 2 months 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.