CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-journal

A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say "log this to my journal", "add to today's journal", "reflect on today/yesterday", or when finishing a meaningful chunk of work in any session.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 clean, token-efficient redirect that delegates to an authoritative playbook and adds one substitution rule. It scores well on conciseness and clarity, but because the actual procedure lives entirely in the referenced file, actionability and workflow clarity are good rather than fully self-contained.

Suggestions

Inline a one-line summary of the journal entry format and reflection steps so the skill remains actionable even if the referenced playbook path is unavailable.

Add minimal section headers (e.g. '## Execution', '## Substitution rules') to give the redirect body explicit structure.

DimensionReasoningScore

Conciseness

Extremely lean: two short paragraphs with no concept explanation or padding, assuming Claude's competence. Every token earns its place.

5 / 5

Actionability

Gives concrete, executable guidance (specific file paths '.claude/skills/daily-journal/SKILL.md', '.agents/rules/cog.md', and the 'invoke_subagent' function), but the substantive instructions are delegated to the referenced playbook rather than present in the body.

4 / 5

Workflow Clarity

Clear two-step sequence (execute the playbook, then follow cog.md) with an explicit conditional substitution rule; not a destructive/batch operation so no validation cap applies, but the real workflow lives in the delegated file.

4 / 5

Progressive Disclosure

The body is an overview pointing one level deep to the authoritative playbook with clearly signaled paths; no bundle files exist to verify, and the body lacks section headers, keeping it just below the ideal.

4 / 5

Total

17

/

20

Passed

Description

91%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 description that clearly states the skill's purpose and provides explicit, natural trigger phrases covering both slash-command and conversational invocation. The only soft spot is the broadly-scoped 'finishing a meaningful chunk of work' trigger, which slightly raises overlap risk.

DimensionReasoningScore

Specificity

Names the domain and gives two concrete actions with a precise target path ('Append short entries...to 01-daily/journal/YYYY-MM-DD.md' and 'Run a guided reflection'), which is above the 1-2 generic actions anchor but short of 'several' comprehensive actions.

4 / 5

Completeness

Explicitly answers both what ('A passive daily work journal... Append short entries... Run a guided reflection') and when ('Use when you run /daily-journal, say...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including the slash command and user utterances ('/daily-journal', 'log this to my journal', 'add to today's journal', 'reflect on today/yesterday') covering the natural ways a user would request this skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche (passive daily work journal) with distinct triggers, but the broad clause 'when finishing a meaningful chunk of work in any session' creates minor overlap risk with general logging or reflection skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

huytieu/COG-second-brain

Path

.agents/skills/daily-journal/SKILL.md

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.