Agent skill · writing content · aiskillstore
chatcrystal-task-writeback
Write reusable ChatCrystal task memories after substantive work completes. Use when implementation or debugging produced a durable fix, pitfall, pattern, or decision worth preserving, and when the environment can either persist it through `write_task_memory` or emit a structured memory candidate for later save.
Why this skill is useful
Provides a structured workflow for persisting task memories that enhances the AI's ability to retain and utilize knowledge from previous tasks.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
ChatCrystal Task Writeback Use this skill after meaningful work completes. Let ChatCrystal Core decide whether a memory should be skipped, merged, or created. Workflow 1. Trigger only after substantive work completes and the result produced reusable knowledge. 2. Good candidates include: a durable fix a meaningful pitfall a reusable pattern an explicit engineering decision 3. If writetaskmemory is available and the runtime has a stable run or session key, call it with: mode: "auto" sourcerunkey: the stable run or session key task.goal, task.taskkind, task.projectdir, task.cwd, task.branch task.sourceagent when known memory.summary: concise and durable, not chatty memory.outcometype: one of pitfall, fix, pattern, decision memory.rootcause, memory.resolution, memory.errorsignatures, memory.filestouched, memory.tags when relevant 4. Use mode: "manual" only for an explicit manual save flow, never as a silent fallback for automatic writeback. 5. Default to project-scoped knowledge. Only use global scope for clearly cross-project knowledge and only in an explicit manual save flow. 6. Report the persistence result accurately: created merged skipped Example MCP Input Use this shape when calling writetaskmemory after a completed task with a stable run key: Full Mode Full mode requires ChatCrystal Core plus MCP access to writetaskmemory. Do not reimplement skip or merge logic in the skill. Trust Core to decide whether the memory should be skipped, merged, or created. If the tool reports skipped, keep the task result but do not force persistence. Degraded Mode If ChatCrystal Core or the MCP tool is unavailable, or if no stable run key exists for automatic writeback: Do not claim that the memory was saved. Emit a structured memory candidate in the response for later save. Keep the candidate aligned with the writetaskmemory.memory payload shape so it can be reused later. Do not instruct the runtime to auto-install ChatCrystal Core as part of the skill flow.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/chatcrystal-task-writeback