CtrlK
BlogDocsLog inGet started
Tessl Logo

beeminder-automation

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

53

Quality

60%

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

Quality

Content

67%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 delivers concrete, executable RUBE_* workflows with clear sequencing and a pre-execution connection validation checkpoint. Its main weaknesses are repeated 'search first' directives and the absence of an explicit post-execution error-recovery loop for batch operations.

Suggestions

Consolidate the 'always search tools first' guidance into a single Prerequisites or Pitfalls statement instead of repeating it across four sections.

Add an explicit post-execution feedback loop for RUBE_MULTI_EXECUTE_TOOL (check results for errors/pagination, re-search and retry on schema mismatches) to strengthen workflow clarity for batch operations.

Consider moving the detailed Core Workflow Pattern and Quick Reference into a separate reference file to better separate overview from operational detail.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized sections, but the directive to search tools first is repeated across Prerequisites, Setup, Tool Discovery, Core Workflow, and Known Pitfalls, creating noticeable redundancy that could be tightened.

3 / 5

Actionability

Concrete RUBE_* tool-call blocks with real parameter structures are provided throughout; placeholders like session IDs and tool slugs are justified by dynamic discovery, leaving only minor gaps versus fully copy-paste-ready code.

4 / 5

Workflow Clarity

Setup, discovery, and execution are clearly sequenced with an explicit ACTIVE-status validation checkpoint before tool execution, but no post-execution error-recovery feedback loop is specified for the batch RUBE_MULTI_EXECUTE_TOOL path.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections within a single self-contained file with no nested references, though the ~80-line body could split detailed execution patterns into a reference file.

4 / 5

Total

15

/

20

Passed

Description

53%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 the Beeminder niche and a key procedural directive, but lacks an explicit "Use when..." trigger clause and specific operation enumeration. It is distinct and on-domain but stops at mid-range completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause naming concrete user cues, e.g. 'Use when the user wants to log goals, track datapoints, or automate Beeminder via Composio.'

List 1-2 concrete Beeminder operations (e.g. create datapoints, manage goals) instead of the generic 'Automate Beeminder tasks' to raise specificity.

Include natural synonyms or phrasings a user might say ('Beeminder goals', 'datapoints', 'derail') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Automate Beeminder tasks" names the domain and pairs it with the concrete procedural action "Always search tools first for current schemas", but does not enumerate specific operations, matching the anchor naming domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

A clear "what" is stated (automate Beeminder tasks via Rube MCP) but there is no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

The natural term "Beeminder" is present alongside "Rube MCP" and "Composio", but common user-facing synonyms or variations are missing, fitting the anchor for some relevant keywords lacking variations.

3 / 5

Distinctiveness Conflict Risk

The Beeminder-specific niche is distinct with clear triggers, with only minor overlap risk against sibling Rube/Composio per-toolkit skills, matching the mostly-distinct anchor.

4 / 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.