weekly-checkin

Cross-domain pattern analysis and strategic reflection for weekly review

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/weekly-checkin/SKILL.md

Quality

Content

62%

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

The body is highly actionable and well-sequenced with strong verification, but it is notably verbose — explaining generic analytical concepts and including philosophical padding that competes for context. Moving the large template and generic technique descriptions into reference files would improve both conciseness and progressive disclosure.

Suggestions

Move the full ~200-line check-in template into a separate reference file (e.g. references/weekly-checkin-template.md) and keep only the frontmatter skeleton and save-path inline.

Cut the 'Pattern Recognition Techniques' and 'Philosophy' sections — these restate concepts Claude already knows and add token load without actionable detail.

Trim the 'Conversational Guidelines' Do/Don't list to a few non-obvious rules (e.g. the 'do not force positivity' point) rather than restating basic empathetic-conversation norms.

Dimension	Reasoning	Score
Conciseness	The ~440-line body pads with concepts Claude already knows (generic 'Pattern Recognition Techniques' like Frequency/Temporal/Domain analysis, a 'Philosophy' section, and conversational Do/Don'ts about being warm), which matches the verbose/padded level-1 anchor.	1 / 3
Actionability	It gives concrete, copy-paste-ready guidance: an exact `date` command, a full markdown template with frontmatter, a specific save path, and a coverage verification checklist — specific and executable for an instruction-only skill.	3 / 3
Workflow Clarity	The four-step process (Gather → Reflect → Generate → Confirm) is clearly sequenced with a deterministic coverage checklist as the verifier, explicit pre-flight timestamp validation, and layered termination conditions with error-recovery guidance.	3 / 3
Progressive Disclosure	Sections are headed, but the skill is a monolithic wall of text with a ~200-line inline template and generic guidance that would be better split into reference files; no bundle files exist to offload detail.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 clear and on-domain but stays at a generic level: it conveys the skill's purpose without enumerating concrete actions or providing an explicit 'Use when' trigger clause. Adding specific verbs and natural trigger phrases would lift it to level 3.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases such as 'weekly checkin', 'weekly review', or 'reflect on my week'.

Replace abstract terms with concrete actions, e.g. 'Scans the week's braindumps and briefs, runs guided reflection across personal/professional/project domains, and writes a structured weekly check-in note.'

Include common user phrasings (e.g. 'end-of-week reflection') to improve trigger coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of actions ('Cross-domain pattern analysis and strategic reflection') but stops short of listing multiple specific concrete actions like the level-3 anchor requires.	2 / 3
Completeness	It states what the skill does but the 'when' is only implied via 'for weekly review'; there is no explicit 'Use when...' trigger clause, which the guideline caps at 2.	2 / 3
Trigger Term Quality	'weekly review' is a natural phrase users would say, but the description omits common variations ('weekly checkin', 'reflect on my week') that the body's 'When to Invoke' section actually lists.	2 / 3
Distinctiveness Conflict Risk	The weekly-review framing gives it a niche, but generic terms like 'pattern analysis' and 'strategic reflection' could overlap with other reflection/analysis skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: huytieu/COG-second-brain
Path: .claude/skills/weekly-checkin/SKILL.md
Commit: dfbf9e9

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