weekly-checkin

Cross-domain pattern analysis and strategic reflection for weekly review

Quality

52%

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

60%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.

The body is a thorough, well-structured, and largely actionable guide with a clear process flow, explicit checklist verifier, and a complete output template. Its main weakness is verbosity — several trailing sections (Philosophy, generic pattern-recognition techniques) pad the skill without adding executable guidance.

Suggestions

Remove or drastically condense the 'Philosophy' section — it is inspirational padding that does not change Claude's behavior.

Trim the 'Pattern Recognition Techniques' section to a short checklist, since frequency/temporal/domain/contradiction analysis is largely Claude's existing knowledge.

Shorten the Do/Don't 'Conversational Guidelines' into a few concrete rules; the current two-list format repeats guidance already implied by the reflection prompts.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is noticeably verbose with several padded sections — the closing 'Philosophy' section, the fairly generic 'Pattern Recognition Techniques', and long Do/Don't lists — that add little executable value over what Claude already knows.	2 / 5
Actionability	Highly actionable: literal reflection questions to ask, exact vault paths to scan, a `date` command for the timestamp, a full copy-paste output template, and a concrete save path; minor gaps are the abstract 'help identify...' guidance and many template placeholders.	4 / 5
Workflow Clarity	A clear four-step sequence (Gather → Reflect → Generate → Confirm) plus an explicit coverage checklist verifier and layered termination conditions in the Loop Engineering section; the validation is somewhat conceptual rather than hard-coded, keeping it just below a 5.	4 / 5
Progressive Disclosure	Well-organized single file with clear sections and one clearly-signaled one-level-deep external reference (loop-engineering/SKILL.md); no nested references or bundle files. The large inlined output template is appropriate for this skill type, though sections like Philosophy could be trimmed.	4 / 5
	Total	14 / 20 Passed

Description

45%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.

The description is a concise but overly abstract single line: it names the domain and a couple of high-level actions yet omits explicit 'Use when...' trigger guidance and concrete verbs. It reads more as a tagline than a trigger-rich capability statement.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks for a weekly check-in, weekly review, or to reflect on their week across personal, professional, and project domains.'

Replace abstract buzzwords ('strategic reflection') with concrete actions ('gathers weekly braindumps and briefs, leads guided reflection, and generates a structured weekly check-in document').

Include natural synonyms already used in the body ('weekly checkin', 'reflect on my week') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('weekly review', 'cross-domain') but the only stated actions are the generic/abstract 'pattern analysis' and 'strategic reflection', which read more like buzzwords than concrete capabilities.	2 / 5
Completeness	The 'what' is moderately clear (pattern analysis + strategic reflection), but there is no 'Use when...' clause and the 'when' is only weakly implied by 'for weekly review'; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'weekly review' is a natural phrase users would say, but synonyms and common variations such as 'weekly checkin' or 'reflect on my week' (which actually appear in the body) are missing from the description.	3 / 5
Distinctiveness Conflict Risk	The weekly-review niche is somewhat specific, but 'pattern analysis' and 'strategic reflection' overlap with related skills the body itself references (daily check-in, knowledge-consolidation, pattern analysis).	3 / 5
	Total	11 / 20 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: cb4644d

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.