mcpField
C
chatcrystal-task-recall

chatcrystal-task-recall

github.com/zengliangyiAgent workflows6154 installsUpdated 5d ago
Repository

About chatcrystal-task-recall

A pre-task recall workflow for ChatCrystal Core, intended for substantial implementation, refactoring, migration, configuration, investigation, or optimization work. It prioritizes project memories and allows work to continue when Core or the MCP tool is unavailable.

Key features

  1. 01Decide when task recall is warranted
  2. 02Send task goals and context
  3. 03Prioritize project memories
  4. 04Continue when Core or tools are unavailable

Use cases

  1. 01Recall relevant experience before implementation or refactoring
  2. 02Review project decisions and pitfalls before investigation

MCP support

The full workflow requires ChatCrystal Core and the MCP tool recall_for_task. The skill explains how to provide task context and use the returned project memories.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zengliangyi/chatcrystal --skill chatcrystal-task-recall

After installing, type/chatcrystal-task-recallin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

ChatCrystal Task Recall

Use this skill as a thin workflow on top of ChatCrystal Core. Do not invent a parallel memory system in the skill.

Workflow

  1. Decide whether the task is substantial enough to justify recall.
  2. Trigger for non-trivial implement, refactor, migration, config, investigate, or optimization work.
  3. Skip trivial edits, one-line answers, or purely conversational requests.
  4. If recall_for_task is available, call it before substantive work with:
    • mode: "task"
    • task.goal: the concrete task objective
    • task.task_kind: the best matching task kind
    • task.project_dir and task.cwd when repository context exists
    • task.branch when known
    • task.related_files or task.files_touched when known
    • task.source_agent when the runtime has a stable value
  5. Treat project_memories as primary context and global_memories as supplemental context.
  6. Apply recalled pitfalls, patterns, and prior decisions before proposing or writing code.

Example MCP Input

Use this shape when calling recall_for_task for implementation or investigation work:

{
  "mode": "task",
  "task": {
    "goal": "Add a paginated notes export endpoint",
    "task_kind": "implement",
    "project_dir": "/path/to/project",
    "cwd": "/path/to/project",
    "branch": "feature/export-notes",
    "related_files": [
      "server/src/routes/notes.ts",
      "shared/types/index.ts"
    ],
    "source_agent": "codex"
  },
  "options": {
    "project_limit": 5,
    "global_limit": 3,
    "include_relations": true
  }
}

Full Mode

Full mode requires ChatCrystal Core plus MCP access to recall_for_task.

  • Prefer the current repository or workspace path so Core can derive project_key.
  • Surface relevant warnings such as no-project-key or no-matches, but do not treat them as failures.
  • If recall returns nothing useful, continue the task normally.

Degraded Mode

If ChatCrystal Core or the MCP tool is unavailable:

  • Continue the task without blocking.
  • State briefly that long-term recall is unavailable in this environment.
  • Do not claim that any memory was recalled.
  • Do not instruct the runtime to auto-install ChatCrystal Core as part of the skill flow.

Comments

Markdown supported