Skip to content
Back to skills

Headless Ghidra Intake

ASecurity

P0 phase skill for Headless Ghidra intake. Use when a target binary/archive needs identity confirmation, workspace initialization, Ghidra discovery, binary inspection, or analysis scope setup before any Ghidra analysis runs.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
toolsbackend

Works with

  • cli

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned October 17, 2026

npx -y skills add NetVar1337/agent-skill-canon --skill headless-ghidra-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Headless Ghidra Intake?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Headless Ghidra Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/netvar1337-headless-ghidra-intake/badge)](https://www.skillsdirectory.com/skills/netvar1337-headless-ghidra-intake)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "headless-ghidra-intake"
description: "P0 phase skill for Headless Ghidra intake. Use when a target binary/archive needs identity confirmation, workspace initialization, Ghidra discovery, binary inspection, or analysis scope setup before any Ghidra analysis runs."
phase: "P0"
---

# Headless Ghidra Intake — P0

P0 prepares a target for the rest of the workflow. It is responsible for
turning an input binary or archive path into a valid `ghidra-agent-cli`
workspace target and recording the initial analysis scope.

## Required ghidra-agent-cli Commands

- `ghidra-agent-cli workspace init`
- `ghidra-agent-cli ghidra discover`
- `ghidra-agent-cli inspect binary`
- `ghidra-agent-cli scope show`
- `ghidra-agent-cli scope set`
- `ghidra-agent-cli scope add-entry`
- `ghidra-agent-cli scope remove-entry`
- `ghidra-agent-cli gate check --phase P0`

Archive normalization and any target-specific bootstrap scripts may still
run as backend details until the CLI exposes them directly.

## Inputs

- User-provided binary or archive path
- Workspace root
- Local environment needed for Ghidra discovery

## Outputs

- `targets/<target-id>/ghidra-projects/`
- `artifacts/<target-id>/pipeline-state.yaml`
- `artifacts/<target-id>/scope.yaml`
- Optional phase-owned intake records under `artifacts/<target-id>/intake/`

## Exit Expectations

- Target workspace exists and is addressable through `--target <id>`.
- `pipeline-state.yaml` records the selected binary path.
- `scope.yaml` records the selected functions, addresses, symbols, or explicit
  whole-target scope.
- Ghidra discovery and binary inspection have been run and reviewed.

## Constraints

- Do not run actual Ghidra analysis in this phase.
- Do not write baseline, evidence, decompilation, or verification outputs.
- Do not bypass `ghidra-agent-cli workspace init`, `ghidra discover`, or
  `inspect binary` for supported steps.
- Do not create or run a new Ghidra script if the CLI lacks a capability; pause
  and ask the user first.

## Next Step

- P0 gate passes → `headless-ghidra-baseline`

Files in this skill

  • README.ja-JP.md4.9 KB
  • README.md4.4 KB
  • README.zh-CN.md4.1 KB
  • SKILL.md2 KB
  • agents/openai.yaml43 B
  • examples/intake-speckit-handoff.md2.9 KB
  • planning-brief.md4.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.