agentsclimarketplace

Chatcrystal debug recall

Skill bg-szy/TOP-SKILLS/skills/marketplace/chatcrystal-debug-recall

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill chatcrystal-debug-recall

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.6 KB, 549 tokens by cl100k_base, as published. Nobody here has run it

ChatCrystal Debug Recall

Use this skill when the task is clearly about diagnosis or debugging. Keep the skill thin and let ChatCrystal Core handle retrieval.

Workflow

  1. Trigger when the task includes failing tests, compiler errors, runtime exceptions, broken dependencies, environment problems, or performance regressions.
  2. If recall_for_task is available, call it before proposing a fix with:
    • mode: "debug"
    • task.goal: the concrete debugging objective
    • task.task_kind: "debug"
    • task.project_dir and task.cwd when known
    • task.branch when known
    • task.related_files or task.files_touched when known
    • task.error_signatures populated with the most useful identifiers available
  3. Prefer concrete signals such as:
    • failing test names
    • exception classes
    • error codes
    • log signatures
    • package or tool versions when they materially affect the failure
  4. Prioritize returned memories that explain root cause, remediation, or known pitfalls.
  5. Use recalled memories to sharpen diagnosis, not to skip verification in the current environment.

Example MCP Input

Use this shape when calling recall_for_task for debugging:

{
  "mode": "debug",
  "task": {
    "goal": "Diagnose failing build after TypeScript upgrade",
    "task_kind": "debug",
    "project_dir": "/path/to/project",
    "cwd": "/path/to/project",
    "branch": "upgrade/typescript",
    "related_files": [
      "server/src/cli/mcp/server.ts",
      "tsconfig.base.json"
    ],
    "error_signatures": [
      "TS2322",
      "Type is not assignable"
    ],
    "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.

  • Keep project_memories primary and global_memories secondary.
  • If the response includes warnings or no-matches, continue debugging normally.
  • Do not overfit to a recalled fix when the current failure signature diverges materially.

Degraded Mode

If ChatCrystal Core or the MCP tool is unavailable:

  • Continue the debugging task without blocking.
  • State briefly that long-term debug recall is unavailable.
  • Do not fabricate historical failures, causes, or fixes.
  • Do not turn installation commands into automatic skill steps.

What ships with it: 1 file

21.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.