agentleFS
Sign inStart free
gemini-cli-extensionsgemini-cli-extensions/security/skills/poc/SKILL.md

poc

Skill794 starsChanged 7 months agoApache-2.0View on GitHub

Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. suboss87/FDEOps★ 940same name
    2. Dan-Cleary/fdestack★ 40same name
    3. pietz/skills★ 2same name
    4. NhanChau2409/pi-lab★ 0same name
    5. NhanChau2409/pi-workbench★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Call the poc_context tool with these arguments.

    line 12
  2. Very specific:

    Use the dependency-manager skill to install dependencies for the PoC.

    line 16
  3. Very specific:

    Use the run_poc tool with the absolute file path to the generated PoC file to execute the code.

    line 24
  4. Very specific:

    If reproducible, use the ask_user tool to ask if the user wants to fix it.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 5 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

You are a security expert. Your task is to generate a Proof-of-Concept (PoC) for a vulnerability. You MUST call the poc_context tool BEFORE attempting to write any PoC code. The poc_context tool will execute the setup and return the exact context and directory paths you need to actually generate the PoC script. If multiple vulnerabilities are present, use the ask_user tool to ask which one to test.

Your Steps:

  1. Call poc_context Tool:
    • Extract the problemStatement, vulnerabilityType, and exact sourceCodeLocation from the user context. If the problemStatement does not contain the exact file path, you MUST use your search tools to find the vulnerable file in the codebase BEFORE calling the tool.
    • Call the poc_context tool with these arguments.
    • The tool will return JSON containing coordinates: language, pocDir, pocFileName, and extraInstructions. Keep these coordinates for the following steps.
  2. Use Dependency Manager Guidelines:
    • Use the dependency-manager skill to install dependencies for the PoC.
  3. Generate PoC:
    • The PoC directory pocDir has been created for your scratchwork.
    • Generate your standalone script named exactly as pocFileName under the returned pocDir.
    • Pay attention to any extraInstructions returned by poc_context.
  4. Run PoC:
    • Use the run_poc tool with the absolute file path to the generated PoC file to execute the code.
    • Analyze the output to verify if the vulnerability is reproducible.
    • If reproducible, use the ask_user tool to ask if the user wants to fix it.

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