make-scenario-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill make-scenario-creatorMake Scenario Creator - Auto-activating skill for Business Automation. Triggers on: make scenario creator, make scenario creator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when Claude should use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The duplicate trigger term suggests this may be auto-generated boilerplate that was never properly filled in.
Suggestions
Add specific capabilities like 'Creates Make.com automation scenarios, configures module connections, sets up triggers and actions, maps data between apps'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions Make.com, Make scenarios, automation workflows, connecting apps, or building integrations'
Remove the duplicate trigger term and expand with variations users might actually say: 'make automation', 'make.com workflow', 'scenario builder', 'integromat'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Make Scenario Creator' and 'Business Automation' without describing any concrete actions. There are no specific capabilities listed like 'create workflows', 'connect apps', or 'automate tasks'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'make scenario creator, make scenario creator' (duplicated). Missing natural variations users might say like 'automation workflow', 'Make.com', 'integromat', 'connect apps', or 'automate'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Make Scenario Creator' is somewhat specific to the Make.com platform, 'Business Automation' is generic and could overlap with other automation tools like Zapier, n8n, or general workflow skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do rather than any concrete guidance for creating Make scenarios. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete, executable examples of Make scenario JSON structures or API calls for common automation patterns
Include step-by-step workflows for creating specific scenario types (e.g., email-to-spreadsheet automation, webhook triggers)
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual instructions
Add validation steps and common error patterns when building Make scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague platitudes that waste tokens without teaching Claude anything specific. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual Make scenario creation. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, 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 marketing-style text with no structure for learning. There are no references to detailed materials, no links to examples, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.