CtrlK
BlogDocsLog inGet started
Tessl Logo

make-automation

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

55

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/make-automation/SKILL.md

The canonical home for this skill is make-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 clear workflows and an explicit connection-validation checkpoint, but it is padded with repeated advice and lacks concrete parameter/response examples to make guidance fully executable.

Suggestions

De-duplicate repeated advice (cache enums, search tools first) into a single note and reference it, rather than restating in every section.

Add at least one concrete example of a RUBE_SEARCH_TOOLS call/response and a sample MAKE_GET_OPERATIONS request with real filter parameters and a representative response shape.

Move the lengthy 'Alternative Approaches' and 'Known Pitfalls' detail into a separate reference file, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and avoids explaining basics, but repeats the same advice multiple times ("cache results" appears in languages, timezones, caching strategy, and rate limits; "Always call RUBE_SEARCH_TOOLS first" appears 4-5 times), which could be tightened.

3 / 5

Actionability

Names exact tools and ordered sequences (e.g. MAKE_GET_OPERATIONS, MAKE_LIST_ENUMS_LANGUAGES), but defers specifics to schema lookups and provides no concrete parameter examples or response shapes, leaving guidance incomplete.

3 / 5

Workflow Clarity

Core workflows are clearly sequenced with 'When to use', 'Tool sequence', 'Key parameters', and 'Pitfalls', and setup includes an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running'); minor validation gaps remain in the analysis workflows.

4 / 5

Progressive Disclosure

No bundle files exist and the body is a single well-organized file with clear section headers and a quick-reference table; structure is good, though some reference-like content (detailed pitfalls, alternative approaches) is inlined rather than split out.

4 / 5

Total

14

/

20

Passed

Description

66%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 conveys the skill's purpose and domain with concrete actions and good keyword coverage, but lacks an explicit 'when to use' trigger phrase, capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to automate Make/Integromat scenarios, check operation usage, or look up valid language/timezone values.'

Broaden trigger terms with natural user phrasings like 'Make scenarios', 'Integromat workflows', or 'operation logs'.

Consider naming the read-only nature of the toolkit to sharpen distinctiveness from full Make API skills.

DimensionReasoningScore

Specificity

Names concrete actions ("operations, enums, language and timezone lookups") specific to the Make domain, with only minor gaps in coverage; not quite the exhaustive list needed for a 5.

4 / 5

Completeness

The 'what' is clear ("Automate Make tasks via Rube MCP: operations, enums, language and timezone lookups"), but there is no explicit 'Use when...' trigger clause; the closing "Always search tools first" is a usage instruction, not a trigger, so completeness is capped at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes natural terms and synonyms ("Make (Integromat)", "operations", "language and timezone lookups") but is missing some common phrasings a user might say, so it falls just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to Make automation via Rube MCP/Composio, a clear niche with minor overlap risk against generic automation skills; not perfectly distinct enough for a 5.

4 / 5

Total

15

/

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
administrakt0r/AI-Agents-Safe-Coding-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.