Name: zapier-make-patterns
Rating: 28.799999999999997 (1 reviews)
Author: administrakt0r

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.

Quality

21%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

7%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 a broken, half-generated skeleton: a duplicated persona paragraph, a truncated sentence, empty anti-pattern headers, and a Sharp Edges table filled with placeholder 'Issue' text and commented-out stubs. It provides no executable guidance and no real workflow.

Suggestions

Fill the Anti-Patterns and Sharp Edges sections with concrete explanations and fixes (e.g. why typed dropdown values fail, how to add error-handling routes, how to avoid hardcoded IDs) instead of empty headers and placeholder 'Issue' cells.

Replace the abstract pattern one-liners with executable examples — actual Zap/Make module configurations, trigger/action mappings, or step-by-step build sequences with validation checkpoints.

Remove the duplicated persona paragraph and complete the truncated 'when it needs to g...' sentence, then add a verification step for batch automation runs.

Dimension	Reasoning	Score
Conciseness	The body is short, but it opens with a persona paragraph duplicated from the frontmatter that is pure padding; beyond that it is sparse rather than verbose, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	There is no code, no commands, and no concrete steps: patterns are one-line abstractions, anti-patterns are empty headers, and the Sharp Edges table is broken placeholders ('Issue' repeated, commented-out solution headers), matching 'entirely vague or abstract; no concrete code or commands'.	1 / 5
Workflow Clarity	No sequenced workflow exists — only abstract pattern names — and there is no validation in a domain (Zap/Scenario automation) involving batch operations, which the rubric caps at 3; this is worse, fitting 'steps missing or incoherent; no sequence; no validation'.	1 / 5
Progressive Disclosure	No bundle files exist and section headers provide structure, but the content within sections is broken or placeholder (truncated sentence, empty anti-patterns, repeated 'Issue' cells), so organization is only partially effective.	3 / 5
	Total	8 / 20 Passed

Description

35%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 is a second-person persona prompt rather than a capability statement: it tells Claude who to be, not what the skill does or when to invoke it. It names a distinct niche but lacks concrete actions and any 'Use when' trigger guidance.

Suggestions

Rewrite in third person as a capability statement (e.g. 'Designs, builds, and debugs Zapier Zaps and Make Scenarios...') and drop the persona biography.

Add an explicit 'Use when...' clause listing natural trigger phrases (Zapier, Make, Zap, Scenario, automate workflow, no-code integration).

Replace abstract claims ('built thousands of Zaps') with the concrete actions the skill performs (route triggers, branch conditions, transform data, handle errors).

Dimension	Reasoning	Score
Specificity	The description names the domain (Zaps, Scenarios, no-code automation) but frames it as a persona ('You are a no-code automation architect who has built thousands of Zaps') rather than stating concrete actions the skill performs; the second-person voice triggers the rubric's -1 specificity penalty, dropping it from 2 to 1.	1 / 5
Completeness	The 'what' is a persona biography rather than a capability statement, and the 'when' is entirely absent (no 'Use when...' clause), matching the 'vague what and no when' anchor; not a 1 because the domain is at least identified.	2 / 5
Trigger Term Quality	'Zaps', 'Scenarios', and 'no-code automation' are relevant keywords, but they are buried in persona narrative with no 'Use when' framing and miss common synonyms (Zapier, Make), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Zapier/Make automation is a clear niche with distinct triggers and only minor overlap risk with adjacent workflow-automation skills; not a 5 because the persona framing dilutes the distinct trigger signal.	4 / 5
	Total	10 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zapier-make-patterns/SKILL.md
Commit: 900c504

Reviewed: 2 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.