Receber por email
← Voltar para o catálogo

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.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/chatcrystal-task-recall/svg)](https://www.skillteca.com.br/skills/chatcrystal-task-recall)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  5. mode: "task"
  6. task.goal: the concrete task objective
  7. task.task_kind: the best matching task kind
  8. task.project_dir and task.cwd when repository context exists
  9. task.branch when known
  10. task.related_files or task.files_touched when known
  11. task.source_agent when the runtime has a stable value
  12. Treat project_memories as primary context and global_memories as supplemental context.
  13. 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.
Compartilhar X LinkedIn