apify-public-registries
Look up official company data from European public registries across 11 countries/regions (CZ, SK, PL, DE, UK, NL, RO, HR, SE + EU-level + ESG). Covers company registration, ownership, financial filings, VAT status, ESG data. Use when the user asks to "look up a company", "check registry", "find company info", "look up IČO/KRS/LEI/CRN", "company due diligence", "check VAT status", "find ownership structure", or needs official data from European registries. Reads tracked companies from data/companies.json. Some lookups use Python scripts (stdlib), some fall back to Apify actors for scraping-based registries.
What this skill does
# Public Company Registries — 11 Countries Look up official company data from European public registries via Python scripts (direct REST API) or Apify actor fallback (scraping when no API exists). ## Prerequisites - Python 3 (scripts use stdlib — no pip dependencies for most countries) - Apify access (only for DE, UK, PL financials, CZ justice.cz, RO fallback) — preferred: `apify` CLI (`npm install -g apify-cli && apify login`); fallback: Apify MCP connector (`call-actor` tool). CLI is faster and preferred when both are available. - **NL**: `KVK_API_KEY` env var (register at developers.kvk.nl — see [REGISTRATION/NL.md](REGISTRATION/NL.md)) - **PL GUS**: `GUS_API_KEY` env var (email [email protected]) - **SE**: Bolagsverket requires registration (see [REGISTRATION/SE.md](REGISTRATION/SE.md)) - **HR**: Sudski registar requires OAuth registration (see [REGISTRATION/HR.md](REGISTRATION/HR.md)) `${CLAUDE_PLUGIN_ROOT}` is the plugin's root directory (where `.claude-plugin/` lives). It is resolved automatically by Claude Code when the plugin is installed, or set to the `--plugin-dir` path during development. ## Workflow checklist Copy this and tick boxes as you progress: ``` Task Progress: - [ ] Step 0: Verify prerequisites — run `python3 --version` (required); for Apify-dependent registries: try `apify --version && apify info`, or check for `call-actor` MCP tool; if neither, tell user to install apify CLI or Apify MCP connector - [ ] Step 1: Identify country + identifier type (IČO/KRS/CUI/LEI/company name) - [ ] Step 2: Run the lookup command per country table - [ ] Step 3: Interpret results (key fields vary by source) - [ ] Optional: Apify fallback for scraping-based registries - [ ] Optional: Cross-reference with EU-level sources (GLEIF LEI, ESMA bonds, EBA) ``` ## Quick Reference — Lookup by Country All paths relative to `${CLAUDE_PLUGIN_ROOT}/skills/apify-public-registries/`. | Country | Command | Identifier | Access | |---|---|---|---| | **CZ** | `python3 reference/scripts/CZ/fetch_all.py lookup <IČO>` | IČO (8-digit) | Free (ARES API) | | **SK** | `python3 reference/scripts/SK/fetch_all.py lookup <IČO>` | IČO | Free (ORSR scraping) | | **PL** | `python3 reference/scripts/PL/fetch_all.py lookup <KRS>` | KRS (10-digit, zero-padded) | Free (KRS API) | | **PL** | `python3 reference/scripts/PL/fetch_all.py lookup_nip <NIP>` | NIP (10-digit) | Free (Biała Lista, 100/day) | | **PL GUS** | (included in batch `fetch_all.py`) | NIP | **`GUS_API_KEY` REQUIRED** — without it, returns fake test data silently (see gotchas) | | **DE** | `python3 reference/scripts/DE/fetch_all.py keyword <name>` | Company name | Apify (mcpc CLI) | | **UK** | `python3 reference/scripts/UK/fetch_all.py search <name>` | Company name | Apify (mcpc CLI) | | **NL** | `python3 reference/scripts/NL/fetch_all.py` | KVK number (configured) | API key (`KVK_API_KEY`) | | **RO** | `python3 reference/scripts/RO/fetch_all.py lookup <CUI>` | CUI number | Free (ANAF — offline since 2026-03) | | **HR** | Manual — see [REGISTRATION/HR.md](REGISTRATION/HR.md) | OIB / MBS | OAuth registration | | **SE** | Manual — see [REGISTRATION/SE.md](REGISTRATION/SE.md) | Org.nr | Bolagsverket registration | | **EU** | `python3 reference/scripts/EU/fetch_all.py lookup <name>` | Company name | Free (GLEIF + ESMA + TED) | | **EU** | `python3 reference/scripts/EU/fetch_all.py lookup_lei <LEI>` | LEI (20-char) | Free (GLEIF) | | **ESG** | `python3 reference/scripts/ESG/fetch_all.py lookup <country>` | Country name/ISO code | Free | ## By Data Type | Need | Best source | Command | |---|---|---| | Basic profile (name, address, legal form) | CZ: ARES, SK: ORSR, PL: KRS, DE: Handelsregister, UK: Companies House | See country table above | | Ownership / corporate tree | EU GLEIF | `EU/fetch_all.py lookup_lei <LEI>` | | Financial filings (CZ) | Justice.cz sbírka listin (Apify fallback) | `CZ/fetch_all.py justice` | | Financial filings (SK) | FinStat.sk | `SK/fetch_all.py finstat` | | Financial filings (PL) | eKRS via Apify | `PL/fetch_all.py financials` | | Bonds & instruments | ESMA FIRDS | `EU/fetch_all.py lookup <name>` | | VAT / due diligence (CZ) | DPH register | Included in `CZ/fetch_all.py lookup` | | VAT / due diligence (PL) | Biała Lista | `PL/fetch_all.py lookup_nip <NIP>` | | Bank regulatory data | EBA Transparency CSVs (100MB+) | `EU/fetch_all.py eba` | | ESG / emissions | Climate TRACE + EU ETS | `ESG/fetch_all.py lookup <country>` | | Regulated entities (CZ) | ČNB bank list + OAM | `CZ/fetch_all.py cnb_banks` / `cnb_oam` | | Public procurement | TED | `EU/fetch_all.py lookup <name>` | ## Step 1: Identify country + identifier - Check `${CLAUDE_PLUGIN_ROOT}/data/companies.json` -> `identifiers.registry_ids` for existing IDs. - If identifier unknown, start with **EU GLEIF by name** — returns LEI + registered-as numbers usable in country-specific lookups. **Identifier types by country:** - **CZ/SK**: IČO (8-digit) - **PL**: KRS (10-digit zero-padded) or NIP (10-digit) - **DE**: Company name keyword - **UK**: Company name - **NL**: KVK number (8-digit) - **RO**: CUI (numeric) - **HR**: OIB (11-digit) or MBS - **SE**: Organisationsnummer (10-digit, e.g. 559124-6847) - **EU**: LEI (20-char alphanumeric) or company name ## Step 2: Run lookup Execute the command from the country table. Scripts are at: `${CLAUDE_PLUGIN_ROOT}/skills/apify-public-registries/reference/scripts/<CC>/fetch_all.py` **Example — look up a company in Czech ARES:** ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/apify-public-registries/reference/scripts/CZ/fetch_all.py lookup 25099345 ``` **Example — find ownership chain via GLEIF:** ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/apify-public-registries/reference/scripts/EU/fetch_all.py lookup_lei 31570048XH84U51GGT05 ``` **Example — look up InPost in KRS:** ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/apify-public-registries/reference/scripts/PL/fetch_all.py lookup 0000536554 ``` **Batch fetch (all companies in a country):** ```bash python3 reference/scripts/CZ/fetch_all.py # all CZ sources (ares, dph, cnb_banks, cnb_oam, justice) python3 reference/scripts/PL/fetch_all.py # all PL sources (krs, biala_lista, gus, financials) python3 reference/scripts/EU/fetch_all.py # all EU sources except EBA (gleif, ted, esma, eurostat) ``` ## Step 3: Interpret results Key fields vary by source: | Source | Key fields | |---|---| | **ARES** (CZ) | obchodniJmeno, dic, sidlo.textovaAdresa, czNace, datumVzniku, pravniForma | | **DPH** (CZ) | nespolehlivyPlatce (unreliable payer flag), bank accounts | | **GLEIF** (EU) | lei, legalName, jurisdiction, status, registeredAs, parent LEI + name | | **KRS** (PL) | nazwa, nip, regon, kapital (share capital) | | **Biała Lista** (PL) | statusVat, krs, regon, accountNumbers | | **ORSR** (SK) | name, address, legal_form, share_capital, registration_date | | **FinStat** (SK) | revenue, profit, employees, assets | | **Handelsregister** (DE) | name, legal form, share capital, management, HRB number | | **Companies House** (UK) | company number, SIC codes, directors, incorporation date | | **ESMA FIRDS** (EU) | isin, lei, instrument name, cfi_code, status | | **TED** (EU) | buyer-name, winner-name, total-value, procedure-type | | **ANAF** (RO) | denumire, adresa, scpTVA (VAT payer flag), active status | ## Apify fallback When no direct API exists, use Apify CLI with a specific actor or `apify/website-content-crawler`: ```bash apify call apify/website-content-crawler \ --input '{"startUrls":[{"url":"https://or.justice.cz/ias/ui/rejstrik-$firma?ico=25099345"}],"maxCrawlPages":1}' \ --user-agent apify-awesome-skills/apify-public-registries ``` **Apify-dependent registries:** | Country | Registry | Actor | Trigger | |---|---|---|---| | DE | Handelsregister | `radeance/handelsregister-api` | `DE/fetch_all.py keyword <name>` | | UK | Companies House | `dhrumil/company-house-scraper` | `UK/fetch_all.py search <name>` | | PL | eKR
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.