OpenParable
Skip to content
← Back to skills

Update Entities

Development
update-entities

Update Entities is an Agent Skill for development published in the duckduckgo/tracker-radar repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

How to add or remove domains from an entity (company/organization) in Tracker Radar. Use when modifying domain-to-entity mappings.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/duckduckgo/tracker-radar/blob/HEAD/.cursor/skills/update-entities/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-entities, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

How to Update Entities

Prerequisites

  1. Clone the tracker-radar-detector repo alongside this one and run npm install.
  2. Update the tracker-radar-detector config.json so trackerRadarRepoPath points to your local clone of this repo (tracker-radar).

Steps

1. Edit build-data/generated/entity_map.json

Find the target entity and add the new domain to its properties array in alphabetical order.

2. Run npm run apply-entity-changes in the tracker-radar-detector repo

This propagates changes to all dependent files:

FileWhat changes
build-data/generated/entity_map.jsonThe source of truth you edited
build-data/generated/domain_map.jsonReverse mapping — one entry per domain with entityName, aliases, displayName
entities/<Entity Name>.jsonThe entity file gets the domain added to its properties array

3. Verify

  • entity_map.json — domain in the entity's properties, alphabetically sorted
  • domain_map.json — new key for the domain with correct entityName, aliases, displayName
  • entities/<Entity Name>.json — domain in properties, alphabetically sorted
  • All three files are valid JSON
  • Run npm test to validate schemas