skills.rest
crissdiamond
crissdiamondCOMMUNITY
Explore all skills by this author →
GitHub

crisai-debugging-playbook

Diagnoses and resolves common runtime issues in crisAI via triage playbook.

Updated Apr 18, 2026
Search Tags:#debugging#troubleshooting#triage#runtime issues#crisAI
One-click install
npx skills add https://github.com/crissdiamond/crisAI --skill crisai-debugging-playbook
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crisai-debugging-playbook
Source: https://github.com/crissdiamond/crisAI/tree/main/.claude/skills/crisai-debugging-playbook
Command: npx skills add https://github.com/crissdiamond/crisAI --skill crisai-debugging-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to troubleshooting and resolving common runtime issues in the crisAI platform, streamlining the process of identifying and fixing problems.

Core Features & Use Cases

  • Symptom-to-cause analysis: Triage issues based on specific symptoms and corresponding likely causes.
  • Discriminating experiments: Execute experiments to narrow down the root cause of issues.
  • Fix recommendations: Provide detailed steps and considerations for resolving identified problems.
  • Use Case: When encountering a "Policy gate failed" error in crisAI, use this Skill to diagnose the issue based on the error message and logs, and apply the recommended fixes.

Quick Start

Load the crisai-debugging-playbook skill to diagnose and resolve "Policy gate failed" errors in crisAI.

Frequently Asked Questions about crisai-debugging-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a policy gate failed error in crisAI?▼

To troubleshoot a crisAI policy gate failure, analyze the specific error symptoms and logs to identify the root cause, then apply the recommended resolution steps provided by the triage runbook.

What is the best way to diagnose crisAI runtime issues like retrieval errors and tool timeouts?▼

The best way to diagnose crisAI runtime issues is performing symptom-to-cause analysis and executing discriminating experiments to narrow down the root cause of retrieval errors or tool timeouts.

Do I need specific environment configuration access to triage crisAI authentication issues?▼

Yes, resolving crisAI authentication issues requires access to crisAI logs and environment configuration to accurately diagnose the runtime failures and apply the correct fixes.

How does symptom-to-cause analysis work for resolving crisAI runtime errors?▼

Symptom-to-cause analysis works by mapping specific runtime error symptoms, such as policy failures, to their likely causes and running targeted experiments to isolate the exact issue before applying fixes.

What should I do when crisAI troubleshooting does not resolve my tool timeout issues?▼

If initial troubleshooting does not resolve tool timeouts, run further discriminating experiments against your environment configuration and logs to isolate deeper runtime anomalies causing the persistent failures.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
different-aidifferent-ai
249

debug prod issues

Diagnose Vercel production issues via live logs, deployments, and Neon Postgres.

Official
Advanced
ajianazajianaz
4

observability-monitor

Orchestrate end-to-end observability and monitoring for complex applications.

Community
Advanced
HerxinsasaHerxinsasa
1

log-analyze

Correlate text, JSON, Windows Event, and crash dump logs to identify root causes.

Community
Advanced