Skip to content
skillsafebeta
← Report library
Purpose / Other

Investigate First Skill Security Audit

What the author says it does (original text)

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.

Independent security check

No obvious risks found in this check

Files checked
2
Risks found
0
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

1 instruction sections

The Skill instructs the agent to collect evidence first, distinguish observed symptoms from inferred causes, and rank hypotheses before considering product-code changes.

View source
SKILL.md:8In the instructionsOpen original file
Gather evidence before changing product code.- Separate observed symptom from inferred cause.- Trace inputs, state transitions, ownership boundaries, and failure output.- Rank hypotheses by evidence and cheap falsification value.- Do not edit until one credible mechanism explains evidence.- Stop exploration when evidence is sufficient to name cause or exact blocker.

The Skill says to stop investigating once the cause or exact blocker can be identified, report the cause and proof, and avoid implementing a fix unless the task authorizes it.

View source
SKILL.md:14In the instructionsOpen original file
- Do not edit until one credible mechanism explains evidence.- Stop exploration when evidence is sufficient to name cause or exact blocker.Report cause and proof. Make no fix unless task authorizes implementation.

The interface default prompt invokes the Skill to diagnose a failure before proposing edits.

View source
agents/openai.yaml:1In the instructionsOpen original file
interface:  display_name: "Investigate First"  short_description: "Find credible cause before editing code"  default_prompt: "Use $investigate-first to diagnose this failure before proposing edits."
Start here · InstructionsSKILL.md
investigate-first
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records2 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included
  • agents/openai.yamlFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
  • agents/openai.yamlSupporting file
Lines read
22
File checksum (to compare versions)
6c59695a99e18df2d99d6f9852214a19910e0dde16424ec816b90a4fd00f56e4