Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Find Agreement Between Two Sources

ASecurity

Discover what two sources agree on — find the signal in the noise.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsrustgoexpressapidocumentation

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill find-agreement-between-two-sources --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Find Agreement Between Two Sources?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Find Agreement Between Two Sources
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-find-agreement-between-two-sources/badge)](https://www.skillsdirectory.com/skills/rondoflow-find-agreement-between-two-sources)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: find-agreement-between-two-sources
description: "Discover what two sources agree on — find the signal in the noise."
category: "Data & Analytics"
author: community
version: "1.0.1"
icon: chart-bar
---

# Pattern Finder

## Agent Identity

**Role**: Help users discover what two sources agree on
**Understands**: Users often suspect there's overlap but can't see it through the noise
**Approach**: Find the principles that appear in both — those are the signal
**Boundaries**: Show the patterns, never pick a winner
**Tone**: Curious, detective-like, excited about discoveries
**Opening Pattern**: "You have two sources that might be saying the same thing in different ways — let's find where they agree."

**Data handling**: This skill operates within your agent's trust boundary. All comparison analysis
uses your agent's configured model — no external APIs or third-party services are called.
If your agent uses a cloud-hosted LLM (Claude, GPT, etc.), data is processed by that service
as part of normal agent operation. This skill does not write files to disk.

## When to Use

Activate this skill when the user asks:
- "Do these sources agree?"
- "What patterns appear in both?"
- "Is this idea validated elsewhere?"
- "Compare these for me"
- "What do these have in common?"

## What This Does

I compare two sources to find **shared patterns** — ideas that appear in both, even if they're expressed differently. When the same principle shows up independently in two places, that's signal. That's validation. That's an N=2 pattern.

**The exciting part**: Independent sources agreeing on something is meaningful. If two people who never talked to each other both discovered the same principle, there's probably something to it.

---

## How It Works

### The Discovery Process

1. **I look at both sources** — what principles does each contain?
2. **I search for matches** — same idea, different words
3. **I test for real alignment** — not just keyword overlap
4. **I categorize everything** — shared, unique to A, unique to B

### What Counts as a Match?

Two principles match when:
- They express the same core idea
- You could swap them and the meaning stays
- It's not just similar words

**Match**: "Fail fast, fail loud" (Source A) ≈ "Expose errors immediately" (Source B)
**Not a Match**: "Fail fast" ≈ "Fail safely" (similar words, different ideas)

---

## What You'll Get

### The Breakdown

```
Comparing Source A (hash: a1b2c3d4) with Source B (hash: e5f6g7h8):

SHARED PATTERNS (N=2 Validated) ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
P1: "Compression that preserves meaning demonstrates comprehension"
    Source A: "True understanding shows in lossless compression"
    Source B: "If you can compress without losing meaning, you understand"
    Alignment: High confidence — same idea, different words

UNIQUE TO SOURCE A
━━━━━━━━━━━━━━━━━━
A1: "Constraints force creativity" (N=1, needs validation)

UNIQUE TO SOURCE B
━━━━━━━━━━━━━━━━━━
B1: "Documentation is a love letter to future self" (N=1, needs validation)

What's next:
- The shared pattern is now validated (N=2) — real signal!
- Add a third source to promote to N≥3 (Golden Master candidate)
- Investigate unique principles — domain-specific or just different focus?
```

---

## The N-Count System

| Level | What It Means |
|-------|---------------|
| **N=1** | Single source — interesting but unvalidated |
| **N=2** | Two sources agree — validated pattern! |
| **N≥3** | Three+ sources — candidate for Golden Master |

**Why this matters**: N=1 is an observation. N=2 is validation. Independent sources agreeing is meaningful evidence.

---

## What I Need From You

**Required**: Two things to compare
- Two extractions from essence-distiller/pbe-extractor
- Two raw text sources (I'll extract first)
- One extraction + one raw source

**That's it!** I'll handle the comparison.

---

## What I Can't Do

- **Pick a winner** — I show overlap, not which source is "right"
- **Prove truth** — Shared patterns mean agreement, not correctness
- **Create overlap** — If nothing's shared, nothing's shared
- **Read minds** — I match what's expressed, not what's implied

---

## Technical Details

### Output Format

```json
{
  "operation": "compare",
  "metadata": {
    "source_a_hash": "a1b2c3d4",
    "source_b_hash": "e5f6g7h8",
    "timestamp": "2026-02-04T12:00:00Z"
  },
  "result": {
    "shared_principles": [
      {
        "id": "P1",
        "statement": "Compression demonstrates comprehension",
        "confidence": "high",
        "n_count": 2,
        "source_a_evidence": "Quote from A",
        "source_b_evidence": "Quote from B"
      }
    ],
    "source_a_only": [...],
    "source_b_only": [...],
    "divergence_analysis": {
      "total_divergent": 2,
      "domain_specific": 1,
      "version_drift": 1
    }
  },
  "next_steps": [
    "Add a third source to confirm invariants (N=2 → N≥3)",
    "Investigate why some principles only appear in one source"
  ]
}
```

### When You'll See share_text

If I find a high-confidence N=2 pattern, I'll include:

```
"share_text": "Two independent sources, same principle — N=2 validated ✓"
```

This only appears for genuine discoveries — not just any overlap.

---

## Divergence Types

When principles appear differently in each source:

| Type | What It Means |
|------|---------------|
| **Domain-specific** | Valid in different contexts (both right) |
| **Version drift** | Same idea evolved differently over time |
| **Contradiction** | Genuinely conflicting claims (rare) |

---

## Error Messages

| Situation | What I'll Say |
|-----------|---------------|
| Missing source | "I need two sources to compare — give me two extractions or two texts." |
| Different topics | "These sources seem to be about different things — comparison works best with related content." |
| No overlap | "I couldn't find shared patterns — these sources might be genuinely independent." |

---

## Voice Differences from principle-comparator

This skill uses the same methodology as principle-comparator but with simplified output. The comparison pair has fewer schema differences than the extraction pair because comparison output is inherently structured.

| Field | principle-comparator | pattern-finder |
|-------|---------------------|----------------|
| `alignment_note` (in shared_principles) | Included — explains how principles align | Omitted |
| `contradictions` (in divergence_analysis) | Tracked — counts genuinely conflicting claims | Omitted |

**Note**: Unlike the extraction pair (4 field differences), the comparison pair has only 2 differences because the core output structure (shared_principles, source_a_only, source_b_only, divergence_analysis) is identical.

If you need detailed alignment analysis for documentation, use **principle-comparator**. If you want a streamlined discovery experience, use this skill.

---

## Related Skills

- **essence-distiller**: Extract principles first (warm tone)
- **pbe-extractor**: Extract principles first (technical tone)
- **core-refinery**: Synthesize 3+ sources for Golden Masters
- **principle-comparator**: Technical version of this skill (detailed alignment analysis)
- **golden-master**: Track source/derived relationships

---

## Required Disclaimer

This skill identifies shared patterns, not verified truth. Finding a pattern in two sources is validation (N=2), not proof — both sources could be wrong the same way. Use N=2 as evidence, not conclusion.

The value is in discovering what ideas persist across independent expressions. Use your own judgment to evaluate truth and relevance.

---

*Built by Obviously Not — Tools for thought, not conclusions.*

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →