brag-summarize

Append a source-backed, impact-first brag-doc roll-up from repo-local weekly-recap outputs. Use for accomplishments, achievements, wins tracker updates, performance summaries, monthly/quarterly brag summaries, or custom-period roll-ups that append Wins to an existing local brag doc while deduplicating prior claims.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, highly actionable skill with an excellent multi-step workflow that includes proper validation checkpoints, safety guardrails, and error recovery paths. Its main weakness is moderate verbosity—some guardrails and contract terms could be tightened—and the referenced bundle files (TEMPLATE.md, GOALS.md, VOICE.md) are not provided, making it impossible to fully evaluate progressive disclosure. The security-conscious treatment of untrusted source data and the append-only-by-default contract are notable strengths.

Suggestions

Tighten the Guardrails section by consolidating overlapping rules (e.g., the multiple 'do not claim X unless source proves Y' items could be a single rule with examples).

Provide the referenced bundle files (TEMPLATE.md, GOALS.md, VOICE.md) so the skill's progressive disclosure structure is complete and verifiable.

Dimension	Reasoning	Score
Conciseness	The skill is fairly detailed and well-structured, but some sections are verbose for what Claude needs. The theme definitions (Strategic Leadership, Engineering Leverage, etc.) and some guardrails repeat concepts Claude already understands. The contract section could be tighter. However, much of the detail is domain-specific and necessary for correct behavior.	2 / 3
Actionability	The workflow is highly concrete with specific file paths (weekly/YYYY-Www/brag-candidates.md, recap.md), explicit resolution logic for workspace root and target doc, specific parsing instructions (ISO weeks, STAR fields, headline counts), and clear output structure. The example requests ground the skill in real usage. While there's no executable code, this is an instruction-only skill where the guidance is fully actionable.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with explicit validation checkpoints: stop if evidence/target/skill files are missing (step 1), warn on gaps/overlaps (step 3), deduplication with merge warnings (step 5), timestamped backup before writing (step 9), and a comprehensive report step (step 10). Feedback loops are present—e.g., stop and ask if target is ambiguous, warn on rewrite-merge needs, flag partial overlaps for review.	3 / 3
Progressive Disclosure	The skill references TEMPLATE.md, GOALS.md, and VOICE.md as supporting files, which is good progressive disclosure design. However, no bundle files are provided, so we cannot verify these references resolve correctly. The main SKILL.md itself is quite long (~180 lines) and some content like the full theme definitions or detailed guardrails could potentially be split out, though the single-file approach is defensible for a skill of this complexity.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, well-crafted skill description that clearly defines a specific niche (brag-doc roll-ups from weekly recaps), provides comprehensive trigger terms covering natural user language, and explicitly states both what the skill does and when to use it. The description is concise yet information-dense, with distinct terminology that minimizes conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'append a source-backed, impact-first brag-doc roll-up', 'from repo-local weekly-recap outputs', 'deduplicating prior claims', 'append Wins to an existing local brag doc'. These are concrete, well-defined actions.	3 / 3
Completeness	Clearly answers both what ('Append a source-backed, impact-first brag-doc roll-up from repo-local weekly-recap outputs... while deduplicating prior claims') and when ('Use for accomplishments, achievements, wins tracker updates, performance summaries, monthly/quarterly brag summaries, or custom-period roll-ups').	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'accomplishments', 'achievements', 'wins tracker', 'performance summaries', 'monthly/quarterly brag summaries', 'custom-period roll-ups', 'brag doc'. These are terms users would naturally use when requesting this kind of task.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: brag-doc roll-ups from weekly recaps with deduplication. The specificity of 'repo-local weekly-recap outputs', 'brag doc', and 'deduplicating prior claims' makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: javiermolinar/dope-brag
Commit: 2d9f95a

Reviewed: 22 days ago

Table of Contents

Discovery Implementation Validation

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.