Fähigkeiten investigate-first
📦

investigate-first

Inhaltsrevision r1 Sicher

Investigate Failures Before Editing Code

Premature edits can hide causes and introduce new failures. This skill organizes evidence, ranks hypotheses, and identifies a credible mechanism before implementation.

Unterstützt: Claude Codex Code(CC)
🥉 78 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
Review the Skillstore skill "investigate-first" from https://skillstore.io/skills/juliusbrussee-investigate-first.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-investigate-first/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/juliusbrussee-investigate-first.md Signiertes manifest GET /api/skills/juliusbrussee-investigate-first/manifest Signiertes lockfile GET /api/skills/juliusbrussee-investigate-first/lockfile

Testen

„investigate-first“ wird verwendet. The checkout test fails twice weekly, but reruns pass. Recent edits changed retry timing.

Erwartetes Ergebnis:

  • Observed: the first run sometimes times out, while immediate reruns pass.
  • Leading hypothesis: shared setup becomes ready after the first attempt.
  • Next test: record setup readiness and request timestamps on the first run.

„investigate-first“ wird verwendet. API latency increased after deployment, with no increase in request volume.

Erwartetes Ergebnis:

The strongest evidence points to a new downstream wait. Compare dependency timing before and after deployment to confirm the responsible transition.

„investigate-first“ wird verwendet. A report is empty for one customer, but logs and sample data are unavailable.

Erwartetes Ergebnis:

No cause can be supported yet. The exact blocker is missing customer-specific input, filtering decisions, and report generation output.

Sicherheitsaudit

Sicher
v1 • 12.8.2026 Versionsbericht öffnen

The two prompt-only files contain no executable code, external access, credential handling, or suspicious instructions. No static or semantic security findings were identified.

2
Gescannte Dateien
22
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/juliusbrussee-investigate-first/security.svg)](https://skillstore.io/skills/juliusbrussee-investigate-first?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/juliusbrussee-investigate-first?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-investigate-first/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/juliusbrussee-investigate-first.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

juliusbrussee. (2026). investigate-first security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1

BibTeX-Zitat

@techreport{juliusbrussee-juliusbrussee-investigate-first-2026, author = {juliusbrussee}, title = {investigate-first security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "investigate-first security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "juliusbrussee" date-released: "2026-08-12" url: "https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1" identifiers: - type: other value: "skillstore:juliusbrussee-investigate-first:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
91
Spezifikationskonformität

Was Sie erstellen können

Diagnose an Intermittent Test Failure

Organize observations and rank likely mechanisms before modifying test or product code.

Investigate a Performance Regression

Trace changed inputs and state transitions to identify evidence supporting the slowdown.

Clarify an Ambiguous Defect Report

Separate reported symptoms from assumptions and define the next useful evidence to collect.

Diese Prompts ausprobieren

Review a Failure 
Investigate this failure before proposing edits: [symptom]. Separate observations from assumptions and list the evidence needed next.
Rank Root Cause Hypotheses 
Analyze [failure details]. Rank plausible causes by supporting evidence, conflicting evidence, and the cheapest test that could disprove each cause.
Trace a Regression 
Investigate the regression from [baseline] to [current behavior]. Trace inputs, state transitions, ownership boundaries, and outputs without changing code.
Build an Evidence-Backed Diagnosis 
Evaluate [system context and evidence]. Identify the most credible mechanism, prove each causal step, and name the exact blocker if evidence remains insufficient.

Bewährte Praktiken

  • Provide exact symptoms, timestamps, reproduction steps, and relevant recent changes.
  • Label observations, assumptions, and hypotheses separately.
  • Prefer inexpensive tests that can quickly disprove the leading explanation.

Vermeiden

  • Do not treat temporal correlation as proof of causation.
  • Do not edit multiple components before identifying a supported mechanism.
  • Do not continue exploring after evidence proves the cause or identifies the exact blocker.

Häufig gestellte Fragen

When should I use this skill?
Use it for unknown causes, intermittent failures, performance regressions, or investigations with competing explanations.
Will this skill edit my code?
It will not edit code unless your task explicitly authorizes implementation after diagnosis.
What information should I provide?
Provide symptoms, expected behavior, reproduction steps, logs, timestamps, recent changes, and relevant system boundaries.
How does it rank hypotheses?
It compares each hypothesis with supporting evidence and prioritizes inexpensive tests that could disprove it.
What happens when evidence is insufficient?
The skill identifies the exact missing evidence or access that blocks a credible diagnosis.
Can it investigate performance problems?
Yes. It can trace inputs, state transitions, boundaries, and output timing to identify a supported regression mechanism.

Entwicklerdetails

Lizenz

MIT

Skillstore-Revision

r1

Versionshinweis

Der Autor hat keine Version angegeben.

Repository

https://github.com/juliusbrussee/caveman/tree/a0109974ea3258a14aadaef1ed1f8ff2837d30d5/skills/investigate-first

Ref.

d8fdd465806692db394c1b3f87ab3a021fe733d2

Aktualität der Wartung

13.8.2026

Nutzung

0 Downloads · 0 Aufrufe

Dateistruktur

📁 agents/

📄 openai.yaml

📄 SKILL.md