org-chart-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill org-chart-creatorOrg Chart Creator - Auto-activating skill for Visual Content. Triggers on: org chart creator, org chart creator Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what the skill actually does, uses redundant trigger terms, and lacks any guidance for when Claude should select it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific capabilities: describe what the skill does (e.g., 'Creates organizational hierarchy diagrams, visualizes reporting structures, generates team charts from employee data').
Add a 'Use when...' clause with explicit triggers: 'Use when the user asks to create an org chart, visualize team hierarchy, show reporting relationships, or diagram organizational structure'.
Expand trigger terms to include natural variations: 'organization chart', 'hierarchy diagram', 'team structure', 'reporting lines', 'company structure', 'management hierarchy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Org Chart Creator') without describing any concrete actions. It doesn't explain 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, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. The 'Triggers on' line is not a proper usage guide. | 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 | While 'org chart' is a somewhat specific domain, the vague 'Visual Content' category and lack of specific capabilities could cause overlap with other diagramming or visualization skills. The narrow trigger terms provide some distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It describes what an org chart skill should do without providing any actionable guidance, code examples, or concrete instructions for creating org charts. The entire content could be replaced with a single Mermaid org chart example and be infinitely more useful.
Suggestions
Add concrete Mermaid syntax examples for creating org charts (e.g., `graph TD; CEO --> CTO; CEO --> CFO;`)
Include at least one complete, executable example showing a typical org chart structure
Remove all generic boilerplate text ('provides automated assistance', 'follows industry best practices') and replace with actual org chart creation guidance
Add specific formatting options and customization patterns for org chart styling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about org charts. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually create org charts. No code examples, no Mermaid syntax, no specific commands or tools - just vague descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. The skill claims to provide 'step-by-step guidance' but contains no actual steps for creating org charts. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, examples, or related documentation. The 'Related Skills' section mentions tags but provides no actual links or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.