make-automation

Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.

1.07x

Quality

62%

Does it follow best practices?

Impact

87%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/make-automation/SKILL.md

Quality

Content

50%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.

A well-structured, single-file MCP-orchestration skill with concrete tool sequences, but it is held back by repeated guidance, deferred parameter details, missing validation loops on batch operations, and no use of separate reference files.

Suggestions

Deduplicate the caching strategy and the 'call RUBE_SEARCH_TOOLS first' guidance into a single authoritative section rather than repeating them 3-5 times.

Add explicit validation/retry checkpoints to the Operations Analysis and Operations Monitoring workflows (e.g., verify response pagination, retry on rate-limit) since they handle batch data.

Move the 'Alternative Approaches', 'Integration with Other Toolkits', and 'Composing Equivalent Workflows' material into separate reference files (e.g., references/alternatives.md) and link to them, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient structured sections without explaining Make/MCP basics, but caching guidance is repeated across multiple sections and 'always call RUBE_SEARCH_TOOLS first' appears 5+ times — could be tightened.	3 / 5
Actionability	Concrete tool names and explicit call sequences are given, but key parameter guidance is deferred ('Check current schema... for available filters', '(check schema for filters)') leaving the user without specific argument details.	3 / 5
Workflow Clarity	Setup has a clear verification checkpoint (confirm ACTIVE before running), but operations workflows involving batch/large data lack explicit validate/retry feedback loops, capping workflow clarity at 3 per the batch-operation guideline.	3 / 5
Progressive Disclosure	The ~200-line body is well-sectioned but entirely monolithic — no bundle files exist and alternative-approach/integration/caching content that could live in separate references is all inlined in SKILL.md.	3 / 5
	Total	12 / 20 Passed

Description

75%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.

A specific, distinct description that clearly states what the skill does, but it lacks an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' sentence would round it out.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to automate Make (Integromat) scenarios, retrieve operations/logs, or validate language and timezone values.'

Include common natural trigger terms like 'Make scenarios', 'scenario logs', or 'Make automation' alongside the existing 'operations' and 'lookups' keywords.

Dimension	Reasoning	Score
Specificity	Names the Make domain via a specific stack (Rube MCP/Composio) and lists multiple concrete actions — 'operations, enums, language and timezone lookups' — giving comprehensive coverage of the toolkit's capabilities.	5 / 5
Completeness	The 'what' is explicit and clear, but there is no 'Use when...' trigger clause — only an instruction to 'Always search tools first' — so per the missing-trigger guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Good keyword coverage including both 'Make' and 'Integromat' plus 'operations' and 'language/timezone lookups', but missing common natural phrases like 'Make scenarios', 'scenario logs', or 'automation' that users would say.	4 / 5
Distinctiveness Conflict Risk	A clearly defined niche (Make/Integromat automation via a specific Rube MCP/Composio toolkit) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/make-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 19 hours 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.