plugin-enable-verify

Verifies plugin usability for a Bot with one read-only probe call per connector.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installed, enabled, and working are three different states for connectors: a plugin can appear in a Bot's tool list yet fail at runtime due to missing per-Bot attachment, expired auth, or a team admin block. This Skill turns "the plugin is installed" into evidence that this Bot can actually call it right now, and names the exact human click required when it cannot. ## Core Features & Use Cases - Read-only probing: Runs exactly one pre-named read-only call per plugin (list, search, get, or an authenticated CLI status check for skill-packs like Firecrawl) and records the observable that came back. - Bucketed classification: Sorts every needed plugin into WORKING, MISSING, AUTH, ADMIN-BLOCKED, or UNVERIFIED, quoting failure text verbatim so routing goes to the right owner. - Dated verification report: Produces a per-Bot report with the plugin list, probe results, human steps in click order (Settings → Plugins, Teams Marketplace), and the single blocking item. - Use Case: Before handing a Bot to a teammate, run the verification to prove each connector returned data in this session, and get a clean stop with the admin's name and click path when a plugin reads "Disabled by team admin". ## Quick Start Verify that every plugin this Bot's job depends on actually works by running one read-only probe per connector and reporting each as working, missing, auth-failed, admin-blocked, or unverified.

Frequently Asked Questions about plugin-enable-verify

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

FAQPage Schema
How do I verify a plugin actually works for my Bot before running it?▼

List the Bot's attached plugins, then make exactly one read-only call per needed plugin, such as a list, search, or get. A plugin passes only if that probe returns real data in the current session; appearing in Settings proves nothing.

What does "Disabled by team admin" mean for a connector?▼

It means the team's connector policy blocks that server, so the plugin is ADMIN-BLOCKED. A team admin must enable it in Teams Marketplace and add it to any MCP allowlist, after which members restart the app.

Can this verification install or enable a plugin for me?▼

No. The process is strictly read-only and cannot install, add, authenticate, enable, or detach a connector, because there is no connector-install API. Every gap it finds ends in a named human click in Settings or Teams Marketplace.

Why is a plugin that worked last week reported as unverified?▼

Verification never inherits a pass from another Bot, a prior date, or the account-level Settings list. Attachment is per Bot, so each run must make its own probe and record fresh evidence before a plugin counts as working.

How are skill-pack plugins like Firecrawl verified without MCP tools?▼

For a skill-pack with zero MCP tools, the probe is an authenticated CLI status check, such as firecrawl --status on the cloud computer. An authenticated status counts as WORKING, a logged-out CLI is AUTH, and an empty MCP list alone is never UNVERIFIED.