Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate ready-to-post content from guide updates.
Install with Tessl CLI
npx tessl i github:FlorianBruniaux/claude-code-ultimate-guide --skill guide-recap93
Quality
92%
Does it follow best practices?
Impact
94%
1.17xAverage score across 3 eval scenarios
Quality
Discovery
85%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 is a strong description that clearly defines a specific transformation task (CHANGELOG to social content) with explicit platforms, languages, and timing triggers. The main weakness is trigger term coverage - it could benefit from additional natural language variations users might use when requesting this type of content generation.
Suggestions
Add common trigger term variations like 'release notes', 'announcement', 'social media posts', or 'marketing content' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Transform CHANGELOG entries into social content' with explicit platforms (LinkedIn, Twitter/X, Newsletter, Slack) and languages (FR + EN). Clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Transform CHANGELOG entries into social content') AND when ('Use after releases or weekly to generate ready-to-post content from guide updates'). Explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'CHANGELOG', 'social content', 'LinkedIn', 'Twitter/X', 'releases', but missing common variations users might say like 'release notes', 'announcement', 'social media posts', or 'marketing content'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining CHANGELOG source, social media output, bilingual FR+EN, and release timing. Unlikely to conflict with generic social media or documentation skills due to the specific CHANGELOG-to-social transformation focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing comprehensive, actionable guidance. The 7-step workflow is clearly sequenced with explicit validation checkpoints and error handling. The progressive disclosure is well-executed with clear references to supporting files without burying essential information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for compact reference, avoiding explanations of concepts Claude already knows, and every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides concrete command examples, specific flag syntax, detailed scoring formulas, and explicit output formats. The workflow steps are executable with clear inputs and outputs. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit validation points (Step 5 score threshold check, error handling table). Each step has defined inputs, outputs, and decision points with clear error recovery paths. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, well-organized sections, and clear one-level-deep references to 8 supporting files (templates, examples, reference docs) that are clearly signaled and categorized. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.