agentleFS
Sign inStart free
MysterionRiseMysterionRise/ctf-kit/skills/analyze/SKILL.md

analyze

Skill12 starsChanged 9 months agoMITView on GitHub

Analyze CTF challenge files to detect category and suggest next steps. Use when starting a new challenge, receiving unknown files, or needing triage. Triggers: file, strings, xxd, binwalk output, unknown binaries, .bin .dat .raw .enc files, "what is this file", "analyze this", "identify challenge type". Routes to crypto/forensics/stego/web/pwn/ reverse/osint/misc skills based on detection.

70 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, revise and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • stormlightlabsSkill

    revise

    Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.

    Also in 3 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 6 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 projects that use this

  • H-mmerSkill

    submit

    Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this command when you have new challenge files and need to:

    line 18
  2. Very specific:

    All scripts produce a === PARSED RESULTS (JSON) === section with structured data.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CTF Analyze

Analyze challenge files to determine type and suggest approaches.

When to Use

Use this command when you have new challenge files and need to:

  • Identify the challenge category (crypto, forensics, stego, web, pwn, reversing, OSINT, misc)
  • Detect file types and formats
  • Get initial suggestions for tools to use
  • Understand what you're working with

Bundled Scripts

  • check-tools.sh — Verify required analysis tools are installed
  • triage.sh — Multi-step triage pipeline: file type → strings → binwalk → category suggestion. Produces a JSON summary with detected category, confidence score, and recommended next skill.
  • run-strings.sh — Extract strings with pattern detection (flags, URLs, hashes, credentials). Outputs JSON with categorized findings.

Instructions

  1. First check tool availability: bash scripts/check-tools.sh

  2. Recommended: Run the full triage pipeline for automatic category detection:

    bash scripts/triage.sh $ARGUMENTS

    The triage script chains: file → strings → binwalk → exiftool, then outputs a JSON summary including:

    • category: detected challenge type (crypto, forensics, stego, etc.)
    • confidence: detection confidence (0-100%)
    • suggested_skill: which /ctf-kit:* command to use next
    • findings: flags, URLs, hashes, base64 strings found
    • embedded_signatures: files hidden inside the challenge file

  3. For strings-only analysis with pattern detection:

    bash scripts/run-strings.sh $ARGUMENTS

  4. Or run the CLI analysis:

    ctf analyze $ARGUMENTS
  5. Read the JSON output at the end of each script. It contains structured data you can use to decide next steps. The suggestions field tells you exactly what to do next.
  6. Based on the triage results, use the recommended skill:
    • /ctf-kit:crypto for cryptography challenges
    • /ctf-kit:forensics for forensics challenges
    • /ctf-kit:stego for steganography challenges
    • /ctf-kit:web for web security challenges
    • /ctf-kit:pwn for binary exploitation challenges
    • /ctf-kit:reverse for reverse engineering challenges
    • /ctf-kit:osint for OSINT challenges
    • /ctf-kit:misc for miscellaneous challenges

Output Format

All scripts produce a === PARSED RESULTS (JSON) === section with structured data. Key fields:

FieldDescription
categoryDetected challenge category
confidenceDetection confidence (0.0-1.0)
suggested_skillWhich skill to invoke next
findings.flagsAny flags found in strings
suggestionsActionable next steps

Example Usage

/ctf-kit:analyze challenge.bin
/ctf-kit:analyze ./challenge-folder/

Related Commands

  • /ctf-kit:crypto - Crypto-specific analysis
  • /ctf-kit:forensics - Forensics analysis
  • /ctf-kit:stego - Steganography analysis

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free