journal-entry-creator

Create structured Markdown journal entries from YAML templates with validation.

9|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/pantheon-org/tekhne --skill journal-entry-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journal-entry-creator
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/documentation/journal-entry-creator
Command: npx skills add https://github.com/pantheon-org/tekhne --skill journal-entry-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and template (resource) components.

What problem does it solve?

This Skill automates the creation of structured journal entries, ensuring consistency and compliance with predefined templates and validation rules, saving time and reducing errors in documentation.

Core Features & Use Cases

  • Structured Entry Creation: Generates timestamped Markdown journal entries with YAML frontmatter.
  • Template-Based Generation: Supports multiple entry types (troubleshooting, learning, article summary, general) using specific YAML schemas.
  • Compliance Validation: Enforces date consistency, heading hierarchy, tag matching, and code block formatting.
  • Use Case: When you need to document a troubleshooting session, learning experience, or summarize an article, this Skill guides you through the process, ensuring all required fields and formats are met.

Quick Start

Use the journal-entry-creator skill to create a new journal entry about your recent project planning session.

Frequently Asked Questions about journal-entry-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate structured Markdown journal entries with YAML frontmatter?

You can automate structured Markdown journal entries by applying predefined YAML templates that generate timestamped files with required frontmatter. This enforces strict formatting, date synchronization, and section compliance across various entry types like troubleshooting and learning logs.

What is the best way to format and validate troubleshooting documentation?

The best way to format and validate troubleshooting documentation is using template-based generation with built-in compliance validation. This enforces heading hierarchy, tag matching, and code block formatting while ensuring date consistency across your structured journal entries.

Can I use predefined templates for different types of journal entries like learning logs and article summaries?

Yes, predefined templates support multiple entry types including troubleshooting, learning, article summaries, and general logs. Each type uses specific YAML schemas to guide you through the process, ensuring all required fields and formats are met.

How does compliance validation work for date consistency and heading hierarchy in Markdown?

Compliance validation for Markdown works by enforcing date synchronization between filename timestamps and frontmatter, checking heading hierarchy structures, verifying tag matching, and validating code block formatting against predefined YAML schema rules.

Do I need any external dependencies to generate timestamped journal entries?

No external dependencies are required to generate timestamped journal entries. The Skill operates independently using internal scripts, references, and templates to produce validated Markdown files with synchronized dates and structured sections.

Why does my journal entry validation fail when dates do not match?

Journal entry validation fails when dates do not match because the compliance rules enforce strict date synchronization between the YAML frontmatter and the timestamped filename. This ensures chronological consistency across all generated Markdown entries.