weekly-checkin

Cross-domain pattern analysis and strategic reflection for weekly review

Quality

24%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/weekly-checkin/SKILL.md

Quality

Discovery

22%

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 description is too abstract and buzzword-heavy to be effective for skill selection. It lacks concrete actions, explicit trigger conditions, and natural user-facing keywords. The only useful signal is 'weekly review', but even that is not elaborated with trigger guidance.

Suggestions

Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks for a weekly review, weekly summary, retrospective, or end-of-week reflection.'

Replace abstract phrases like 'cross-domain pattern analysis' and 'strategic reflection' with concrete actions, e.g., 'Summarizes accomplishments, identifies recurring themes across projects, and generates actionable insights for the upcoming week.'

Include natural trigger terms users would actually say, such as 'weekly summary', 'week recap', 'retrospective', 'progress review', or 'weekly check-in'.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'cross-domain pattern analysis' and 'strategic reflection' without listing any concrete actions. It does not specify what is analyzed, what patterns are detected, or what outputs are produced.	1 / 3
Completeness	The 'what' is extremely vague (pattern analysis and reflection) and there is no explicit 'when' clause or trigger guidance. The description fails to answer either question clearly.	1 / 3
Trigger Term Quality	'Weekly review' is a natural term a user might say, but 'cross-domain pattern analysis' and 'strategic reflection' are abstract jargon unlikely to match user queries. Missing common variations like 'weekly summary', 'week in review', 'retrospective', etc.	2 / 3
Distinctiveness Conflict Risk	'Weekly review' provides some specificity, but 'cross-domain pattern analysis' is broad enough to overlap with many analytical skills. The lack of concrete scope makes it somewhat ambiguous.	2 / 3
	Total	6 / 12 Passed

Implementation

27%

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

This skill is far too verbose for its purpose, embedding a massive output template and extensive conversational coaching that Claude doesn't need inline. The workflow is reasonably clear but lacks error handling and validation checkpoints for file operations. The content would benefit enormously from extracting the template and supplementary guidance into separate bundle files.

Suggestions

Extract the ~150-line markdown template into a separate file (e.g., `templates/weekly-checkin-template.md`) and reference it from SKILL.md to dramatically reduce token usage.

Remove or drastically condense the 'Conversational Guidelines', 'Philosophy', 'Success Metrics', and 'Pattern Recognition Techniques' sections — these describe behaviors Claude already understands and waste significant token budget.

Add error handling for the context-gathering step: what to do if no braindumps exist, if directories are missing, or if MY-PROFILE.md has unexpected structure.

Split supplementary content (integration notes, pattern recognition techniques) into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. The massive template could be a separate file. Sections like 'Philosophy', 'Success Metrics', conversational guidelines ('Don't be clinical or robotic'), and pattern recognition techniques explain concepts Claude already knows. The Do/Don't lists are largely common sense for an LLM.	1 / 3
Actionability	The process flow is reasonably concrete with specific file paths, bash commands for timestamps, and a complete markdown template. However, the reflection questions are conversational prompts rather than executable steps, and the pattern recognition techniques are abstract descriptions rather than concrete implementations.	2 / 3
Workflow Clarity	The 4-step process (Gather Context → Guided Reflection → Generate Document → Confirm Completion) is clearly sequenced, and the pre-flight check includes a validation step for timestamps. However, there are no validation checkpoints for the scanning/gathering phase (what if files don't exist?), no error handling for missing directories, and no feedback loop for the generated document.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files. The enormous markdown template (~150 lines) should be in a separate template file. The pattern recognition techniques, conversational guidelines, and integration notes could all be split into referenced files. Everything is inlined into one massive document.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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

Repository: huytieu/COG-second-brain
Commit: 034af4c

Reviewed: 18 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.