investigate-first
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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « investigate-first ». The checkout test fails twice weekly, but reruns pass. Recent edits changed retry timing.
Résultat attendu:
- 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.
Utilisation de « investigate-first ». API latency increased after deployment, with no increase in request volume.
Résultat attendu:
The strongest evidence points to a new downstream wait. Compare dependency timing before and after deployment to confirm the responsible transition.
Utilisation de « investigate-first ». A report is empty for one customer, but logs and sample data are unavailable.
Résultat attendu:
No cause can be supported yet. The exact blocker is missing customer-specific input, filtering decisions, and report generation output.
Audit de sécurité
SûrThe two prompt-only files contain no executable code, external access, credential handling, or suspicious instructions. No static or semantic security findings were identified.
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/juliusbrussee-investigate-first?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
juliusbrussee. (2026). investigate-first security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces prompts
Investigate this failure before proposing edits: [symptom]. Separate observations from assumptions and list the evidence needed next.
Analyze [failure details]. Rank plausible causes by supporting evidence, conflicting evidence, and the cheapest test that could disprove each cause.
Investigate the regression from [baseline] to [current behavior]. Trace inputs, state transitions, ownership boundaries, and outputs without changing code.
Evaluate [system context and evidence]. Identify the most credible mechanism, prove each causal step, and name the exact blocker if evidence remains insufficient.
Bonnes pratiques
- 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.
Ăviter
- 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.
Foire aux questions
When should I use this skill?
Will this skill edit my code?
What information should I provide?
How does it rank hypotheses?
What happens when evidence is insufficient?
Can it investigate performance problems?
Détails du développeur
Auteur
juliusbrusseeLicence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
d8fdd465806692db394c1b3f87ab3a021fe733d2
Récence de maintenance
13/08/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers