make-scenario-creator
Make Scenario Creator - Auto-activating skill for Business Automation. Triggers on: make scenario creator, make scenario creator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
97%
1.05xAverage 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/make-scenario-creator/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 minimal and fails to communicate what the skill does or when it should be used. It reads like an auto-generated stub with no concrete actions, no natural trigger terms, and no explicit usage guidance. The only slight positive is the mention of 'Make' which hints at the Make.com platform, providing marginal distinctiveness.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Make.com automation scenarios, configures module connections, sets up triggers and webhooks, and defines data mappings between integrated apps.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Make.com scenarios, automation workflows, integrating apps, or building no-code automations.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'Make.com', 'automation scenario', 'workflow builder', 'integrate services', 'no-code automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Make Scenario Creator' and 'Business Automation' but provides no concrete actions. It doesn't describe what the skill actually does—no mention of creating workflows, connecting apps, configuring triggers, or any specific capabilities. | 1 / 3 |
Completeness | The 'what' is essentially absent—it only names itself without explaining capabilities. The 'when' is missing entirely; there is no 'Use when...' clause or equivalent explicit trigger guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'make scenario creator' repeated twice. It lacks natural keywords users would say like 'automation workflow', 'Make.com', 'integrate apps', 'scenario', 'webhook', or 'automate tasks'. The repetition adds no value. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Make Scenario Creator' provides some specificity to the Make.com platform, which narrows the domain somewhat. However, 'Business Automation' is very broad and could overlap with many other automation-related skills. | 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 entirely a placeholder/template with no actual instructional content. It describes what a Make scenario creator skill would do without providing any concrete guidance, code examples, API references, or workflow steps. It is essentially a self-referential description that teaches Claude nothing it couldn't infer from the skill name alone.
Suggestions
Add concrete, executable examples of Make (Integromat) scenario JSON configurations or API calls for creating scenarios programmatically.
Define a clear workflow with specific steps: e.g., 1) Define modules, 2) Configure connections, 3) Set up data mapping, 4) Validate scenario, 5) Activate—with actual code/config for each step.
Remove all meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable content like Make API endpoints, scenario templates, and common module configurations.
Add specific examples of common business automation scenarios (e.g., email-to-spreadsheet pipeline) with complete Make scenario definitions that Claude can adapt.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of Make scenario configurations. The content only describes what the skill could do in vague terms like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure. There are no references to detailed files, no quick-start section, and no organized navigation to deeper 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.