zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
99%
0.99xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/zapier-integration-helper/SKILL.mdQuality
Discovery
7%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 extremely weak across all dimensions. It reads as auto-generated boilerplate with no substantive content—just a skill name, a duplicated trigger phrase, and a category label. It provides no information about what the skill actually does, when it should be used, or what user requests should activate it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Zapier integrations, configures triggers and actions between apps, troubleshoots zap workflows, and sets up multi-step automations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions Zapier, zaps, connecting apps, automating workflows, webhooks, or integrating services like Slack, Gmail, or Sheets.'
Remove the duplicated trigger term and replace with diverse natural keywords users would actually say, such as 'automate tasks', 'connect two apps', 'set up a zap', 'workflow automation', or specific app integration names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the tool ('Zapier Integration Helper') and a vague category ('Business Automation') without describing what it actually does—no mention of creating zaps, connecting apps, setting up triggers, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the redundant 'zapier integration helper' repeated twice. There are no natural user keywords like 'automate', 'connect apps', 'workflow', 'zap', 'trigger', 'webhook', or names of common integrations users might mention. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Zapier' provides some specificity that distinguishes it from generic automation skills, but 'Business Automation' is extremely broad and could overlap with many other automation-related skills. The lack of concrete scope makes conflict risk moderate. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a template placeholder with no actual instructional content. It repeatedly names the skill and describes what it would do in theory but provides zero actionable guidance on Zapier integrations, no code examples, no API details, no workflow steps, and no references to supplementary materials. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of Zapier integration patterns (e.g., webhook setup, Zap configuration via API, common trigger/action pairs with code snippets).
Define a clear multi-step workflow for common Zapier integration tasks, including validation checkpoints (e.g., test webhook → verify payload → configure action → test end-to-end).
Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than teaching how to perform the task.
Add references to Zapier API documentation, common integration patterns, and link to separate files for advanced topics like error handling or multi-step Zaps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. It explains what triggers the skill, restates the skill name repeatedly, and provides no actual technical content. Every section is boilerplate with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no API references, no configuration examples. The skill claims to provide 'step-by-step guidance' and 'production-ready code' but delivers neither. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The content is entirely descriptive metadata about the skill rather than any operational process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to external files, and no structured navigation. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.