add-registry

Automate corporate registry addition with data discovery and ingester creation.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/tcole333/ithildin --skill add-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-registry
Source: https://github.com/tcole333/ithildin/tree/main/.claude/skills/add-registry
Command: npx skills add https://github.com/tcole333/ithildin --skill add-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, python, curl, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the issue of manually adding corporate registries to a unified system, automating the process and ensuring consistency in data management.

Core Features & Use Cases

  • Registry Addition: Automatically add new state or country corporate registries to the unified registry system.
  • Data Ingestion: Execute ingesters that feed registry data into the unified registry.db schema.
  • Use Case: When you need to incorporate a new jurisdiction's corporate registry into your data source, use this Skill to quickly set up the ingester without manual configuration.

Quick Start

Use the add-registry skill to add the Florida corporate registry by running the command /add-registry florida.

Frequently Asked Questions about add-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate corporate registry data ingestion into a unified schema?

Automating corporate registry data ingestion involves data discovery, endpoint probing, and ingester creation to feed registry data into a unified `registry.db` schema. This Skill automates those steps using Python scripts to process and map data.

What's the best way to add a new jurisdiction's corporate registry to my data source?

The best way to add a new jurisdiction's corporate registry is to use an automated ingester that handles API, FTP, or SFTP interaction. This ensures consistent data management without requiring manual configuration for each new state or country.

Do I need Python and curl to set up data ingestion for corporate registries?

Yes, you need Python, curl, and uv installed. These dependencies are required to run the Python scripts that execute endpoint probing and process the registry data into the unified schema.

Can I use API and SFTP endpoints for system integration with a unified registry system?

Yes, the system integration process supports API, FTP, and SFTP endpoint interaction. It probes these endpoints during data discovery to successfully feed corporate registry records into the unified schema.

How does endpoint probing work when adding a corporate registry?

Endpoint probing tests available API, FTP, or SFTP connections to discover accessible data sources. It determines the correct integration method before creating the Python ingester that maps and loads the registry data.

What are the limitations of automating corporate registry addition with Python scripts?

The main limitation is that the Python scripts require specific dependencies like uv and curl to function. Additionally, successful ingestion depends on the accessibility and structure of the external API, FTP, or SFTP endpoints being probed.