code-of-conduct-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill code-of-conduct-generatorCode 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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The redundant trigger terms and lack of concrete actions make it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Generates customizable code of conduct documents for open source projects, including contributor expectations, enforcement guidelines, and reporting procedures.'
Include a proper 'Use when...' clause with natural trigger terms: 'Use when creating community guidelines, contributor codes of conduct, project behavior policies, or when users mention CoC, community standards, or contributor expectations.'
Add variations of trigger terms users might naturally use: 'code of conduct', 'CoC', 'community guidelines', 'contributor guidelines', 'behavior policy', 'project rules', 'open source conduct'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Code Of Conduct Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, customizing, or generating specific content. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause and merely repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('code of conduct generator' listed twice) and overly narrow. Missing natural variations users might say like 'community guidelines', 'contributor guidelines', 'project rules', 'CoC', or 'behavior policy'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'code of conduct' is a specific document type that provides some distinctiveness, the vague 'Technical Documentation' category and lack of specific triggers could cause overlap with other documentation generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual instructional content. It describes what a code of conduct generator skill would do in abstract terms but provides no templates, examples, sections to include, customization options, or any actionable guidance. The entire content could be replaced with a single sentence without losing information.
Suggestions
Add a concrete code of conduct template with standard sections (Purpose, Expected Behavior, Unacceptable Behavior, Reporting, Enforcement, Attribution)
Include 2-3 example variations (e.g., minimal, standard, comprehensive) with actual markdown content
Provide a step-by-step workflow: 1) Determine scope, 2) Select template, 3) Customize sections, 4) Add contact info, 5) Review and finalize
Remove all generic boilerplate about 'automated assistance' and 'best practices' - replace with actual best practices content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about code of conduct generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance, code, templates, or examples of actual code of conduct content. The skill describes what it does abstractly but provides zero executable or actionable instructions for generating a code of conduct. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no process for generating a code of conduct, no validation checkpoints, and no guidance on what sections to include or how to customize them. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, templates, or examples. There's nothing to disclose progressively because there's no substantive content. | 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.