secondpool-reconcile

Reconciles contradictory usage-pool wordings against quoted client reads.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill secondpool-reconcile-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secondpool-reconcile
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/secondpool-reconcile
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill secondpool-reconcile-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A linked SuperGrok subscription is advertised as a separate usage pool while the FAQ describes whichever-has-more usage, and no one can tell which behavior is real. This Skill settles the contradiction with evidence by quoting both wordings verbatim and testing them against dated client reads, instead of relying on memory or assumed pool math. ## Core Features & Use Cases - Verbatim contradiction capture: Quotes the separate-pool claim and the whichever-has-more claim with sources and dates before any analysis begins. - Client-read reconciliation: Records allowance figures, usage consumed, pool labels, on-demand state, and rollover behavior exactly as rendered, then tests each wording's prediction against the observed figures. - Run-over-run diffing: Compares wording moves, figure moves, and verdict moves against the prior run, and names gaps with an owner and date. - Use Case: After a billing-page wording change, run the reconcile to determine whether the linked SuperGrok allowance actually pools separately, producing a dated markdown verdict with every figure traced to a quoted read. ## Quick Start Ask the assistant to reconcile whether the linked SuperGrok allowance is a separate pool or shared, using fresh reads from the usage and billing pages.

Frequently Asked Questions about secondpool-reconcile

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

FAQPage Schema
How do I check if SuperGrok allowance is a separate pool from Bot usage?▼

Quote both the separate-pool wording and the whichever-has-more FAQ wording verbatim, then read the usage and billing pages and record allowance figures and consumption exactly as rendered. Test which wording's prediction matches the observed figures before declaring a verdict.

How to resolve contradictory billing FAQ wording with evidence?▼

Fix both contradictory wordings in writing with sources and dates, gather fresh client reads, and state what each wording predicts for the observed figures. Report the contradiction as closed only when the reads settle it; otherwise report it open with the evidence quoted.

Can I test usage pooling by toggling on-demand or changing limits?▼

No. The reconcile is strictly read-only and never toggles on-demand, changes monthly limits, or consumes allowance to test pooling. Those actions require the owner's explicit approval for that exact setting and are outside this workflow.

What happens when usage reads contradict each other or are missing?▼

The contradiction is reported as open-with-evidence, never as closed by assumption. Unreadable or unreachable pages become named gaps with an owner and date, and any figure without a quoted source fails the run.

Does a closed pool verdict apply to future billing cycles?▼

No. A closed verdict proves the behavior only on the read date against those specific figures. Future cycles may differ, so the output names the single read that most needs re-checking and when.