zz-plugin-locate

Resolves a plugin's released version, content digest, skill versions, and declared tools for evaluation.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/zhixuan312/zz-stack --skill zz-plugin-locate-zhixuan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zz-plugin-locate
Source: https://github.com/zhixuan312/zz-stack/tree/main/catalog/zz/zz-plugin-eval/skills/zz-plugin-locate
Command: npx skills add https://github.com/zhixuan312/zz-stack --skill zz-plugin-locate-zhixuan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plugin evaluation scores are meaningless unless pinned to an exact released version, since skill content changes weekly. This Skill settles precisely which plugin, at which released version, with which skill versions and declared tools, is being evaluated before any measurement begins. ## Core Features & Use Cases - Version Resolution: Calls plugin_locate to return the plugin's latest released version and its own content digest, distinct from the shelf-wide digest shown by claude plugin list. - Surface Declaration: Returns the skill versions shipped, the MCP servers declared, and the tools the plugin's skills tell an agent to call. - Release Enforcement: Refuses to proceed when no released version is recorded, preventing evaluation of whatever happens to be on disk. - Use Case: As stage 1 of a plugin evaluation initiative, run plugin_locate(plugin: "sdlc") to pin the version and digest, then hand both to every later evaluation stage so the measurement cannot drift onto different content. ## Quick Start Run plugin_locate for the plugin being evaluated and state the returned version, digest, skill count, and server count before continuing to the next evaluation stage.

Frequently Asked Questions about zz-plugin-locate

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

FAQPage Schema
How do I pin a plugin to an exact version before evaluating it?▼

Call plugin_locate with the plugin name to get its latest released version and content digest. Carry both the name and version into every later evaluation stage so the score belongs to fixed, released content.

Why does a plugin evaluation need a released version instead of the catalog content?▼

The catalog represents the next release, not what someone installed. Skills change weekly, so a score is only comparable when pinned to the version and digest recorded at release time.

What is the difference between the plugin digest and the shelf digest?▼

The shelf digest shown by claude plugin list is computed over the whole shelf including the deployment address, so every plugin shares the same suffix. The plugin's own digest identifies only that plugin's shipped content.

What happens if plugin_locate finds no recorded version?▼

The skill refuses to continue. A missing version means the plugin does not exist under that name or has not been released since version recording began, and evaluating unreleased content cannot be compared to anything.

Does tools_named show every tool a plugin can reach?▼

No. tools_named lists only the tools the plugin's own skills tell an agent to call, which is its claim rather than its full reach. Tools merely present on a shared door but unused say nothing about the plugin.