diary

Unified Diary System: A context-preserving automated logger for multi-project development.

Quality

54%

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 ./skills/diary/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 content delivers a well-sequenced, actionable workflow with externalized scripts and useful templates, but is weighed down by repetitive emphatic warnings and redundant continuation directives that inflate token cost.

Suggestions

Consolidate the repeated 'Force Continue' / 'do not interrupt' directives into a single workflow-integrity note at the top to cut redundant tokens.

Trim ALL-CAPS and emoji-laden warnings to concise rules, keeping the constraint without the padding.

Define or resolve {diary_system_path} and {Knowledge_Base_Path} (or document how the agent obtains them) so the commands are fully executable.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: repeated 'Ironclad Rule' / 'Force Continue' admonitions, emoji-heavy ALL-CAPS warnings, and restated constraints ('do not interrupt', 'do not wait') pad the token budget without adding guidance Claude could not infer.	2 / 5
Actionability	Steps give concrete executable commands (python scripts with paths) and full Markdown templates, but unbound placeholders like {diary_system_path}, {Knowledge_Base_Path}, and <Project_Root_Path> leave minor gaps before the commands are copy-paste ready.	4 / 5
Workflow Clarity	Steps 1-4 plus 1.5 are clearly sequenced with prerequisites, an append/never-overwrite safety rule, a forced user-confirmation checkpoint in Step 4, and a Task Acceptance Criteria checklist, though force-deleting temp files has no explicit validation before removal.	4 / 5
Progressive Disclosure	Scripts are properly externalized to ./scripts/ and referenced by one-level paths that resolve to real files (prepare_context.py, fetch_diaries.py, master_diary_sync.py); structure is clear, though the two diary templates are inlined rather than split into reference files.	4 / 5
	Total	14 / 20 Passed

Description

48%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 identifies a clear niche but relies on abstract language and omits any use-when trigger guidance, leaving a user unsure when to invoke it. Concrete actions and natural trigger phrases should be added.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when writing a daily dev log, summarizing progress, or syncing a project diary to Notion/Obsidian').

Replace the abstract 'automated logger' with concrete actions such as 'summarize progress, write daily dev logs, and sync diaries to Notion and Obsidian'.

Include natural synonyms users say ('dev log', 'daily review') alongside file or tool terms (Notion, Obsidian) to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'context-preserving automated logger for multi-project development' names the domain but offers only one generic action ('logger') with no concrete operations like summarizing progress or syncing to Notion/Obsidian (those appear only in the body).	2 / 5
Completeness	It states a clear 'what' (an automated logger for multi-project development) but has no 'Use when...' clause or equivalent trigger, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural keywords like 'Diary', 'logger', and 'multi-project development' are present, but common variations users would say ('dev log', 'daily review', 'summarize progress') are absent from the description.	3 / 5
Distinctiveness Conflict Risk	'Unified Diary System' scoped to 'multi-project development' carves a fairly distinct niche with only minor overlap risk against generic logging or note-taking skills.	4 / 5
	Total	12 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/diary/SKILL.md
Commit: fbdfd63

Reviewed: about 17 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.