CtrlK
BlogDocsLog inGet started
Tessl Logo

zapier-make-patterns

You are a no-code automation architect who has built thousands of Zaps and Scenarios for businesses of all sizes. You've seen automations that save companies 40% of their time, and you've debugged disasters where bad data flowed through 12 connected apps.

24

Quality

14%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/zapier-make-patterns/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

11%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a skeleton or template that was never filled in. Pattern names are listed without any concrete guidance, anti-patterns are empty headers, and the Sharp Edges table is populated with placeholder text ('Issue') and truncated solution fragments. The content provides virtually no actionable information for Claude to use when helping users with Zapier or Make automations.

Suggestions

Fill in each Pattern section with concrete, step-by-step examples showing actual Zapier/Make configurations (e.g., specific trigger/action pairs, field mappings, filter conditions) rather than just naming the pattern.

Replace the placeholder Sharp Edges table with real issues and complete, actionable solutions — e.g., 'Zapier webhook timeout after 30s → Solution: Use a queued architecture with async polling'.

Add content to each Anti-Pattern section explaining what the problem looks like and how to fix it, with specific examples from Zapier/Make interfaces.

Remove the persona/narrative introduction and capabilities list, replacing them with a concise overview of when to use Zapier vs Make with a decision table or flowchart.

DimensionReasoningScore

Conciseness

The opening paragraphs explain Claude's persona and 'core insight' in a verbose, padded way that adds no actionable value. The capabilities list is redundant tagging. However, the content is relatively short overall, preventing a score of 1.

2 / 5

Actionability

There is zero concrete, executable guidance anywhere in the skill. Patterns are named but never defined with steps, code, or examples. The Sharp Edges table contains placeholder text ('Issue') with truncated solution fragments that are not actionable. Anti-patterns are listed as headers with no content beneath them.

1 / 5

Workflow Clarity

Patterns like 'Multi-Step Sequential Pattern' and 'Conditional Branching Pattern' are named but contain only one-line descriptions with no steps, no sequences, and no validation checkpoints. The Sharp Edges table is filled with placeholder content ('Issue', 'Issue') making it incoherent.

1 / 5

Progressive Disclosure

There is some section-level structure (Patterns, Anti-Patterns, Sharp Edges), but no references to external files, no bundle files, and content that should be elaborated is instead left as empty stubs. The structure exists but contains no meaningful navigable content.

2 / 5

Total

6

/

20

Passed

Description

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

This description is written as a first-person persona backstory rather than a functional skill description, violating the third-person voice requirement and failing to communicate concrete capabilities or trigger conditions. It contains no actionable 'what' or 'when' information, making it nearly useless for skill selection among multiple options. The only redeeming quality is the mention of domain-specific terms like 'Zaps' and 'Scenarios' that hint at the automation platform context.

Suggestions

Rewrite in third person with concrete actions, e.g., 'Designs and debugs no-code automation workflows using Zapier (Zaps) and Make (Scenarios), including trigger configuration, multi-step workflows, data mapping, and error handling.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Zapier, Make, workflow automation, app integrations, Zaps, Scenarios, or connecting apps without code.'

Remove the persona narrative and quantitative claims ('40% of their time', 'thousands of Zaps') which add no functional value for skill selection.

DimensionReasoningScore

Specificity

The description contains no concrete actions whatsoever. It uses vague language like 'built thousands of Zaps and Scenarios' and 'debugged disasters' without specifying what the skill actually does (e.g., design workflows, configure triggers, map fields).

1 / 5

Completeness

There is no clear 'what does this do' beyond vague references to building automations, and there is no 'when should Claude use it' clause at all. The description reads as a persona backstory rather than a functional skill description.

1 / 5

Trigger Term Quality

It includes some relevant domain keywords like 'Zaps', 'Scenarios', 'no-code automation', and 'connected apps' that users might mention. However, it misses natural trigger terms like 'Zapier', 'Make', 'workflow', 'integration', 'automate', or specific app names.

3 / 5

Distinctiveness Conflict Risk

While 'Zaps and Scenarios' hints at Zapier/Make specifically, the description is so vague about actual capabilities that it could overlap with any general automation, integration, or workflow skill. The persona framing adds no distinctiveness.

2 / 5

Total

7

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.