capability-delta-review

Reviews hashed capability gate diffs to classify entitlement changes as adopt, ignore, or not applicable.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Grok Bot account's entitlement set changes, it is easy to misread the diff: gate names disappear because client bundle literals moved, unnamed gates belong to other products, and RPC probing errors get confused. This Skill turns a hashed gate diff into an honest verdict instead of reporting movement the vendor never made. ## Core Features & Use Cases - Id-based diffing: Compares hashed gates.enabled_ids against a reviewed baseline, using names only to describe rows the id-diff already found. - Three-verdict classification: Labels each changed capability as adopt, ignore with reason, or not a Grok Bot capability at all. - RPC existence discipline: Distinguishes 400 invalid_argument, 404 not_found, and route-not-found answers, and requires checking every service prefix before claiming no read RPC exists. - Use Case: After a client upgrade appears to remove 38 named capabilities, use this Skill to confirm via id-diff that all gates are still enabled and only the string literals left the bundle. ## Quick Start Review the newest audit's enabled gate ids against the reviewed baseline and give me a verdict for each changed capability.

Frequently Asked Questions about capability-delta-review

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

FAQPage Schema
How do I review capability changes in a Grok Bot account?▼

Diff the hashed gate ids in the newest audit's enabled_ids against the reviewed baseline, then classify each change as adopt, ignore, or not a Grok Bot capability. Use gate names only to describe rows the id-diff already found, never as the diff basis.

Why did capability names disappear after a client upgrade?▼

Gate names are recovered from string literals in the client bundle, so an upgrade can remove the literals while the gates stay enabled. A name-basis diff then falsely reports the vendor removed capabilities; diff the hashed ids instead.

What does a gained gate with no name mean?▼

An unnamed gained gate usually belongs to another product sharing the same backend and cannot be invoked from the Grok Bot client. Record the id and a watch condition for a future bundle naming it rather than inventing a meaning.

How do I tell if an RPC method really does not exist?▼

A 400 invalid_argument means the method exists but was called wrong, and 404 not_found means the method exists but the resource does not. Only a route-not-found answer indicates a missing method, and you must check every service prefix first.

Does this skill enable or toggle capabilities it recommends adopting?▼

No. For an adopt verdict it only names the single smallest action that turns the capability on and how to verify it took effect. A person or another process performs the actual change.