ti-ingest — Claude Code skill: what it does, how to install
ti-ingest parses threat-intel payloads with CVEs and affected assets into queue files for validation agents.
MIT 147 installs ★ 632 updated 2026-07-29
npx skills add transilienceai/communitytools --skill ti-ingest -a claude-codeWhat ti-ingest does
The skill ingests vulnerability signals either via prompt invocation on a local JSON file or on a cron schedule checking {OUTPUT_DIR}/inbox/. Execution relies on tools/ti-ingest.py, demanding signal_id, cve, assets, and claim keys in every record.
It enriches each referenced vulnerability by querying NVD metrics through tools/nvd-lookup.py. Should the NVD lookup fail, the process continues without dropping the record: it writes nvd: null and stores the diagnostic string in nvd_error. Duplicate (asset, cve) pairs are discarded unless an earlier attempt was rejected and the incoming signal carries higher confidence.
Ingestion writes queued scope rows directly to queue/scope-{ts}-{asset_id}-{cve}.json. It never executes exploit payloads, and every target asset is matched against artifacts/org-surface.json to flag uninventoried entries.
What it helps with
- process threat-intelligence payloads into validation queue records
- enrich incoming CVE entries with NVD severity and CWE metrics
- deduplicate asset vulnerability pairs across task queues
- flag unknown organization assets before downstream verification runs
Example prompts for the agent
- Ingest the security findings payload from
signal.json - Run ti-ingest on the latest threat report in the inbox folder
How to install ti-ingest
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill ti-ingest -a claude-code2Manually: put the files in place
~/.claude/skills/ti-ingest/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ti-ingest/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill ti-ingest -a codex2Manually: put the files in place
.agents/skills/ti-ingest/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill ti-ingest -a cursor2Manually: put the files in place
.cursor/skills/ti-ingest/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install transilienceai/communitytools skills/ti-ingest2Manually: put the files in place
.github/skills/ti-ingest/SKILL.md1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill ti-ingest -a gemini-cli2Platform CLI
gemini skills install https://github.com/transilienceai/communitytools --path skills/ti-ingestManually: put the files in place
.devin/skills/ti-ingest/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill ti-ingest -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ti-ingest
How to install ti-ingest in Claude Code?
Run npx skills add transilienceai/communitytools --skill ti-ingest -a claude-code in your terminal.
What does the ti-ingest skill do?
It parses threat intelligence reports, retrieves NVD data for CVEs, verifies targets against an asset inventory, and queues tasks for validation agents.
What happens when an asset is not found in the inventory?
The item is still queued as a JSON file, but receives an unknown_asset: true flag so subsequent validation tasks ignore it.
Source text
SKILL.md · MIT
---
name: ti-ingest
description: Threat-intel signal ingest — converts a CVE + affected-asset + claim payload into a queued engagement-scope row for the validation pipeline.
---
# Threat-Intel Signal Ingest
Convert a threat-intel signal into a queued engagement-scope row that the Exploitability Validation Run (cloud-agent task #3) consumes.
## Trigger
Two modes:
- **Prompt-invoked**: an analyst runs the skill against a `signal.json` they have on hand.
- **Scheduled poll**: the cloud-agent runtime polls `{OUTPUT_DIR}/inbox/` on a cron (default every 15 minutes) and processes any new signal files it finds.
## Workflow
1. **Read the payload** — `tools/ti-ingest.py --in <path-or-stdin>`.
2. **Validate schema** — required keys: `signal_id`, `cve` (one or more), `assets` (one or more), `claim`. Optional: `confidence`, `source`, `references`.
3. **Enrich with NVD** — for every CVE in the payload, run `tools/nvd-lookup.py <CVE>` and attach `{score, severity, cwe}` to the row.
4. **De-dup** — skip rows whose `(asset, cve)` pair already exists in `queue/scope-*.json`. Re-queue only if the prior row's status is `REJECTED` AND the TI signal carries a higher `confidence` than the last attempt.
5. **Write queue row** — one JSON file per `(asset, cve)` pair at `queue/scope-{ts}-{asset_id}-{cve}.json`. The Validation Run task picks these up.
## Output
```
{OUTPUT_DIR}/
inbox/
signal-{ts}.json # raw payload, kept for audit
queue/
scope-{ts}-{asset}-{cve}.json
```
Per scope row:
```json
{
"scope_id": "scope-20260513-asset42-CVE-2024-12345",
"signal_id": "ti-2026-0042",
"asset": {"id": "asset42", "url": "https://app.example.com", "tier": "revenue"},
"cve": "CVE-2024-12345",
"nvd": {"score": 9.8, "severity": "CRITICAL", "cwe": "CWE-79"},
"claim": "Reflected XSS via search parameter",
"confidence": "high",
"source": "vendor-advisory",
"references": ["https://..."],
"queued_at": "2026-05-13T10:00:00Z",
"status": "queued"
}
```
## Rules
1. **Idempotent.** Re-running on the same payload must not produce duplicate queue rows.
2. **No execution.** Ingest never runs PoCs. It only queues scope for downstream tasks.
3. **Audit trail.** Raw payload is always copied to `inbox/` before any transformation.
4. **NVD failures are non-blocking.** If `nvd-lookup` errors, write the row with `nvd: null` and `nvd_error: "..."`; do not drop the signal.
5. **Asset must be in inventory.** Cross-check `asset.id` against `artifacts/org-surface.json` (from Org Recon Refresh task). Unknown assets get a row but flagged `unknown_asset: true` so the validator skips them.
## References
- `reference/ingest-schema.md` — full input/output JSON schemas.
© transilienceai · MIT · transilienceai/communitytools