journal-entry-creator

Create structured journal entries with YAML frontmatter, template-based sections, and compliance validation. Use when user asks to 'create journal entry', 'new journal', 'document [topic]', 'journal about [topic]', or needs to create timestamped .md files in YYYY/MM/ directories. Supports six entry types: general journal entries, troubleshooting sessions, learning notes, article summaries, ticket-refinement sessions, and ticket-kickoff sessions. Keywords: journal, documentation, troubleshooting, learning, article-summary, ticket-refinement, ticket-kickoff, YAML frontmatter, template schemas, validation.

Quality

86%

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

Quality

Content

81%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 workflow clarity is excellent, with a fully specified four-phase process, a validation feedback loop, and copy-paste-ready commands for a bespoke journal system whose rules Claude could not guess. The main cost is token efficiency: compliance rules are stated two to three times across sections, which also keeps progressive disclosure at 4 rather than 5.

Suggestions

State each compliance rule once: keep the normative version in 'Domain-Specific Compliance Rules' (or references/compliance.md) and reduce the Anti-Patterns WHY/BAD/GOOD blocks to one-line pointers for rules already covered, cutting the duplicated triple-sync, bare-code-block, and schema-first material.

Trim the assets/.gitignore note to its actionable core (check .gitignore before committing assets; never place secret-bearing output there) and drop the extended rationale about ephemeral vs tracked treatment.

Move the detailed per-rule validation specifics that already live in references/compliance.md fully out of SKILL.md, keeping only the one-line rule summaries plus the link, so the body reads as a true overview with one-level-deep references.

Dimension	Reasoning	Score
Conciseness	Most content is non-obvious domain rules Claude cannot know (triple-sync dates, taxonomy, continuation links), but the same rules are repeated across "Domain-Specific Compliance Rules", "Success Criteria & Validation Rules", and the Anti-Patterns WHY/BAD/GOOD blocks, and the .gitignore aside on assets runs well past what is needed. Not 2: the bulk earns its tokens; not 4: the triple-stated rules are real tightening opportunities.	3 / 5
Actionability	Fully executable throughout: exact commands (bash skills/journal-entry-creator/scripts/validate-journal-entry.sh, npx prettier --write, npx markdownlint-cli2 --fix), exact filename/slug/H1 formats with concrete examples, and verbatim YAML/markdown patterns for tags and proposed ticket descriptions.	5 / 5
Workflow Clarity	The Four-Phase Workflow is explicitly sequenced with freedom levels per phase, Phase 4 gives an exact validate → format → lint → re-validate command sequence, failure handling is a closed feedback loop ("Re-run validation after fixes", "Do NOT proceed to git commit if validation fails"), and file-overwrite is guarded by confirmation. Not 4: checkpoints and recovery loops are explicit and complete.	5 / 5
Progressive Disclosure	References are one level deep, all verified to exist (templates, compliance.md with the #ticket-kickoff-rules and #continuation-links anchors, edge-cases.md, validator script), and gated by explicit load conditions ("Load compliance.md: Only if validation fails", "Do NOT load: journal-command.md (superseded)"). Not 5: the ~480-line body inlines detailed compliance rules that are also duplicated in references/compliance.md, so the overview/body split is not clean; not 3: navigation and signaling are clearly better than the 3-anchor's buried references.	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: it states concrete capabilities, enumerates the six supported entry types, and gives explicit natural-language trigger phrases plus a keyword list. Its only weaknesses are mild abstraction in a couple of capability phrases and the slightly over-broad "document [topic]" trigger.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and artifacts ("Create structured journal entries with YAML frontmatter, template-based sections, and compliance validation", "timestamped .md files in YYYY/MM/ directories", six named entry types), but "template-based sections" and "compliance validation" stay one level more abstract than the 5-anchor's fully concrete action list.	4 / 5
Completeness	Explicitly answers both "what" (create structured entries with frontmatter, template schemas, compliance validation, six entry types) and "when" with concrete quoted trigger phrases, matching the 5-anchor pattern.	5 / 5
Trigger Term Quality	Covers natural trigger phrases users would actually say ("create journal entry", "new journal", "journal about [topic]", "document [topic]") plus an explicit Keywords list with synonyms (journal, documentation, troubleshooting, learning, article-summary, ticket-refinement, ticket-kickoff).	5 / 5
Distinctiveness Conflict Risk	A clear journaling niche with distinct triggers, but the trigger "document [topic]" is broad enough to overlap with generic documentation-creation skills, giving minor conflict risk.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 1 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: pantheon-org/tekhne
Path: skills/documentation/journal-entry-creator/SKILL.md
Commit: a1083f4

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