knowledge_growth

Name: knowledge_growth
Availability: InStock
Author: kid0317

Automate daily three-phase knowledge processing from raw to formed materials.

26|4|Updated Mar 5, 2026

Search Tags:#automation #workflow #bash #memory #knowledge #scripting #cron

Ready to run

npx skills add https://github.com/kid0317/cc_workspace_bot --skill knowledge-growth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: knowledge_growth
Source: https://github.com/kid0317/cc_workspace_bot/tree/main/workspaces/_companion/.claude/skills/knowledge_growth
Command: npx skills add https://github.com/kid0317/cc_workspace_bot --skill knowledge-growth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the daily processing of knowledge materials in memory, advancing through a three-phase lifecycle: raw → digesting → formed. It runs independently on a cron-based schedule (0 3 * * *), not relying on life_sim, and uses a dedicated lock to ensure deterministic processing across sessions.

Core Features & Use Cases

Independent scheduled workflow that ingests knowledge items from memory/material_pool.md and stores results into memory/knowledge_bank.md with 3-phase transitions.
Supports deterministic locking (.knowledge.lock) to prevent race conditions and enables phase transitions (raw, digesting, formed).
Use Case: An enterprise team curates knowledge chunks daily and progressively digests them into "formed" knowledge entries for proactive referencing.

Quick Start

Configure the cron to run at 0 3 * * * and ensure material_pool.md and the memory lock file are in place so the workflow can execute automatically.

Frequently Asked Questions about knowledge_growth

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

FAQPage Schema

How do I automate daily knowledge processing from raw notes to formed knowledge?▼

You can automate daily knowledge processing by running a cron-based scheduled workflow that ingests raw materials from material_pool.md and transitions them through raw, digesting, and formed phases into knowledge_bank.md. This lifecycle operates independently at 0 3 * * *.

How does file locking prevent race conditions in automated knowledge workflows?▼

File locking prevents race conditions in automated knowledge workflows by using a dedicated .knowledge.lock file to ensure deterministic processing across multiple concurrent sessions. This guarantees phase transitions execute safely without overlapping writes to memory.

Do I need any external dependencies to run a cron-based knowledge lifecycle script?▼

No external dependencies are required to run a cron-based knowledge lifecycle script. You only need to configure the cron schedule, ensure material_pool.md exists for ingestion, and maintain the memory lock file to enable deterministic phase transitions.

What is the three-phase knowledge lifecycle for memory material processing?▼

The three-phase knowledge lifecycle for memory material processing is a structured transition from raw to digesting to formed. It progressively converts raw knowledge chunks into fully formed knowledge entries stored in memory for proactive retrieval and referencing.

Can I use scheduled bash scripting for enterprise team knowledge curation?▼

Yes, you can use scheduled bash scripting for enterprise team knowledge curation. An independent workflow can automatically curate daily knowledge chunks and progressively digest them into formed knowledge entries for proactive referencing by the team.

Why does my automated knowledge workflow not process materials correctly across sessions?▼

Automated knowledge workflows may fail to process materials correctly across sessions if the .knowledge.lock file is missing or improperly managed, preventing deterministic phase transitions. Ensure material_pool.md and the lock file are correctly in place before execution.