Install
$ agentstack add skill-zengliangyi-chatcrystal-chatcrystal-debug-recall ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- Trigger when the task includes failing tests, compiler errors, runtime exceptions, broken dependencies, environment problems, or performance regressions.
- If
recall_for_taskis available, call it before proposing a fix with:
mode: "debug"task.goal: the concrete debugging objectivetask.task_kind: "debug"task.project_dirandtask.cwdwhen knowntask.branchwhen knowntask.related_filesortask.files_touchedwhen knowntask.error_signaturespopulated with the most useful identifiers available
- Prefer concrete signals such as:
- failing test names
- exception classes
- error codes
- log signatures
- package or tool versions when they materially affect the failure
- Prioritize returned memories that explain root cause, remediation, or known pitfalls.
- 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_memoriesprimary andglobal_memoriessecondary. - 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ZengLiangYi
- Source: ZengLiangYi/ChatCrystal
- License: Apache-2.0
- Homepage: https://zengliangyi.github.io/ChatCrystal/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.