Навыки investigate-first
📦

investigate-first

Ревизия содержимого r1 Безопасно

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.

Поддерживает: Claude Codex Code(CC)
🥉 78 Бронза

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента
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.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Протестировать

Использование «investigate-first». The checkout test fails twice weekly, but reruns pass. Recent edits changed retry timing.

Ожидаемый результат:

  • 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». API latency increased after deployment, with no increase in request volume.

Ожидаемый результат:

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

Использование «investigate-first». A report is empty for one customer, but logs and sample data are unavailable.

Ожидаемый результат:

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

Аудит безопасности

Безопасно

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
Просканировано файлов
22
Проанализировано строк
0
Пункты проверки
0
Ложные срабатывания проигнорированы
Последний завершенный статический и семантический аудит не обнаружил подтвержденных проблем безопасности. Это не доказывает отсутствие побочных эффектов у навыка.
Аудитор:: codex
Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет
Оценка безопасности

Копировать ссылку на отчёт

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

Значок 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)

Значок 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>

Встраиваемая карточка

<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>
Академические ссылки (APA · BibTeX · CFF)

Цитата APA

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

Цитата 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"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний
55
Архитектура
85
Сопровождаемость
87
Контент
65
Сообщество
91
Соответствие спецификации

Что вы можете построить

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.

Попробуйте эти промпты

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.

Лучшие практики

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

Избегать

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

Часто задаваемые вопросы

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.

Сведения для разработчиков

Автор

juliusbrussee

Лицензия

MIT

Ревизия Skillstore

r1

Примечание о версии

Автор не указал версию.

Ссылка

d8fdd465806692db394c1b3f87ab3a021fe733d2

Актуальность поддержки

13.08.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📁 agents/

📄 openai.yaml

📄 SKILL.md