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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill org-chart-creator36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/org-chart-creator/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 essentially a placeholder with no substantive content. It names the skill and category but provides zero information about capabilities, use cases, or meaningful trigger terms. The repeated 'org chart creator' trigger term suggests auto-generated or template content that was never properly filled in.
Suggestions
Add specific actions the skill performs, e.g., 'Creates organizational hierarchy diagrams showing reporting relationships, team structures, and department layouts'
Add a 'Use when...' clause with natural trigger terms like 'organization chart', 'team hierarchy', 'reporting structure', 'who reports to whom', 'company structure diagram'
Remove the redundant trigger term and replace with varied natural language users would actually say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Org Chart Creator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating, editing, visualizing, 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. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'org chart creator' repeated twice, which is redundant. Missing natural variations users would say like 'organization chart', 'hierarchy diagram', 'team structure', 'reporting structure', or 'organizational hierarchy'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'org chart' is fairly specific to organizational hierarchy diagrams, 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 entirely meta-content that describes what a skill should do without providing any actual instruction on creating org charts. It contains no executable code, no Mermaid syntax examples, no concrete guidance, and no real value for Claude attempting to help users create organizational charts.
Suggestions
Add concrete Mermaid syntax examples showing how to create org charts with different structures (hierarchical, matrix, etc.)
Include copy-paste ready code blocks demonstrating common org chart patterns like 'graph TD; CEO --> VP1; CEO --> VP2'
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual org chart creation instructions
Add a quick reference section showing org chart node styling, connection types, and layout options
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about org chart creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no examples of actual org chart creation. The content describes what the skill supposedly does but never shows how to actually create an org chart. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for creating org charts. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples, and no links to actual implementation guides or syntax references for org chart tools like Mermaid. | 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.