agentleFS
Sign inStart free
z91772524-aiz91772524-ai/pojia-next-mac/skills/pojia-lab/SKILL.md

pojia-lab

Skill39 starsChanged 34 days agoMITView on GitHub

Create reproducible technical research workspaces for reverse engineering, penetration testing, memory analysis, fuzzing, malware analysis, protocol research, and CTF cases. Use when Codex needs to organize artifacts, hash evidence, create case directories, track commands and observations, build local test harnesses, collect logs/PCAP/dumps, preserve originals, generate manifests, or package a reproducible technical report.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a clean, repeatable case before complex analysis.

    line 17
  2. Very specific:

    Run scripts/new_case.py <name> --root <directory> to create a case workspace.

    line 21
  3. Very specific:

    Put untouched inputs under artifacts/original/.

    line 22
  4. Very specific:

    Run scripts/hash_artifact.py <path> --manifest <case>/manifest.json for each input.

    line 23
  5. Very specific:

    Keep derived files under work/, scripts under scripts/, evidence under evidence/, and final outputs under output/.

    line 24
  6. Distinctive:

    Prefer deterministic scripts and configuration over manual-only steps.

    line 36
  7. Distinctive:

    Keep service ports/processes and cleanup commands in the case manifest.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Pojia Lab

Create a clean, repeatable case before complex analysis.

Start

  1. Run scripts/new_case.py <name> --root <directory> to create a case workspace.
  2. Put untouched inputs under artifacts/original/.
  3. Run scripts/hash_artifact.py <path> --manifest <case>/manifest.json for each input.
  4. Keep derived files under work/, scripts under scripts/, evidence under evidence/, and final outputs under output/.

Select references

  • Case lifecycle, commands, snapshots, local services: read references/case-workflow.md.
  • Evidence, hashes, timestamps, logs, PCAP, dumps, and reporting: read references/evidence.md.
  • Full-speed CTF intake, category triage, solve engineering, flag verification, and Writeup packaging: read eferences/ctf-operations.md.

Execute

  • Record tool versions, exact commands, environment, timestamps, and output paths.
  • Prefer deterministic scripts and configuration over manual-only steps.
  • Track assumptions and failed hypotheses in notes.md.
  • Keep service ports/processes and cleanup commands in the case manifest.

Deliver

Package the manifest, scripts, evidence index, key artifacts, results, verification commands, and cleanup instructions.

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.

Reviews can't be read right now.

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