CtrlK
BlogDocsLog inGet started
Tessl Logo

weekly-review

Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is weekly-review in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-organized with a strong, validated three-phase workflow and concrete commands, but it is undermined by a missing bundle: none of the referenced scripts, references, or assets exist, which breaks progressive disclosure and leaves the otherwise copy-paste-ready commands non-executable.

Suggestions

Ship the bundle: create scripts/open_loop_scanner.py, scripts/weekly_review_gate.py, scripts/commitment_auditor.py plus the three references/*.md and two assets/*.md files so the referenced paths resolve — this alone would raise progressive_disclosure and actionability.

Trim the 'What this does' rationale to one line; move the GTD 'why' into references/gtd_weekly_review_canon.md and keep the body to the operational loop.

Add a one-line note in the Scripts table or a short 'Requirements' line stating the scripts are stdlib-only and where they live, so the actionability is unambiguous even before the bundle is consulted.

DimensionReasoningScore

Conciseness

Mostly efficient with tight code blocks and a clean script table, but the 'What this does' section spends tokens on GTD rationale ('the critical success factor of the whole method', 'their memory is exactly what the method says not to trust') that could be trimmed without losing guidance.

4 / 5

Actionability

Provides concrete, flag-specific commands (e.g. 'python scripts/open_loop_scanner.py --dir ~/notes --stale-days 14') and explicit routing rules, but the referenced scripts do not exist in the bundle, so the commands are not actually executable as written — a real execution gap.

4 / 5

Workflow Clarity

A clearly sequenced three-phase workflow (GET CLEAR / GET CURRENT / GET CREATIVE) with an explicit validation checkpoint: the gate computes completion %, names missing steps, and exits 0 (COMPLETE) or 2 (INCOMPLETE), with a feedback rule that an unskipped GET CURRENT step forces INCOMPLETE.

5 / 5

Progressive Disclosure

The structure is well-signaled with one-level-deep ## References and ## Assets sections each carrying a one-line description, but every referenced file (3 references, 2 assets, 3 scripts) is absent from the bundle, so the navigation links are dead and the 'content across files' structure is not actually realized.

3 / 5

Total

16

/

20

Passed

Description

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

An excellent description: third-person voice, explicit 'Use when...' trigger clause with natural phrasing and a slash command, and a concrete, comprehensive 'what' covering the three phases and the deterministic scripts. No over-claims or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'inventory open loops', 'gate the checklist with named gaps', 'score commitment health 0-100', plus the three named phases — giving comprehensive coverage with no vague filler.

5 / 5

Completeness

Explicitly answers both: what it does ('Walks David Allen's three-phase loop... inventory open loops, gate the checklist... score commitment health 0-100') and when to use it (a full 'Use when...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Covers natural phrases users would actually say ('run a weekly review', 'close open loops', 'audit stalled projects', 'get their system back to trusted', 'restart a lapsed review habit') plus the explicit '/cs:weekly-review' slash trigger, with synonyms included.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (personal GTD weekly review / trusted-system audit) with distinct triggers; unlikely to fire for sibling skills like reflect or capture.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 17 missing

Warning

Total

13

/

16

Passed

Repository
alirezarezvani/claude-skills
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.