say-ducklake-xor

Cross-reference thread 'say' occurrences with DuckDB sources using XOR-based uniqueness.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill say-ducklake-xor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: say-ducklake-xor
Source: https://github.com/plurigrid/asi/tree/main/skills/say-ducklake-xor
Command: npx skills add https://github.com/plurigrid/asi --skill say-ducklake-xor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates discovering uses of "say" or MCP tooling across threads and cross-references with DuckDB sources. It provides deterministic XOR-based uniqueness guarantees to avoid collisions during bounded parallel exploration.

Core Features & Use Cases

  • Deterministic parallel discovery: bounded, repeatable exploration with XOR-based uniqueness.
  • Cross-reference DuckLake sources: automatically correlates thread data with DuckDB sources for verification.
  • Integrity guarantees: enforces same seed yields same colors across runs (SPI) and GF(3) conservation checks.

Quick Start

Just run the discovery with a seed and bound: python scripts/say_ducklake_xor.py --seed 1069 --bound 27

Frequently Asked Questions about say-ducklake-xor

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

FAQPage Schema
How do I discover 'say' usage across threads and verify it against DuckDB sources?

This Skill scans threads for 'say' or 'say mcp' calls, cross-references them with DuckDB sources, and enforces XOR-based uniqueness to eliminate collisions. Run with a seed and concurrency bound to get deterministic, deduplicated discovery results ready for storage.

What guarantees does XOR-based uniqueness provide during parallel discovery?

XOR uniqueness prevents duplicate discoveries across bounded-parallel workloads. Combined with seed-based derivation, it ensures the same input seed produces identical results across runs, with GF(3) conservation validation confirming data integrity throughout the discovery chain.

Can I run deterministic parallel discovery across large thread datasets?

Yes. The Skill handles bounded-parallel exploration of large datasets by applying seed-based derivation and concurrency limits. Specify your bound parameter to control scan scope; results integrate into standard schemas for analysis and storage without collision risk.

How do I cross-reference thread data with DuckDB to avoid missed correlations?

The Skill automatically correlates 'say' occurrences in threads with DuckDB source timestamps and concepts. Cross-reference logging captures all matches, and integration-ready schemas output coherent discovery chains that preserve relationships between thread and database entries.

What's the difference between parallel discovery with and without XOR-based uniqueness?

Without XOR enforcement, parallel scans risk duplicate discoveries when exploring the same conceptual space. XOR-based uniqueness guarantees one canonical result per discovery, reducing noise and storage overhead while maintaining determinism across runs with identical seed values.

Do I need prior setup or data preparation before running discovery?

Prepare your DuckDB source with thread data indexed by timestamp and concept. Provide a seed value and concurrency bound to invoke the discovery script. No external dependencies are required; the Skill handles schema validation and GF(3) conservation checks automatically.