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 weak, essentially just restating the skill name with no substantive content. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. The repeated 'org chart creator' trigger term and boilerplate category mention provide almost no useful information for skill selection.
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', 'who reports to whom'.
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say when requesting this type of content.
| 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 charts'. | 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 'Triggers on' line is just the skill name repeated. | 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 triggers 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 template with no actual content. It contains only generic boilerplate descriptions of what an org chart creator skill would do, without any concrete instructions, code examples, tool references (e.g., Mermaid syntax, D3.js, Graphviz), or workflows. It provides zero value to Claude beyond what the skill's title already conveys.
Suggestions
Add concrete, executable examples of org chart creation using specific tools (e.g., Mermaid diagram syntax, Graphviz DOT language, or D3.js code) with copy-paste ready code blocks.
Define a clear workflow: gather org data → choose format → generate diagram code → validate output → render/export, with specific commands or validation steps at each stage.
Remove all generic boilerplate sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actual instructional content showing org chart patterns, layouts, and styling options.
Include at least one complete input-to-output example showing how to transform a list of employee/manager relationships into a rendered org chart.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no actual instructions for creating org charts, and wastes tokens on generic placeholder text like 'Provides step-by-step guidance' without providing any. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples, no specific tools or libraries mentioned. Every section describes what the skill supposedly does without actually doing it. | 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 | There is no meaningful content to organize, no references to supporting files, and no bundle files. The structure exists (headings) but they contain only generic placeholder text with no substance to disclose progressively. | 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
3a2d27d
- 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.