Meeting Contradiction Detector

    1

    Detect conflicts between meeting notes and chat logs to stop scope creep and "invisible" decision changes.

    $9

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Meeting Contradiction Detector

    Example session with this skill installed

    Compare these meeting notes: 'Agreed on PostgreSQL for the database, Sarah to lead' with this Slack log: 'Sarah: Actually let's use MongoDB, it's faster for this. Dave: Sounds good.'

    • Read your context and instructions
    • Compiled the meeting contradiction detector
    • Generated the document

    Analyzed 1 meeting transcript and 1 chat log. Found 2 discrepancies regarding database architecture and formal decision-making.

    [Contradiction Analysis Report]

    ✅ Aligned Items:

    • Sarah remains the lead for the database implementation.

    ⚠️ Contradictions & Drift Detected:
    1.

    Direct Contradiction: The team switched from a relational to a non-relational database without updating formal project documentation.

    • Receipts: Source A ("Agreed on PostgreSQL for the database") vs. Source B ("Sarah: Actually let's use MongoDB... Dave: Sounds good.")
    • Suggested Resolution: Ask the team: "Are we officially pivoting to MongoDB as suggested in Slack, or should we stick to the PostgreSQL decision from the formal meeting?"
    1. Decision Authority Drift: A architectural change was made via a casual chat message rather than a formal review.
      • Receipts: Source A ("Agreed on...") vs. Source B ("Sounds good.")
      • Suggested Resolution: Ask Dave: "Does your 'sounds good' in Slack constitute a formal approval of the architecture change, or do we need a quick sync?"

    📋 Final Action Item Summary:

    • Sarah to confirm database selection (PostgreSQL vs MongoDB) by EOD.
    • Update the system architecture diagram once the database type is finalized.

    Next steps

    • Post the suggested resolution questions in the project Slack channel.
    • Update the ARCHITECTURE.md file once the team confirms the choice.
    • Attach this report to the Jira ticket to document the pivot.

    meeting-contradiction-detector.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Flag conflicting tech stack decisions between meetings and chat.Detect silent task reassignments and owner drift.Identify scope creep by comparing notes against original briefs.Generate quote-backed receipts to resolve team miscommunications.

    About this skill

    The problem

    Teams suffer from verbal amnesia and "invisible" scope creep. Decisions made in meetings often drift in Slack threads or get silently reassigned, leading to wasted dev hours and finger-pointing during sprint reviews.

    What it does

    • Extracts core commitments, decisions, and action items from transcripts and chat logs.
    • Cross-references multiple sources to flag direct contradictions in tech stack or architecture choices.
    • Identifies silent owner changes where tasks migrate between team members without formal handoffs.
    • Detects timeline drift and unauthorized scope additions by comparing current notes against project briefs.
    • Generates "receipts" using direct quotes to provide undeniable evidence of discrepancies.

    Why this beats prompting it yourself

    General LLMs often try to "harmonize" conflicting information or pick one source as correct by default. This skill is hardcoded to be adversarial, specifically hunting for friction and providing the exact quotes needed to resolve the dispute without manual scrolling.

    Use cases

    • Reviewing Monday's meeting transcript against Wednesday's Slack "recap" to find drift.
    • Auditing a project brief against the latest sprint planning notes for scope creep.
    • Resolving "who said what" disputes by extracting timestamped evidence from multiple documents.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 20 days ago

    • Passed all security checks, Safe to install

    Listed20 days ago

    What's inside

    Frequently Asked Questions