algernon-orchestrator

What This Skill Does

The algernon-orchestrator is the central command center for the OpenAlgernon study ecosystem. It acts as an intelligent router and session manager, ensuring that every time you interact with your study system, the context is loaded, stats are retrieved, and your intent is correctly interpreted. The orchestrator automates the 'getting started' phase by reading your personalized memory files, checking pending study cards in your local SQLite database, and providing a concise status briefing. It bridge the gap between user intent and specific atomic skills, allowing you to transition seamlessly from a meta-study planning phase to specialized tasks like flashcard reviews, Feynman technique explanations, or deep-work sprints.

Installation

To integrate this orchestrator into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/antoniovfranco/algernon-orchestrator Once installed, ensure your ALGERNON_HOME environment variable is correctly configured to point to your data directory to enable full synchronization with your SQLite databases and memory markdown logs.

Use Cases

• Session Initialization: Automatically generate a briefing of your study status, pending tasks, and streaks upon login.
• Skill Routing: Delegate complex tasks to specialized agents (e.g., routing 'sprint 25' to the timer utility or 'feynman' to the pedagogical explanation engine).
• Content Management: Centralize content lifecycle operations such as importing new materials, removing outdated papers, or listing your current knowledge base.
• Progress Tracking: Consolidate your study session data to provide periodic reports on your learning velocity.

Example Prompts

1. "iniciar sessao"
2. "quero estudar sobre machine learning, me entrevista sobre o tema"
3. "sprint 25"

Tips & Limitations

• Contextual Awareness: The orchestrator relies on the validity of your MEMORY.md file. Keep it updated to ensure the briefing section remains accurate.
• Database Integrity: Since the orchestrator queries study.db directly, ensure no concurrent writes are occurring during the briefing generation phase.
• Pathing: If the system fails to display cards due, check your ALGERNON_HOME variable; if the orchestrator cannot locate the path, it will default to 'no activity' indicators to prevent crashes.