weekly-checkin

Cross-domain pattern analysis and strategic reflection for weekly review

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 validation and loop engineering, but it is verbose in places (explaining concepts Claude knows) and monolithic in structure, with a large inline template and supporting material that would benefit from being split into reference files.

Suggestions

Move the full weekly-checkin markdown template into a references file (e.g. references/weekly-checkin-template.md) and keep only the frontmatter schema and a short pointer inline.

Trim or remove the Philosophy section and condense Pattern Recognition Techniques to a short bullet list, since Claude already knows these analysis methods.

Extract the Conversational Guidelines and Pattern Recognition Techniques into a separate reference file, signaled one level deep, to reduce the inline token footprint.

Dimension	Reasoning	Score
Conciseness	The core process flow and template are efficient, but the Philosophy section and Pattern Recognition Techniques (frequency analysis, temporal clustering) explain concepts Claude already knows and add padding that could be trimmed.	2 / 3
Actionability	Guidance is concrete and copy-paste ready: exact reflection questions, a complete markdown template with frontmatter, the deterministic `date '+%Y-%m-%d %H:%M'` command, and a precise save path.	3 / 3
Workflow Clarity	A clear four-step sequence is paired with explicit validation: a pre-flight date check, a deterministic verifier checklist, and layered termination conditions with feedback loops in the Loop Engineering section.	3 / 3
Progressive Disclosure	The skill is monolithic: the large template, Pattern Recognition Techniques, Philosophy, and Integration sections are all inline with no bundle files (references/scripts/assets absent), and the one external pointer to loop-engineering/SKILL.md is not a bundled, clearly-signaled reference.	2 / 3
	Total	10 / 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 identifies a recognizable niche (weekly review with cross-domain pattern analysis) but stops at abstract category language without concrete actions or an explicit trigger clause. It answers "what" only vaguely and leaves "when" implied, which limits all dimensions to the middle anchor.

Suggestions

Add concrete actions the skill performs, e.g. "Gathers the week's braindumps and briefs, guides domain-by-domain reflection, and generates a structured weekly check-in note."

Append an explicit trigger clause: "Use when the user wants a weekly review or check-in, says 'reflect on my week', or wants to analyze cross-domain patterns from the past week."

Include natural variations users say ("weekly check-in", "weekly review", "reflect on my week") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "pattern analysis" and "strategic reflection" name the domain and a couple of actions but are abstract category labels rather than the multiple concrete actions (e.g., extract, merge, fill) that anchor a 3.	2 / 3
Completeness	It states what the skill does (cross-domain pattern analysis and strategic reflection) but provides no explicit "Use when..." trigger clause, so the "when" is only implied, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	"weekly review" is a natural term a user would say, but common variations the body itself lists ("weekly checkin", "reflect on my week") are absent, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The "weekly review" niche is somewhat specific, but the generic terms "pattern analysis" and "strategic reflection" could overlap with other reflection or analysis skills rather than carving a clearly distinct trigger space.	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
Commit: 5e9851c

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