diagnostic-action
Diagnose Root Causes and Incidents
Problems are hard to explain when symptoms, evidence, and assumptions are mixed together. This skill structures diagnostic reasoning into hypotheses, mechanisms, confidence, and missing data.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "diagnostic-action" from https://skillstore.io/skills/bellabe-diagnostic-action.md and its manifest at https://skillstore.io/api/skills/bellabe-diagnostic-action/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "diagnostic-action". Checkout latency increased after a release, but error rates stayed normal.
Expected outcome:
The likely causes are a slower query path, a cache miss pattern, or added downstream latency. The next data needed is trace timing by dependency.
Using "diagnostic-action". A weekly report stopped arriving after a permissions change.
Expected outcome:
The strongest hypothesis is blocked access to the report source. Other causes include scheduler failure or changed notification rules. Audit logs would disambiguate.
Using "diagnostic-action". A test suite became flaky only on CI.
Expected outcome:
Likely causes include timing assumptions, resource contention, or environment differences. Compare local and CI runtime data before selecting a root cause.
Security Audit
SafeThe static system reconnaissance alert is a false positive because SKILL.md line 13 only shows an example user question for diagnostic use. I found no prompt injection, exfiltration intent, network behavior, scripts, or external command guidance in the reviewed file.
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bellabe-diagnostic-action/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bellabe-diagnostic-action?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bellabe-diagnostic-action?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bellabe-diagnostic-action/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bellabe-diagnostic-action.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
BellaBe. (2026). diagnostic-action security audit report (audit version 9) [Author version 1]. Skillstore. https://skillstore.io/skills/bellabe-diagnostic-action/audits/9BibTeX citation
@techreport{bellabe-bellabe-diagnostic-action-2026,
author = {BellaBe},
title = {diagnostic-action security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bellabe-diagnostic-action/audits/9},
note = {Author version 1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "diagnostic-action security audit report (audit version 9)"
version: "1"
type: report
authors:
- name: "BellaBe"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/bellabe-diagnostic-action/audits/9"
identifiers:
- type: other
value: "skillstore:bellabe-diagnostic-action:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Investigate Service Incidents
An operations engineer can compare likely failure causes after an outage or degraded service.
Explain Product Failures
A product manager can understand why a feature failed before requesting remediation.
Debug Unclear Behavior
A developer can organize symptoms, evidence, and unknowns before making code changes.
Try These Prompts
Diagnose why this happened: [symptoms]. Restate the scope, list likely causes, and explain what evidence would separate them.
Analyze these symptoms and logs: [details]. Rank possible causes by likelihood and impact, with evidence for and against each.
Build a diagnostic matrix for [incident]. Include mechanisms, supporting evidence, contradicting evidence, confidence, and missing data.
Perform a full root cause analysis for [incident]. Scope the problem, generate hypotheses, rank them, and list decisive follow-up data.
Best Practices
- Provide symptoms, timing, recent changes, and known non-causes.
- Ask for confidence levels when decisions depend on certainty.
- Separate diagnosis from remediation until the cause is clear.
Avoid
- Using the skill to request fixes before diagnosis is complete.
- Providing only a conclusion without symptoms or evidence.
- Treating ranked hypotheses as proven causes.