code-of-conduct-generator
Code Of Conduct Generator - Auto-activating skill for Technical Documentation. Triggers on: code of conduct generator, code of conduct generator Part of the Technical Documentation skill category.
84
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/code-of-conduct-generator/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 essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other documentation skills in a large skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Generates CODE_OF_CONDUCT.md files with customizable sections for standards, enforcement, and scope based on templates like Contributor Covenant.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a code of conduct, community guidelines, contributor behavior policy, or CODE_OF_CONDUCT.md for a project.'
Remove the duplicate trigger term and expand with varied natural phrases users might say, such as 'community standards', 'project conduct rules', 'open source behavior guidelines'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Code Of Conduct Generator') and its category ('Technical Documentation') but does not describe any concrete actions like 'generates community guidelines', 'creates contributor behavior policies', or 'customizes enforcement sections'. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'code of conduct generator' repeated twice. It misses natural user phrases like 'community guidelines', 'contributor covenant', 'behavior policy', 'open source conduct rules', or 'CODE_OF_CONDUCT.md'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'code of conduct' is fairly specific and unlikely to conflict with most other skills, but the lack of detail and the broad 'Technical Documentation' category label could cause overlap with other documentation generation 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 placeholder with no substantive content. It contains only generic boilerplate that describes what the skill would do without actually providing any actionable guidance, templates, examples, or workflows for generating a code of conduct. It fails on every dimension of the rubric.
Suggestions
Add a concrete code of conduct template (e.g., Contributor Covenant) with customizable sections and placeholder values that Claude can fill in based on project context.
Include a clear workflow: 1) Gather project info (name, scope, contact), 2) Select template variant, 3) Generate the document, 4) Validate required sections are present.
Provide at least one complete example output showing a finished CODE_OF_CONDUCT.md file.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with direct, actionable instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'code of conduct generator' excessively, and provides zero substantive information about how to actually generate a code of conduct. | 1 / 3 |
Actionability | There are no concrete steps, no executable code, no templates, no examples of actual code of conduct output, and no specific commands. The entire skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without delivering any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it provides 'step-by-step guidance' but never actually includes any steps. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no bundle files exist, and the content is a monolithic block of generic placeholder text with no meaningful structure or navigation to deeper 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
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.