delta-minimizer

Identify one wallet discrepancy on Polymarket with DB rows and Loki logs.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill delta-minimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delta-minimizer
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/delta-minimizer
Command: npx skills add https://github.com/cogni-dao/cogni --skill delta-minimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate ONE specific discrepancy between our wallet's position and a copy-trade target's position on Polymarket. The skill's goal is to identify a single bug, prove it with cited evidence, and stop, avoiding over-scoping or multiple findings.

Core Features & Use Cases

  • One-discrepancy focus: zero in on a single divergence between our position and the target's, ensuring verifiable proof.
  • Evidence-driven analysis: extract exact decisions, fills, and Loki log lines from Postgres and Loki to ground conclusions.
  • Actionable reporting: deliver a concise bug report with precise DB rows and log evidence, then halt.
  • Guardrails: follows strict data-sourcing rules and cites canonical error codes and read-model references when applicable.

Quick Start

Use this skill to identify a single discrepancy and prove it with cited evidence, then stop.

Frequently Asked Questions about delta-minimizer

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

FAQPage Schema
How do I investigate a position discrepancy between my wallet and a Polymarket copy-trade target?

To investigate a copy-trade position discrepancy, identify a single divergence between your wallet and the target on Polymarket, prove it with cited Postgres DB rows and Loki log lines, then stop after one verified bug to avoid over-scoping.

How do I prove a copy-trade missed fill or wrong side bug with evidence?

You prove a copy-trade bug by extracting exact decisions, fills, and Loki log lines from Postgres and Loki to ground conclusions, delivering a concise bug report with precise DB rows and log evidence that references the relevant canonical error codes.

What is the best way to debug a Polymarket mirror misbehaving on VWAP?

The best way to debug a misbehaving Polymarket mirror is to zero in on a single divergence where the VWAP is off, extract the exact DB rows and Loki log lines as evidence, verify the bug, and halt immediately.

Does this investigation approach find multiple copy-trade bugs at once?

No, this investigation approach does not find multiple bugs at once. It enforces a one-discrepancy focus to zero in on a single divergence between your position and the target's, ensuring verifiable proof before stopping.

When should I use a focused delta investigation for copy-trading?

You should use a focused delta investigation when a delta exists between positions or when the copy-trade mirror misbehaves with a wrong side, VWAP off, or missed fill, applying strict data-sourcing rules to present findings with exact DB rows and log lines.

What data sources do I need to find a copy-trade delta on Polymarket?

To find a copy-trade delta on Polymarket, you need access to Postgres for exact decision and fill DB rows and Loki for log lines to ground your conclusions and present cited evidence of the discrepancy.