agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/PromptKit/.github/skills/ingest-cwe-taxonomies/SKILL.md

ingest-cwe-taxonomies

Skill109 starsChanged 3 months agoMITView on GitHub

Ingest the official MITRE CWE database and generate per-domain security audit taxonomies for PromptKit. Use this skill when the user wants to update CWE taxonomies, ingest a new CWE version, or regenerate domain mappings from the CWE corpus.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .github/prompts/ingest-cwe-taxonomies.prompt.md before doing anything else.

    line 32
  2. Very specific:

    Ask the user for the CWE source (path or latest).

    line 34
  3. Distinctive:

    Follow all six phases defined in the prompt file: Acquisition, Normalization, Domain Mapping, Taxonomy Generation, Integration, and …

    line 35
  4. Distinctive:

    Do NOT skip the sanity checks in Phase 6.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- Generated by PromptKit — edit with care -->

You must read and execute the prompt file at .github/prompts/ingest-cwe-taxonomies.prompt.md. Treat it as the complete, self-contained instruction set for the CWE ingestion pipeline.

Inputs

  • CWE source: A local path to a CWE XML file, or latest to download the current release from https://cwe.mitre.org/data/xml/cwec_latest.xml.zip.
  • Any overrides to the domain registry or mapping rules the user specifies.

Output

  • Per-domain taxonomy files at taxonomies/cwe-<domain>.md (13 domains)
  • Normalized CWE data at data/cwe/<version>/
  • Updated manifest.yaml with new taxonomy entries
  • Reusable ingestion script at scripts/ingest-cwe.py
  • Diff report if a previous CWE version exists

Workflow

  1. Read .github/prompts/ingest-cwe-taxonomies.prompt.md before doing anything else.
  2. Ask the user for the CWE source (path or latest).
  3. Follow all six phases defined in the prompt file: Acquisition, Normalization, Domain Mapping, Taxonomy Generation, Integration, and Verification.
  4. Do NOT skip the sanity checks in Phase 6.

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