Install any skill in seconds. Free to start, no credit card required.
Get Started Free →transilienceai/ti-ingest
Threat-intel signal ingest — converts a CVE + affected-asset + claim payload into a queued engagement-scope row for the validation pipeline.
Passed 16 of 20 test cases with the skill, and 5 of 20 without it.
and 14 more in the full report
12 fixed6 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
A new signal for `(asset-3, CVE-2024-9999)` has `confidence: high`. An existing queue file shows `status: queued` (not REJECTED) with `confidence: low`. Does the higher confidence force a new queue entry?
| Checked | Without skill | With skill |
|---|---|---|
| Directs skipping row creation because re-queueing requires the prior status to be REJECTED. | Missed | Passed |
The instructions your model reads when the skill loads.
Convert a threat-intel signal into a queued engagement-scope row that the Exploitability Validation Run (cloud-agent task #3) consumes.
Two modes:
signal.json they have on hand.{OUTPUT_DIR}/inbox/ on a cron (default every 15 minutes) and processes any new signal files it finds.tools/ti-ingest.py --in <path-or-stdin>.signal_id, cve (one or more), assets (one or more), claim. Optional: confidence, source, references.tools/nvd-lookup.py <CVE> and attach {score, severity, cwe} to the row.(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.(asset, cve) pair at queue/scope-{ts}-{asset_id}-{cve}.json. The Validation Run task picks these up.{OUTPUT_DIR}/
inbox/
signal-{ts}.json # raw payload, kept for audit
queue/
scope-{ts}-{asset}-{cve}.json
Per scope row:
{
"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",
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.