decision-logger

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

88%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 highly actionable and well-sequenced, with a strong validation-gated logging workflow and concrete CLI examples. The main weakness is progressive disclosure: a References entry points to a missing templates/ file, slightly undermining the otherwise clean navigation.

Suggestions

Add the missing templates/decision-entry.md file (or remove the dead reference from the References section) so every referenced path resolves.

Consider moving the full Decision Entry Format and Conflict Detection blocks into templates/decision-entry.md and summarizing inline, to deepen the progressive-disclosure structure.

Trim the redundant restatement of the two-layer rationale in the opening paragraph and the legacy migration note to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, with only minor trimmable bits (the opening paragraph restates the architecture rationale already implied, and the migration note is somewhat tangential).	4 / 5
Actionability	Provides fully executable Quick Start CLI commands with flags, a copy-paste-ready decision entry template, and concrete conflict-detection block formats that cover the common cases.	5 / 5
Workflow Clarity	The 'Logging Workflow (Post Phase 5)' is a clearly sequenced 6-step process with an explicit validation checkpoint (step 3-4 conflict check) and a feedback loop (surface conflicts → wait for founder resolution before writing the approved record).	5 / 5
Progressive Disclosure	Well-organized with clear section headers, a commands table, and a dedicated References section; however one referenced file (templates/decision-entry.md) does not exist in the bundle, and detail like the entry format is inlined rather than split out.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong, well-structured description that clearly states concrete capabilities and gives explicit, multi-scenario 'Use when' trigger guidance. It uses third-person voice throughout and carves out a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Manages raw transcripts (Layer 1) and approved decisions (Layer 2)', 'logging decisions', 'reviewing past decisions', 'checking overdue action items') with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (two-layer memory architecture managing raw transcripts and approved decisions) and 'when' via a concrete 'Use when...' clause with multiple trigger scenarios.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('logging decisions after a board meeting', 'reviewing past decisions', 'overdue action items') but leans partly on brand slash-commands (/cs:decisions, /cs:review) rather than pure natural-language synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (board-meeting decision memory) with distinct triggers (/cs:decisions, /cs:review, post-Phase-5 invocation) and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: c-level-advisor/skills/decision-logger/SKILL.md
Commit: 19392f7

Reviewed: ~12 hours 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.