CtrlK
BlogDocsLog inGet started
Tessl Logo

weekly-recap

Collect a source-backed weekly recap from GitHub, chat, calendar, docs, and other configured tools, using best-effort collection when sources are unavailable. Produces a source recap, a disposable status update, and a lean list of brag candidates. Use for weekly summaries, weekly reports, status reports, standup notes, progress updates, accomplishments lists, or questions about what the user did this week.

83

2.55x
Quality

86%

Does it follow best practices?

Impact

92%

2.55x

Average score across 2 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A highly actionable, well-structured instruction skill with executable gh commands and concrete output templates. The chief gaps are the absence of an explicit error-recovery feedback loop in the workflow and some inlined material that could be split into reference files.

Suggestions

Add an explicit validate-fix-retry loop (e.g., on a failed gh query or auth warning, diagnose and retry once before skipping) to raise workflow_clarity.

Move the detailed gh command catalog and/or the three output-shape templates into reference files referenced one level deep from SKILL.md to improve progressive_disclosure.

Tighten the brag-candidate criteria and guardrails lists to remove phrasing that restates earlier instructions, improving conciseness.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no 'what is GitHub/Slack' padding), using compact templates and a YAML block, though the brag-candidate criteria and guardrails could be tightened slightly.

4 / 5

Actionability

Provides fully executable, copy-paste-ready gh commands with complete --json field lists, concrete tools.yaml defaults, exact cross-reference rules, and precise output-shape templates covering the common cases.

5 / 5

Workflow Clarity

An 8-step sequenced workflow with real checkpoints (auth/CLI check, warn-and-skip, stop-when-no-evidence, mark 'claimed, not found'), but it lacks an explicit validate-fix-retry feedback loop for the batch collection.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references, but at ~180 lines with the full gh-command catalog and all output templates inlined, some material could be externalized into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what it does, names its sources and three distinct outputs, and provides a comprehensive 'Use for' trigger clause. The main weakness is mild trigger overlap with general reporting skills and a narrow action-verb vocabulary.

DimensionReasoningScore

Specificity

Names the domain, multiple sources (GitHub, chat, calendar, docs), and three concrete outputs (source recap, status update, brag candidates), but the action vocabulary is narrow (collect/produces) rather than a breadth of distinct actions.

4 / 5

Completeness

Explicitly answers both 'what' (collect source-backed recap producing three named outputs) and 'when' (Use for weekly summaries, reports, standup notes, etc.) with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use for...' clause lists comprehensive natural trigger phrases — weekly summaries, weekly reports, status reports, standup notes, progress updates, accomplishments lists, and 'what did I do this week' — covering synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

The weekly, source-backed, brag-candidate framing is a clear niche, but generic triggers like 'status reports', 'standup notes', and 'progress updates' carry minor overlap risk with general reporting/standup skills.

4 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
javiermolinar/dope-brag
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.