Scaffold a new sanctions list crawler from a source URL or GitHub issue
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opensanctions/opensanctions crawler-sanctions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/crawler-sanctions .claude/skills/crawler-sanctions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .claude/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opensanctions/opensanctions crawler-sanctions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/crawler-sanctions .agents/skills/crawler-sanctions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .agents/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opensanctions/opensanctions crawler-sanctions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/crawler-sanctions .cursor/skills/crawler-sanctions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .cursor/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/opensanctions/opensanctions.git --path .claude/skills/crawler-sanctions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opensanctions/opensanctions crawler-sanctions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/crawler-sanctions .gemini/skills/crawler-sanctions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .gemini/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install opensanctions/opensanctions crawler-sanctionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/crawler-sanctions .github/skills/crawler-sanctions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .github/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opensanctions/opensanctions --skill crawler-sanctions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opensanctions/opensanctions crawler-sanctions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opensanctions/opensanctions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/crawler-sanctions .opencode/skills/crawler-sanctions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "crawler-sanctions" agent skill from https://github.com/opensanctions/opensanctions/tree/main/.claude/skills/crawler-sanctions into .opencode/skills/crawler-sanctions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crawler-sanctions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
crawler-sanctionsScaffold a new sanctions list crawler from a source URL or GitHub issue
Crawler Sanctions is an agent skill from opensanctions/opensanctions. Scaffold a new sanctions list crawler from a source URL or GitHub issue
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `examples.md`).
It sits in Data & Analytics, covering Web scraping. It works with GitHub. The repository describes itself as: An open database of international sanctions data, persons of interest and politically exposed persons. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ce59ef9. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadEditWriteGlobGrepBashWebFetchWebSearchAgentFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python, yaml and bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Crawler Sanctions loads about 1.9k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 538 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, AgentAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from opensanctions/opensanctions at commit ce59ef9, republished under its MIT licence (© opensanctions). 538 words, ~1,937 tokens.
.claude/skills/crawler-sanctions/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Create a new sanctions list crawler. The user will provide a target path, source data URL, and/or a GitHub issue URL: $ARGUMENTS
If given a GitHub issue URL, fetch it first to extract the data source URL and any context about the dataset before proceeding.
Before writing any code, read these files — they contain everything you need:
.claude/docs/crawler-guide.md — shared crawler patterns (YAML template, fetching data, entity creation, helpers, lookups, FTM schemata, qsv analysis).claude/skills/crawler-sanctions/examples.md — full sanctions code examplesDo NOT search the repository for similar crawlers or patterns. The guide and examples
above are the authoritative reference. Do not read datasets/CLAUDE.md or other crawler
source files for patterns — use only the files listed above.
Before writing any code, inspect the data source. In addition to the general checks (fields, date formats, language, record count), sanctions sources need:
Use the generic YAML template from the crawler guide. Sanctions-specific additions:
tags:
- list.sanction
- issuer.west # optional
assertions:
min:
schema_entities:
Person: 1000 # band widths: see "Data assertions" in zavod/docs/metadata.md
Organization: 200
Sanction: 1000
country_entities:
cc: 100
max:
schema_entities:
Person: 5000
Organization: 1000coverage.frequency: daily (house default for sanctions — see zavod/docs/metadata.md). Don't add a cron schedule: unless the run must follow the source's own publication time.The most important sanctions lookup maps source program names to OpenSanctions keys:
lookups:
# Entity type dispatch (when source uses custom type labels)
type.entity:
lowercase: true
options:
- match: [individual, person]
value: Person
- match: [entity, company, organization]
value: Organization
- match: [vessel, ship]
value: Vessel
# Map source program names to OpenSanctions program keys
sanction.program:
options:
- match: "Executive Order 13224"
value: US-EO13224
# Date edge cases common in sanctions data
type.date:
options:
- match: "1972-08-10 or 1972-08-11"
values: ["1972-08-10", "1972-08-11"]
- match: "1975-19-25" # typo
value: "1975"type.* lookups are applied automatically by entity.add(). The sanction.program
lookup must be called explicitly via h.lookup_sanction_program_key().
Full reference: zavod/docs/programs.md
h.make_sanction() automatically sets country, authority, and sourceUrl from
dataset metadata. The key parameters:
sanction = h.make_sanction(
context,
entity, # the sanctioned entity (required)
key=entry_id, # disambiguator when entity has multiple sanctions
program_name=program, # human-readable program name
source_program_key=program, # raw value from source (preserved as original_value)
program_key=h.lookup_sanction_program_key( # OpenSanctions program key from yaml lookup
context, program
),
start_date=listing_date, # optional: when sanction began
end_date=end_date, # optional: when sanction ended
)key: Use when an entity appears on multiple sanctions lists/programs. The sanction
ID is make_id("Sanction", entity.id, key), so key disambiguates multiple sanctions
per entity.program_key: Always go through h.lookup_sanction_program_key() which reads the
sanction.program yaml lookup. Add entries to the lookup as you encounter new program
names.source_program_key: The raw program string from the source, preserved as
original_value on the programId property for auditability.entity.add("topics", "sanction") on the sanctioned entity.For simple datasets with a single known program, you can skip the lookup:
sanction = h.make_sanction(context, entity, program_key="US-DOS-CU-PAL")if h.is_active(sanction):
entity.add("topics", "sanction")
# Only mark as sanctioned if the sanction is currently activeFull reference: zavod/docs/extract/names.md
Sanctioned names are legal designations — do not use LLM-based name cleaning. Any normalisation must be human-reviewed via the stateful review system, or handled with explicit lookup entries.
See the crawler guide for the generic Family and Ownership patterns. See examples.md for UnknownLink (sanctions-specific untyped relationships).
When the source tracks modifications and de-listings, use sanction.add("endDate", ...)
for de-listings and sanction.add("modifiedAt", ...) for amendments. See
examples.md for the full pattern.
Full reference: zavod/docs/data_reviews.md
For sources with unstructured "remarks" fields, use GPT extraction with the stateful
review system. Requires ci_test: false. See examples.md for the pattern.
After running zavod crawl, use these sanctions-specific qsv checks (see the crawler
guide for general qsv patterns):
# Entity counts by schema
qsv search -s prop "^Person:id$" data/datasets/cc_dataset/statements.pack | qsv count
qsv search -s prop "^Organization:id$" data/datasets/cc_dataset/statements.pack | qsv count
qsv search -s prop "^Sanction:id$" data/datasets/cc_dataset/statements.pack | qsv count
# Sanction program distribution
qsv search -s prop "^Sanction:program$" data/datasets/cc_dataset/statements.pack | qsv frequency -s value
# Every Sanction:entity must point to a real entity
qsv search -s prop "^Sanction:entity$" data/datasets/cc_dataset/statements.pack | qsv select value | qsv behead | sort > /tmp/sanction_targets.txt && qsv search -s prop ":id$" data/datasets/cc_dataset/statements.pack | qsv select entity_id | qsv behead | sort -u > /tmp/all_entities.txt && comm -23 /tmp/sanction_targets.txt /tmp/all_entities.txt
# Check all entities have topics=sanction
qsv search -s prop ":id$" data/datasets/cc_dataset/statements.pack | qsv select entity_id | qsv behead | sort -u > /tmp/all_ids.txt && qsv search -s prop ":topics$" data/datasets/cc_dataset/statements.pack | qsv search -s value "^sanction$" | qsv select entity_id | qsv behead | sort -u > /tmp/sanctioned.txt && comm -23 /tmp/all_ids.txt /tmp/sanctioned.txtThen run zavod export datasets/cc/dataset/cc_dataset.yml, which checks the dataset
validators and assertions.
© opensanctions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .claude/skills/crawler-sanctions of opensanctions/opensanctions.
Open the folder on GitHubat commit ce59ef9
Crawler Sanctions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Crawler Sanctions this skillopensanctions/opensanctions | 832 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Multi Account Scrapingantibrow/anti-detect-browser-skills | 932 | — | ~3.7k | Automated safety check: Warn | MIT | |
| Octocode Scrapingbgauryy/octocode | 949 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Dev Pain Findertinyfish-io/tinyfish-cookbook | 2.2k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Deepapidavidondrej/skills | 4.1k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Performing Paste Site Monitoring For Credentialsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.7k | Automated safety check: Warn | Apache-2.0 |
antibrow/anti-detect-browser-skills
Run the same scrape or task across many accounts at once - each in its own browser profile with its own fingerprint, cookies and exit IP - and read data from sites that need a session or that answer…
bgauryy/octocode
A skill your agent uses when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages…
tinyfish-io/tinyfish-cookbook
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them…
davidondrej/skills
Use DeepAPI for all web search, deep research, and web scraping (websites, LinkedIn, GitHub, X/Twitter, YouTube, Instagram) instead of built-in search, research, fetch, or browser tools.
mukul975/Anthropic-Cybersecurity-Skills
Monitor paste sites like Pastebin and GitHub Gists for leaked credentials, API keys, and sensitive data dumps using automated scraping and keyword matching to detect breaches early.
hoodini/ai-agents-skills
Fetch and display GitHub trending repositories and developers.
opensanctions/opensanctions
Scaffold a new PEP (Politically Exposed Persons) crawler — members of a parliament, legislature, senate, chamber of deputies, cabinet, judiciary, or an asset-declaration register — from a source URL…
opensanctions/opensanctions
Move hardcoded lookup/config constants (gender maps, header dicts, value translations, column-label maps, date formats) out of a crawler and into the dataset .yml — as datapatch lookups wherever…
opensanctions/opensanctions
Bring a dataset .yml's metadata in line with house conventions (title, summary, description, coverage, publisher, maintainer comments).
opensanctions/opensanctions
Refactor the title, description and coverage frequency of a legislature/parliament PEP dataset .yml into the house style.
opensanctions/opensanctions
Migrate ad-hoc name cleaning in a crawler to h.reviewnames (Step 1 of the name framework migration).
opensanctions/opensanctions
Rewrite messy or AI-generated crawler code into clean, production-ready style that follows the zavod best practices.
Works with
Categories
Scaffold a new sanctions list crawler from a source URL or GitHub issue. Crawler Sanctions is an agent skill from opensanctions/opensanctions.
Crawler Sanctions fits situations like: tasks that involve Web scraping.
Run `npx skills add opensanctions/opensanctions --skill crawler-sanctions -a claude-code`. Or copy the skill folder (.claude/skills/crawler-sanctions in opensanctions/opensanctions) into .claude/skills/crawler-sanctions in your project. Claude Code loads it when a task matches its description.
Run `npx skills add opensanctions/opensanctions --skill crawler-sanctions -a codex`. Or copy the skill folder (.claude/skills/crawler-sanctions in opensanctions/opensanctions) into .agents/skills/crawler-sanctions in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opensanctions/opensanctions --skill crawler-sanctions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crawler-sanctions, .gemini/skills/crawler-sanctions, .github/skills/crawler-sanctions and .opencode/skills/crawler-sanctions in your project.
SKILL.md names no scripts, command-line tools or credentials: Crawler Sanctions is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Agent.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Crawler Sanctions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Crawler Sanctions: Multi Account Scraping (antibrow/anti-detect-browser-skills, 932 stars), Octocode Scraping (bgauryy/octocode, 949 stars), Dev Pain Finder (tinyfish-io/tinyfish-cookbook, 2.2k stars) and Deepapi (davidondrej/skills, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
opensanctions (a GitHub organization) maintains it in opensanctions/opensanctions, which has 832 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.
Source: opensanctions/opensanctions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
