linked-lookups

Coordinate bidirectional linked lookups across forms during submissions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jacobrocks1212/claude-config --skill linked-lookups
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linked-lookups
Source: https://github.com/jacobrocks1212/claude-config/tree/main/repos/cognito-forms/.claude/skills/linked-lookups
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill linked-lookups

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linked Lookups maintain bidirectional relationships between lookup fields across forms, ensuring updates propagate in real time and preserve referential integrity during submissions that cascade through defaults and auto-create entries.

Core Features & Use Cases

  • Bidirectional synchronization across forms ensures that when a submitting entry references a target entry, the corresponding lookup on the target entry is updated to include the source.
  • Synchronous processing with cascading updates and strict limits prevents runaway updates, supporting per-entry (1,000) and process-wide (10,000) operation caps, plus a 100-entry per-field limit with FIFO overflow.
  • Tight integration with Auto-Create Entries allows cascading updates to occur within the same submission flow, affecting newly created entries as part of the same transaction.
  • Supports multiple linked lookups per form and a centralized context (LinkedLookupSyncContext) to coordinate updates and batched persistence.

Quick Start

Configure a form with linked lookups, submit an entry referencing another entry, and observe bidirectional updates across both forms.

Frequently Asked Questions about linked-lookups

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

FAQPage Schema
How do I keep linked lookups perfectly in sync across forms during data entry?

Yes, cascading updates integrate tightly with auto-create entries, allowing newly created entries to receive linked lookup updates within the same synchronous submission transaction.

What are the operation limits for bidirectional form synchronization?

Bidirectional synchronization enforces strict limits: 1,000 operations per entry, 10,000 process-wide operations, and a 100-entry cap per field with FIFO overflow handling to prevent runaway updates.

How does synchronous processing handle multiple linked lookups on a single form?

A centralized LinkedLookupSyncContext coordinates multiple linked lookups on a single form, batching persistence and managing synchronous updates to maintain referential integrity across all fields.

When do I need bidirectional synchronization for lookup fields?

You need bidirectional synchronization when a submission on one form must update related entries on another form, preserving referential integrity as updates cascade through defaults and auto-create entries.

Can I use cascading updates with auto-create entries in the same submission?

Yes, cascading updates integrate tightly with auto-create entries, allowing newly created entries to receive linked lookup updates within the same synchronous submission transaction.