org-chart-creator
Org Chart Creator - Auto-activating skill for Visual Content. Triggers on: org chart creator, org chart creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/org-chart-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 essentially just restates the skill name with no substantive content. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use the skill. The repeated trigger term 'org chart creator' suggests a template was filled in without thought.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates organizational hierarchy diagrams showing reporting structures, team compositions, and role relationships'.
Add a 'Use when...' clause with natural trigger terms like 'org chart', 'organization chart', 'organizational structure', 'hierarchy diagram', 'reporting structure', 'team structure', 'company hierarchy'.
Remove the duplicated trigger term and replace the boilerplate template language with a genuine description of the skill's capabilities and output formats.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Org Chart Creator') without describing any concrete actions. There are no specific capabilities listed like 'creates hierarchical diagrams', 'adds roles and reporting lines', or 'exports org chart images'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or equivalent trigger guidance). The auto-activating mention is not a substitute for explicit trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'org chart creator' repeated twice. It misses natural variations users would say like 'organization chart', 'organizational structure', 'hierarchy diagram', 'reporting structure', 'team structure', or 'company hierarchy'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'org chart' is somewhat specific to a niche domain, which provides some distinctiveness. However, the vague 'Visual Content' category and lack of specific actions could cause overlap with other diagramming or visualization 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 an empty shell with no actual instructional content. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any concrete guidance, code examples, or workflows for creating org charts. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable examples of org chart creation using Mermaid syntax (e.g., `graph TD; CEO-->VP1; CEO-->VP2;`) or another specific tool
Include a step-by-step workflow: gather hierarchy data → choose layout → generate diagram code → validate rendering → export
Remove all meta-description sections (When to Use, Example Triggers, Capabilities) and replace with actual instructional content showing how to create org charts
Add examples of common org chart patterns (hierarchical, matrix, flat) with copy-paste ready code snippets
| 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 information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of org chart syntax (e.g., Mermaid), no templates. The skill describes rather than instructs, offering only vague promises 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 sequence, no validation checkpoints. The content merely states it 'provides step-by-step guidance' without including any steps. | 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 navigation to deeper content. The sections that exist are all boilerplate with no real information. | 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
b8a3b3e
- 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.