Habilidades investigate-first
📦

investigate-first

Revisión del contenido r1 Seguro

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.

Compatible con: Claude Codex Code(CC)
🥉 78 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente
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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/juliusbrussee-investigate-first.md Manifest firmado GET /api/skills/juliusbrussee-investigate-first/manifest Lockfile firmado GET /api/skills/juliusbrussee-investigate-first/lockfile

Pruébalo

Usando "investigate-first". The checkout test fails twice weekly, but reruns pass. Recent edits changed retry timing.

Resultado esperado:

  • 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.

Usando "investigate-first". API latency increased after deployment, with no increase in request volume.

Resultado esperado:

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

Usando "investigate-first". A report is empty for one customer, but logs and sample data are unavailable.

Resultado esperado:

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

Auditoría de seguridad

Seguro
v1 • 12/8/2026 Abrir el informe versionado

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
Archivos escaneados
22
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.
Auditado por: codex
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

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

Insignia Markdown

[![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)

Insignia 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>

Tarjeta para insertar

<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>
Citas académicas (APA · BibTeX · CFF)

Cita APA

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

Cita 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"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
55
Arquitectura
85
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

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.

Prueba estos prompts

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.

Mejores prácticas

  • 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.

Evitar

  • 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.

Preguntas frecuentes

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.

Detalles del desarrollador

Licencia

MIT

Revisión de Skillstore

r1

Aviso de versión

El autor no declaró una versión.

Repositorio

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

Ref.

d8fdd465806692db394c1b3f87ab3a021fe733d2

Actualidad del mantenimiento

13/8/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📁 agents/

📄 openai.yaml

📄 SKILL.md