process-flow-generator
Process Flow Generator - Auto-activating skill for Visual Content. Triggers on: process flow generator, process flow generator Part of the Visual Content skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill process-flow-generator36
Quality
3%
Does it follow best practices?
Impact
99%
0.99xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/process-flow-generator/SKILL.mdDiscovery
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, natural trigger terms, or usage guidance. The redundant trigger term and reliance on category membership provide almost no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates visual process flow diagrams, workflow charts, and step-by-step procedural visualizations'
Include a 'Use when...' clause with natural trigger terms like 'flowchart', 'workflow', 'process diagram', 'visualize steps', 'sequence of steps', 'procedure visualization'
Remove the redundant trigger term and replace with diverse natural language variations users would actually say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Process Flow Generator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating diagrams, generating flowcharts, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('process flow generator' listed twice) and represent technical/formal language rather than natural user phrases. Missing common variations like 'flowchart', 'workflow diagram', 'process diagram', 'visualize steps', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'process flow' is somewhat specific, the vague 'Visual Content skill category' reference could overlap with many visualization skills. The lack of specific use cases makes it unclear when this should be chosen over other diagram or visualization tools. | 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 essentially a placeholder template with no substantive content. It describes what a process flow generator skill should do but provides zero actionable guidance, no code examples, no Mermaid/diagram syntax, and no actual instructions for generating process flows. The content fails on all dimensions by being both verbose and empty of useful information.
Suggestions
Add concrete Mermaid or diagram syntax examples showing how to create process flows (e.g., flowchart TD, graph LR)
Include at least one complete, executable example with input description and expected diagram output
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual step-by-step guidance for creating different types of process flows
Add references to diagram tool documentation or related skill files if advanced features exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('Generates production-ready code') but never shows how to actually generate a process flow diagram. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The content lists capabilities but provides no sequence, no validation steps, and no actual process for creating process flows. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no examples, and no structured navigation to additional resources. | 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 | |
- 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.