update-threat-db

Integrate new threat intelligence data into threat-db.yaml with deduplication and categorization.

Updated May 30, 2026
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill update-threat-db-alexica00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-threat-db
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/update-threat-db
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill update-threat-db-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams maintain an up-to-date AI agent threat intelligence database by aggregating new malicious authors, malicious skills, CVEs, campaigns, IOCs, and defensive resources into threat-db.yaml, ensuring deduplication and data integrity.

Core Features & Use Cases

  • Deduplicate and categorize new threat intel findings
  • Validate YAML, bump version, update date, and append sources
  • Provide auditable change history and ensure data integrity for security reviews

Quick Start

Invoke the update-threat-db skill with an optional --source URL to ingest the latest threat intelligence into threat-db.yaml.

Frequently Asked Questions about update-threat-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a threat intelligence database with new CVEs and IOCs?

To update a threat intelligence database, you can ingest new CVEs and IOCs by providing a source URL. The skill analyzes recent research, deduplicates entries, and categorizes findings into structured threat intelligence data.

How do I deduplicate and categorize malicious skills into a YAML file?

You can deduplicate and categorize malicious skills into a YAML file by integrating new threat intelligence data. The process categorizes findings into malicious_authors, malicious_skills, and malicious_skill_patterns while validating YAML syntax.

What is the best way to maintain an auditable change history for threat intelligence?

The best way to maintain an auditable change history for threat intelligence is to append new sources, bump the version, and update the date within your database. This preserves existing data and ensures data integrity for security reviews.

Can I automate threat intelligence triage and categorize attack techniques into YAML?

Yes, you can automate threat intelligence triage by invoking the skill with an optional source URL. It categorizes new findings into attack_techniques, campaigns, and defensive_resources while validating the YAML syntax automatically.

Does updating a threat-db YAML file require external dependencies?

Updating a threat-db YAML file does not require external dependencies. The skill operates independently to validate YAML syntax, deduplicate entries, and bump the version without needing additional components or libraries.