cti-setup
Use when the user wants to configure API keys for the CTI skills pack, asks "how do I set up keys", "configure VirusTotal", "add my Shodan key", or runs /cti-setup. Walks through API key configuration inside Claude Code without needing to run a shell script. Also handles re-running setup, adding individual keys, and verifying that configured keys work.
Liberty91LTD · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Liberty91LTD/cti-skills --skill cti-setupAbout this skill
name: cti-setup description: Use when the user wants to configure API keys for the CTI skills pack, asks "how do I set up keys", "configure VirusTotal", "add my Shodan key", or runs /cti-setup. Walks through API key configuration inside Claude Code without needing to run a shell script. Also handles re-running setup, adding individual keys, and verifying that configured keys work. metadata: version: 1.0.0 tags: [setup, configuration, onboarding]
cti-setup
In-chat configuration of API keys for the threat-intel integrations bundled with this pack. Use this when the user is in Claude Code and doesn't want to drop to a shell to run ./scripts/setup.sh.
When to invoke
- User asks "how do I set up keys", "configure my API keys", "add a VirusTotal key", etc.
- User runs
/cti-setup - A
lookup-*skill failed because a key is missing and you want to offer to add it - After install via
/plugin marketplace addornpx(no shell setup ran)
What you do
- Check current state. Read
.claude/settings.local.json. If it's missing or has noenvblock, the user has zero keys configured. If it has some, list which are present and which are missing. - Tell the user the menu. Present the services in a table with: name, env variable, free-tier limit, signup URL. Make clear all are optional and that the pack degrades gracefully.
- Ask which to configure. Let the user provide one, several, or all. Don't force them through every prompt.
- Receive the keys. When the user shares a key, treat it as sensitive — do not echo it back in plain text in your response (refer to it as
your VirusTotal keyor the masked tail…<last 4 chars>). - Write the merged file. Use the non-destructive merge below — preserve every other field in
settings.local.json. - Offer to verify. Ask if they want you to dry-run each configured key against its CLI to confirm it's wired up.
- Tell them what's next. "Try
/ip-investigation 8.8.8.8" or similar concrete next command.
The services
| Service | Env variable | Free tier | Signup |
|---|---|---|---|
| Liberty91 (first-party) | LIBERTY91_API_KEY (optional LIBERTY91_API_URL) | per-key rate limit + monthly credits on your plan | Liberty91 platform → user menu → API Access (Owner/Admin only; the secret is shown once) |
| VirusTotal | VIRUSTOTAL_API_KEY | 4/min, 500/day | virustotal.com → profile → API key |
| URLScan.io | URLSCAN_API_KEY | 100 scans/day | urlscan.io → user settings |
| Shodan | SHODAN_API_KEY | 1 req/sec | account.shodan.io |
| AbuseIPDB | ABUSEIPDB_API_KEY | 1000 checks/day | abuseipdb.com → account → API |
| GreyNoise | GREYNOISE_API_KEY | 50 req/day (community) | viz.greynoise.io → account |
| AlienVault OTX | OTX_API_KEY | 10k req/hour | otx.alienvault.com → settings |
| Censys | CENSYS_PAT | 250 queries/month | accounts.censys.io → settings → personal-access-tokens |
| MISP | MISP_URL + MISP_API_KEY | self-hosted / org-provided | your MISP instance → My Profile → Auth keys |
| OpenCTI | OPENCTI_URL + OPENCTI_TOKEN | self-hosted / org-provided | your OpenCTI instance → profile → API access (token) |
| Ransomware.live | RANSOMWARE_LIVE | 3000 req/day (PRO) | my.ransomware.live → free PRO key |
| ReversingLabs A1000 | REVERSINGLABS_USER + REVERSINGLABS_PASSWORD (optional REVERSINGLABS_HOST) | undocumented; 429+Retry-After | licensed product — issued by your RL admin or RL account team |
| CrowdStrike Falcon Intelligence | CROWDSTRIKE_CLIENT_ID + CROWDSTRIKE_CLIENT_SECRET (optional CROWDSTRIKE_BASE_URL) | per-tenant; 429+Retry-After | licensed product — Falcon console → Support and resources → API clients and keys (assign Intel read scopes) |
| Microsoft Sentinel | SENTINEL_TENANT_ID + SENTINEL_CLIENT_ID + SENTINEL_CLIENT_SECRET + SENTINEL_WORKSPACE_ID | your Azure tenancy (query API is free; 200 queries/30s) | Azure portal — Entra ID app registration + Log Analytics Reader role; walkthrough in tools/integrations/sentinel.md |
If the user has a Liberty91 account, configure LIBERTY91_API_KEY first — it is the pack's first-party source and /lookup-liberty91 runs before third-party lookups, so it saves other services' quota. Keys are l91_live_ (production) or l91_test_ (development); an empty scope list on the key grants all read scopes, which is the right default for enrichment. Set LIBERTY91_API_URL only to point at a non-production host.
A starter set of VirusTotal + OTX + URLScan + AbuseIPDB covers most IP/domain/URL/hash investigations. Shodan and GreyNoise add value for IP-focused work. Censys is optional (very tight rate limit). MISP requires both a base URL and an auth key — point it at your org's instance. OpenCTI likewise takes a base URL plus an API token and powers /lookup-opencti (two-way: query your knowledge base + push vetted intel back). Ransomware.live powers the lookup-ransomwarelive and ransomware-ecosystem skills (victim/group tracking). ReversingLabs is a licensed product — only configure if your organisation has a Spectra Analyze (A1000) account. CrowdStrike Falcon Intelligence is a licensed subscription — it powers /lookup-crowdstrike for IOC reputation AND threat-actor / TTP / report intelligence; configure if your org has a Falcon Intelligence licence with Intel API scopes. Microsoft Sentinel takes four values and powers /lookup-sentinel (hunt your own workspace: IOC exposure sweeps + ATT&CK TTP hunts, read-only). All four come from the Azure portal: create an Entra ID app registration (→ tenant id + client id), add a client secret (shown once), grant the app Log Analytics Reader on the Sentinel workspace, and copy the Workspace ID from the workspace Overview blade — the step-by-step is in tools/integrations/sentinel.md. No extra licence is needed beyond the workspace itself.
How to write the file
The file is .claude/settings.local.json. It is gitignored. Do not overwrite it — read