skills.rest
haidonglethqb
haidonglethqbCOMMUNITY
Explore all skills by this author →
GitHub

ck:journal

Generates concise journal entries from recent changes and session reflections via a subagent.

Updated Feb 27, 2026
Search Tags:#documentation#memory#notes#journal#reflection#journal-entry
One-click install
npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-journal-haidonglethqb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:journal
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.qwen/skills/journal
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-journal-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Journal entries help teams capture learning from recent changes and sessions, preserving memory and decisions in a structured format.

Core Features & Use Cases

  • Journal writing with context: Use the journal-writer subagent to explore memories and recent code changes, and write concise journal entries.
  • Focused reflections: Entries should be concise and focused on the most important events, key changes, impacts, and decisions.
  • Storage & retrieval: Keep journal entries in the ./docs/journals/ directory for easy reference.

Quick Start

Invoke the journal-writer subagent with a topic to generate a concise journal entry saved to ./docs/journals/.

Frequently Asked Questions about ck:journal

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

FAQPage Schema
How do I capture code changes and session reflections in a structured journal entry?▼

To capture code changes in a journal entry, invoke the journal-writer subagent with a topic prompt to explore memories and recent modifications, generating concise reflections saved to your local ./docs/journals/ directory.

What is the best way to document sprint decisions and recent changes for my development team?▼

Documenting sprint decisions is done by generating focused journal entries that record key changes, impacts, and decisions, allowing development teams to preserve learning and project memory across sessions.

Do I need a specific directory structure to store project journal entries?▼

Yes, storing project journal entries requires a local ./docs/journals/ directory in your project root to save and retrieve the generated files for easy reference.

Can I use this to document experiments and decisions across different research projects?▼

You can document experiments across research projects by providing a simple topic prompt to the journal-writer, which generates concise entries capturing learning and decisions applicable to researchers.

How concise should the generated journal entries be for tracking recent changes?▼

Generated journal entries should be concise and focused strictly on the most important events, key changes, impacts, and decisions rather than exhaustive logs of the entire session.

What do I need to provide to generate a journal entry for a specific topic?▼

To generate a journal entry, you need the journal-writer subagent configured and a simple topic prompt describing the recent changes or session you want to document.

Related Skills

Explore More Content & Communication Skills→
mpazarynampazaryna
1

journal

Generate markdown journal entries from git commit history.

Community
Basic
dthuy62dthuy62

ck:journal

Write concise journal entries summarizing recent changes and decisions into ./docs/journals/.

Community
Intermediate
felix-howardfelix-howard

ck:journal

Generate journal entries documenting code changes and session reflections in ./docs/journals/.

Community
Basic
auxi-wardrobeauxi-wardrobe
1

ck:journal

Create technical journal entries for project wrap-ups and session reflections.

Official
Basic