000-jeremy-content-consistency-validator
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 000-jeremy-content-consistency-validatorValidate messaging consistency across website, GitHub repos, and local documentation generating read-only discrepancy reports. Use when checking content alignment or finding mixed messaging. Trigger with phrases like "check consistency", "validate documentation", or "audit messaging".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
22%This skill is a skeleton that describes what should happen without providing any concrete implementation guidance. It lacks executable code, specific commands, or detailed examples that would enable Claude to actually perform content consistency validation. The instructions read like a high-level requirements document rather than actionable skill content.
Suggestions
Add concrete code examples showing how to fetch and compare content from different sources (e.g., WebFetch calls, file reading patterns, diff generation)
Provide a specific example of input sources and expected output report format with actual sample content
Include validation checkpoints in the workflow, such as 'verify source accessibility before comparison' and 'validate report structure before saving'
Replace the vague Resources section with actual links to relevant documentation or remove it entirely
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary filler like 'This skill provides automated assistance for the described functionality' which adds no value. The Resources section lists vague concepts rather than actionable references. | 2 / 3 |
Actionability | Instructions are entirely abstract with no concrete code, commands, or specific examples. Steps like 'Extract key messaging' and 'Compare content systematically' provide no executable guidance on how to actually perform these actions. | 1 / 3 |
Workflow Clarity | While steps are numbered, there are no validation checkpoints, no feedback loops for error recovery, and no concrete details about what tools or methods to use at each step. The workflow is too vague to follow. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content lacks substance to serve as a useful overview. The skill defers too much to external files without providing actionable quick-start content. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a well-crafted skill description that excels in completeness and trigger term quality by explicitly stating both what the skill does and when to use it with concrete trigger phrases. The specificity could be slightly improved by listing more concrete actions beyond validation and report generation, but overall this description would effectively help Claude select this skill from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (messaging consistency) and mentions specific sources (website, GitHub repos, local documentation) and output type (read-only discrepancy reports), but doesn't list multiple concrete actions beyond 'validate' and 'generate reports'. | 2 / 3 |
Completeness | Clearly answers both what (validate messaging consistency across multiple sources, generate discrepancy reports) and when (explicit 'Use when' clause with triggers and a 'Trigger with phrases' section providing concrete examples). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'check consistency', 'validate documentation', 'audit messaging', plus includes terms like 'content alignment' and 'mixed messaging' that users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on cross-platform messaging consistency validation with distinct triggers; unlikely to conflict with general documentation or content skills due to the specific 'consistency/alignment/audit' focus. | 3 / 3 |
Total | 11 / 12 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.