chatcrystal-task-recall
/chatcrystal-task-recall
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
- Author
- ZengLiangYi ↗
- Repository
- ChatCrystal ↗
- Licence
- Apache-2.0
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
Original author description
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
How it works
- Workflow
- Example MCP Input
- Full Mode
- Degraded Mode
SKILL.md preview
---
name: chatcrystal-task-recall
description: Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
---
# 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:
```json
{
"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.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named chatcrystal-task-recall.
Database snapshot: 13.11.2026 · package version d76c41c109fa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix. - 100chatcrystal-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… - 90recall
Search memories from past Oh My Pi sessions in the CURRENT project. Use when the user's question could benefit from historical context, past decisions, debugging notes, architectural choices, or prior conversations in this repo. For cross-project recall, use the recall-global skill instead. - 90memory-informed-design
Architecture/design decisions with working memory -- before recommending, recall prior decisions and tradeoffs; when a decision is made, capture it immediately. Use for any substantive design question. - 90recall
Search memories from past Claude Code sessions in the CURRENT project. Use when the user's question could benefit from historical context, past decisions, debugging notes, architectural choices, or prior conversations in this repo. For cross-project recall, use the recall-global skill instead. - 90brief-first-execution
Create a single working brief before substantial implementation, audit, or migration work. Use when tasks are non-trivial, risks are real, or the session is likely to drift without one source of truth for scope, non-goals, verification, and done criteria.