CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baselinker-automation

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

52

Quality

66%

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

Quality

Content

61%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 well-structured with concrete, mostly executable tool-call examples and a clear setup-to-execution sequence. Its main weaknesses are repeated 'search first' guidance and a missing post-execution validation loop for batch tool calls.

Suggestions

Consolidate the 'search tools first' guidance into one place (e.g. Pitfalls only) to remove repetition across Prerequisites, Tool Discovery, and Step 1.

Add a post-execution validation step after RUBE_MULTI_EXECUTE_TOOL (e.g. inspect responses for errors/pagination tokens and retry on failure) to satisfy the batch-operations feedback-loop expectation.

Consider moving the detailed Known Pitfalls or Quick Reference into a reference file if the body grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats 'Always search first / RUBE_SEARCH_TOOLS first' across Prerequisites, Tool Discovery, Step 1, and Known Pitfalls, and the Tool Discovery section duplicates Step 1, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Concrete tool-call blocks with real parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) are mostly executable; argument placeholders are justified because schemas are dynamic, fitting 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

Steps are sequenced with an ACTIVE-connection checkpoint, but RUBE_MULTI_EXECUTE_TOOL is a batch operation with no post-execution validation or error-retry feedback loop, so the batch-operations cap holds at 3.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-organized file with clear sections and one external doc link, no nested references — good structure with minor organization gaps rather than the ideal one-level-deep reference pattern.

4 / 5

Total

14

/

20

Passed

Description

57%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 a distinct product niche and gives one concrete directive, but lacks a 'Use when...' trigger clause and enumerates no specific Baselinker operations. It is serviceable but not comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when managing Baselinker orders, inventory, or couriers'.

List 1-2 concrete Baselinker operations (e.g. orders, parcels, inventory) to lift specificity above generic 'tasks'.

Include common synonyms or phrasings users might say (e.g. 'Baselinker orders', 'Baselinker shipments') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Baselinker tasks') and mechanism ('Rube MCP (Composio)') plus one concrete directive ('Always search tools first'), but does not enumerate specific operations, matching the 'domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

It clearly states what the skill does ('Automate Baselinker tasks via Rube MCP') but provides no 'when to use' trigger; the missing 'Use when...' clause caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

'Baselinker' is a natural user term, but the rest ('Rube MCP', 'Composio', 'current schemas') is technical jargon with no 'Use when' phrasing or synonyms, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'Baselinker' is a specific named product niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 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

ComposioHQ/awesome-claude-skills

Path

composio-skills/baselinker-automation/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.