CtrlK
BlogDocsLog inGet started
Tessl Logo

beaconstac-automation

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

56

Quality

65%

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 ./composio-skills/beaconstac-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, well-structured, actionable guide with a clear workflow and an explicit connection-validation checkpoint. Its only gap is a missing post-execution verification loop for batch/multi-execute operations.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding about what Beaconstac/Rube is; the only trim is the 'always search first' message repeated across Prerequisites, Setup, Tool Discovery, and Pitfalls, which keeps it just below a 5.

4 / 5

Actionability

Concrete tool calls with real argument shapes (RUBE_SEARCH_TOOLS queries/session, RUBE_MANAGE_CONNECTIONS toolkits, RUBE_MULTI_EXECUTE_TOOL tools/arguments/memory/session_id) are given; the remaining placeholders ('TOOL_SLUG_FROM_SEARCH', 'your_session_id') are justified by the dynamic search-first design, fitting the score-4 anchor.

4 / 5

Workflow Clarity

The Discover → Check connection → Execute sequence is explicit with a validation checkpoint (confirm ACTIVE status before running) and a pitfalls checklist, but there is no post-execution verify/retry feedback loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

A short single-purpose skill (<50 body lines) with no external references needed and well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference), qualifying for the score-5 simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

52%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 clearly identifies its niche (Beaconstac via Rube MCP/Composio) but is generic on actions and omits any 'Use when...' trigger guidance, capping completeness. It is distinguishable but under-specified for triggering.

Suggestions

Add an explicit 'Use when...' trigger clause naming concrete Beaconstac tasks (e.g., QR/NFC campaigns, analytics) so Claude knows when to invoke it.

Replace the generic 'Automate Beaconstac tasks' with 2-3 specific actions (e.g., 'Create and update Beaconstac QR/NFC campaigns, pull analytics, manage dynamic links') to raise specificity.

Include natural user phrasings and synonyms ('Beaconstac campaigns', 'QR codes', 'NFC tags') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Automate Beaconstac tasks' names the domain but the only action is the generic 'Automate ... tasks'; the rest ('Always search tools first') is a behavioral directive rather than a capability, matching the score-2 anchor.

2 / 5

Completeness

The 'what' is clear ('Automate Beaconstac tasks via Rube MCP') but there is no 'Use when...' trigger clause, and the rubric caps a missing explicit trigger at 3.

3 / 5

Trigger Term Quality

It surfaces relevant proper-noun keywords ('Beaconstac', 'Rube MCP', 'Composio') but lacks the natural phrasings a user would actually say, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'Beaconstac' creates a clear niche with a distinct trigger and minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

13

/

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.

Validation15 / 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
ComposioHQ/awesome-claude-skills
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.