Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/writeup-ctfReverse engineering and fuzzing

writeup-ctf

⁨Lab/CTF: reproducible writeups; solved notes, command logs, artifacts, proof output, solver scripts, final reports, evidence checks.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/writeup-ctf

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
FmRmIibxGQ…g+AujRCg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagee3ebcb45…158d04c4
e3ebcb458c45…d0dc158d04c43 files · ⁦2.5 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-ctf/writeup-ctf@21cd568

Goal: produce reproducible challenge writeups with clear proof order, minimal noise, and reusable evidence.

When this skill applies

  • solved challenge notes, command logs, artifacts, proof output, exploit scripts, or final reports
  • tasks requiring concise reconstruction, evidence-backed steps, and reusable lessons

Operating model

  1. Classify the dominant artifact, primitive, or objective.
  2. Load the closest offensive-techniques methodology before selecting tools.
  3. Load the narrowest supporting reference only when the writeup task needs extra structure, packaging, or redaction guidance.
  4. Choose the smallest tool chain that can produce a validation signal.
  5. Record the exact proof path and stop once the objective is reproducible.

Technique integration

Primary methodology to load:

  • forensic-technique
  • evidence-before-claims
  • verification-before-completion

Use these as decision engines. This skill adds writeup structure, proof ordering, artifact packaging, and reproducibility discipline.

Quality gates

  • No claim without a validation signal: recovered secret, replayed exploit, decoded artifact, reproduced model behavior, or corroborated evidence.
  • Do not brute force before representation, constraints, and success oracle are known.
  • Keep a pivot ledger: hypothesis, evidence, result, next shortest path.
  • Keep challenge/platform/competition names out of notes and generated reports.

Resources

  • references/structure-and-proof-order.md — load when turning notes and solver output into one clean, reproducible proof path.
  • references/artifacts-redaction-and-packaging.md — load when deciding what scripts, screenshots, raw requests, hashes, and sanitized artifacts belong in the final package.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568e3ebcb45Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login