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.
34
0%
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/18-visual-content/process-flow-generator/SKILL.mdQuality
Discovery
0%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 essentially a placeholder that repeats the skill name and category without providing any meaningful information about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinctiveness from other visual content skills.
Suggestions
Add specific concrete actions such as 'Generates process flow diagrams, workflow visualizations, and step-by-step flowcharts from textual descriptions'.
Add an explicit 'Use when...' clause with natural trigger terms like 'flowchart', 'workflow diagram', 'process map', 'sequence of steps', 'visualize a process'.
Remove the duplicate trigger term and replace with varied, natural keywords users would actually say, including common synonyms and file format references if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Visual Content') and repeats the skill name ('Process Flow Generator') but does not describe any concrete actions like 'create flowcharts', 'generate diagrams', or 'visualize workflows'. It is essentially a label, not a capability description. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the name, and the 'when' clause is just a duplicate trigger phrase rather than meaningful guidance. There is no explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'process flow generator' repeated twice. It misses natural user phrases like 'flowchart', 'workflow diagram', 'process diagram', 'flow chart', 'sequence diagram', or 'visualize steps' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Visual Content' is extremely broad and could overlap with any image, chart, diagram, or graphic skill. Without specific actions or file types, this would easily conflict with other visual or diagramming skills. | 1 / 3 |
Total | 4 / 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 placeholder that contains no actual instructional content. It only describes itself in abstract, repetitive terms without providing any concrete guidance on generating process flows, no code examples (e.g., Mermaid syntax), no workflow steps, and no references to detailed resources. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of process flow generation (e.g., Mermaid diagram syntax for common flow patterns like sequential, branching, and parallel flows).
Define a clear workflow: 1) Identify process steps, 2) Choose diagram type, 3) Generate Mermaid/PlantUML code, 4) Validate rendering, 5) Iterate on layout.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual instructional content.
Add references to detailed resources for advanced patterns (e.g., a PATTERNS.md for complex flow types, or EXAMPLES.md with real-world process flow diagrams).
| 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 section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of process flow generation, no Mermaid syntax, no diagram templates. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, validation checkpoints, or any procedural content. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured navigation, and no content worth disclosing progressively. The document is a shallow placeholder with no depth or organization of real 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.