holix-self-diagnose

Solid

When the user says Holix is wrong or asks it to check itself («проверь себя», «почему ты делаешь не так», «ты отвечаешь неправильно», check yourself), call self_diagnose, then answer from the report.

AI & Automation 14 stars 2 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
55
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## When to use The user is criticizing **this agent**, not asking to debug their own code: - «проверь себя», «проверь свою работу», «самодиагностика» - «почему ты делаешь не так», «ты отвечаешь неправильно» - «check yourself», «you're answering incorrectly» ## Procedure 1. Call `self_diagnose` immediately (pass their complaint as `complaint` if useful). 2. Read `findings`, `session.tools`, `llm`, and `skill_fixes`. 3. Tell the user what actually happened (tools vs claims). Do not invent a send/write. 4. If a finding says to call another tool (`send_chat_files`, `research_site_pages`, …), call it next. 5. If `skill_fixes` staged a patch, quote the `proposal_id` and whether it is live or waiting for approval. ## Pitfalls - Do not answer the complaint from memory. The session transcript is in the tool result. - `read_file` / `cat` is not delivering a file. `self_diagnose` will flag that. - Do not auto-spawn sub-agents for this. Main agent only. ## Verification - This turn has a `self_diagnose` tool result. - The reply quotes findings (`code` + `next_action`), not a generic apology.

Details

Author
javded-itres
Repository
javded-itres/Holix
Created
3 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

diagnose

Self-diagnosis skill for 5dive agents. Trigger this skill whenever the user says something is broken, not working, or behaving unexpectedly — or when any tool or command exits with an error. Runs a structured health check covering auth state, service health, disk, memory, recent CLI errors, and skill integrity. Surfaces a root-cause summary so the agent can fix the problem itself instead of asking the user. Also exposes a security audit sub-command for SSH keys, open ports, auth failures, and risky file permissions.

1 Updated 2 days ago
5dive-ai
AI & Automation Listed

diagnose

Load when a task needs hard bugs and performance regressions, failing commands, hard-to-reproduce behavior, or unknown root causes diagnosed; use agent-introspection-debugging instead for agent/tool harness failures.

72 Updated 1 months ago
JasonxzWen
AI & Automation Listed

agent-failure-diagnosis

Diagnose why an AI agent behaved badly, using operationalised criteria that two independent reviewers can apply to the same evidence and reach the same answer. Use this whenever someone describes an agent that misbehaved, went off track, did something unexpected, ignored instructions, made things up, went beyond its scope, got stuck in a loop, lied about what it did, or "went rogue" — and whenever reviewing agent traces, logs, or transcripts to work out what went wrong. Use it for post-incident analysis, for design reviews asking "how could this fail?", and when someone needs to classify agent failures consistently enough to spot patterns across many incidents. Reach for this even when the user just wants an explanation rather than a formal report, because the classification is what makes the explanation defensible later.

0 Updated 3 days ago
patkusch