write
Write blog posts from session insights with multi-perspective analysis.
62
45%
Does it follow best practices?
Impact
88%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./write/skills/write/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is too brief and vague to effectively guide skill selection. It lacks a 'Use when...' clause, leaving Claude without explicit trigger guidance. The term 'session insights' is ambiguous and 'multi-perspective analysis' is jargon that users are unlikely to naturally use.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to turn meeting notes, workshop sessions, or discussion insights into blog content.'
Clarify what 'session insights' refers to (e.g., therapy sessions, meeting notes, workshop takeaways) to reduce ambiguity and improve distinctiveness.
List more specific actions beyond just 'write blog posts', such as 'synthesizes key themes, structures arguments from multiple viewpoints, and formats content for publication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blog posts from session insights) and one action (write blog posts with multi-perspective analysis), but lacks concrete details about what 'session insights' means or what specific actions are performed beyond writing. | 2 / 3 |
Completeness | Provides a partial 'what' (write blog posts from session insights) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes 'blog posts' and 'session insights' as relevant keywords, but 'multi-perspective analysis' is somewhat jargon-like and users are unlikely to use that phrase. Missing common variations like 'blog writing', 'content creation', 'meeting notes to blog', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'session insights' and 'blog posts' provides some specificity, but 'session insights' is ambiguous (therapy sessions? meeting sessions? user sessions?) which could cause overlap with general blog writing or content creation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured overview of a multi-phase writing workflow with good progressive disclosure and clear phase sequencing. However, it leans heavily on abstract notation (mathematical formulas for the Prothesis protocol) and lacks concrete, executable examples of what each phase actually produces, making it more of a conceptual framework than actionable guidance. The content transformation tables are useful but the actual drafting and refinement instructions remain vague.
Suggestions
Replace the mathematical notation for the Prothesis protocol with a concrete example showing actual perspective derivation and synthesis for a sample blog topic.
Add a concrete example of a complete draft structure with sample text for at least the Hook → Context → Framework sections to make Phase 5 actionable.
Remove the 'What Gets Filtered' table — Claude already knows not to include debugging steps and tool invocations in blog posts; this wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary elements like the mathematical notation for the Prothesis protocol phases, the 'When to Use / Skip when' section that over-explains, and the 'What Gets Filtered' table which states obvious things Claude already knows (e.g., don't include debugging steps in blog posts). | 2 / 3 |
Actionability | The workflow provides a clear sequence of phases and references specific tools (/frame, /gap, Edit, Write), but the actual execution guidance is abstract rather than concrete. There are no executable examples of content transformation, no sample draft structure with actual text, and the Prothesis protocol is described in mathematical notation rather than actionable steps. | 2 / 3 |
Workflow Clarity | The phases are clearly sequenced with a summary table and numbered steps, and there are exit conditions for the refinement loop. However, validation is deferred to Phase 7 with no intermediate checkpoints, and the feedback loop in Phase 6 lacks specifics on how to handle structural vs incremental changes beyond a brief mention of option versions. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references to external files: `prothesis/skills/frame/SKILL.md` for the Prothesis protocol and `references/workflow.md` for detailed workflow steps. Content is appropriately split between the overview here and detailed materials elsewhere, with one-level-deep references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jongwony/epistemic-protocols
- Commit
01bfef1
- 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.