agentleFS
molt-botmolt-bot/clawdbot/.agents/skills/plugin-sdk-impact/SKILL.md

plugin-sdk-impact

Skill395k starsChanged todayMITView on GitHub

Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.

  • Installs packages

7 other projects use a version of this.

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 8 mentionsFeb 2026: 9 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the molt-bot/clawdbot repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about molt-bot/clawdbot

The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 18

Talked about on the web (18 times).

On the web · 18

13 more on the web

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never infer permission from the count.

    line 92
  2. Distinctive:

    Do not dismiss a security issue just because no consumers were observed.

    line 131

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plugin SDK impact

Combine current ClawHub inventories with a source scan of every bundled OpenClaw plugin, including plugins absent from ClawHub, to inform compatibility decisions. Static usage identifies dependencies; it does not prove execution or reliance on a particular behavior. Keep the approval and deprecation rules in the SDK boundary guide authoritative.

Investigate

  1. Identify every affected public surface from source, including alternate SDK exports and runtime paths. Verify spelling against the definition and known callers; an incorrect key can return a convincing zero. Trace grouped facades, SDK helpers, and registration readers as well: a flat alias can have zero direct plugin calls while implementing a supported grouped method.
  2. Scan every bundled plugin in a clean OpenClaw checkout using Plugin Inspector's static source analysis. Reuse an installed Inspector 0.4.3 or newer; otherwise install it in a separate temporary directory, without lifecycle scripts:

    inspector_dir=$(mktemp -d)
    npm install --prefix "$inspector_dir" --ignore-scripts @openclaw/plugin-inspector@0.4.3
    node {baseDir}/scripts/scan-bundled.mjs \
      --inspector "$inspector_dir/node_modules/@openclaw/plugin-inspector" \
      --out /tmp/openclaw-bundled-sdk-usage.json

    The scanner defaults to this skill's checkout; --root <checkout> selects another. It discovers extensions/*/openclaw.plugin.json, never executes plugin code, and records the commit, input fingerprint, Inspector version, every plugin, and incomplete analyses. A failed or timed-out scan remains a gap. Plugins without declared entrypoints also remain coverage gaps, because Inspector may miss implicit entrypoints. An interrupted corpus scan cannot be used as a finished inventory. Reuse the report for multiple queries while its source remains unchanged. A changed commit, plugin roster, or uncommitted source invalidates it; rescan instead of editing the receipt.

  3. Query each canonical key with both sources:

    node {baseDir}/scripts/query.mjs 'api-member:api.registerTool' \
      --bundled /tmp/openclaw-bundled-sdk-usage.json

    For “updated within the last three months”, add --months 3. This means the latest eligible public release was uploaded within three calendar months of now, measured in UTC (month ends are clamped). Listing edits and rescans do not count as updates. The stored release date is its creation/upload time; public approval can happen later. --since 2026-07-16T12:00:00Z accepts an explicit cutoff. Report the exact inclusive cutoff from releaseWindow, not a guessed date. Public consumers and coverage use the same window on every page. Bundled source has no comparable upload date: report it separately, unfiltered, even for a recent-release question. The combined count is the union of that public release window and current bundled source, not a count of recent releases.

    The helper follows all usage and coverage pages, including empty intermediate pages. Counts and coverage include every result; items, gaps, and warnings contain bounded examples with omitted counts in output.omitted. Mixed references count in both runtime and type totals. For an investigation needing every consumer or gap, save --full output to a file and read it in sections:

    node {baseDir}/scripts/query.mjs 'api-member:api.registerTool' \
      --bundled /tmp/openclaw-bundled-sdk-usage.json --full > sdk-usage.json

    --help documents local endpoint and traversal limits.

  4. Inspect matched evidence against the proposed change. A method call may not use the behavior being changed. Type-only consumers still matter for type/export removal. Query related members separately; a module import does not prove use of every export. Repeated references in a plugin count as one consumer.
  5. For a usage-count question, report the key, query time, exact release window (if requested), ClawHub and bundled counts, their combined count, bundled commit, and both coverage gaps. Top-level distinctPlugins and coverage remain ClawHub-only; bundled describes source results; combined merges exact package identities once. Some bundled plugins have no package name: when they could overlap public matches, combined.distinctPlugins is null and distinctPluginBounds reports the possible range. observedPluginIdentities counts source identities before that uncertain overlap. Report the range, not its upper bound as an exact count. Different names remain distinct; never guess aliases from display names. Missing bundled evidence makes combined impact unavailable. For a proposed SDK change, also report matched evidence, indirect callers, and your compatibility recommendation. Finish change investigations with the maintainer's decision: preserve behavior, deprecate with migration, or proceed under existing policy. Never infer permission from the count.

Canonical keys

SurfaceExample
SDK modulesdk-module:openclaw/plugin-sdk/core
Named SDK exportsdk-export:openclaw/plugin-sdk/core#OpenClawPluginApi
Plugin API methodapi-member:api.registerTool
Host runtime memberruntime-member:runtime.channel.reply.dispatchReplyFromConfig
Named hookhook:hook.before_agent_start
Manifest contractmanifest-contract:manifest.contracts.tools:example_tool

Keys describe SDK identities, not local aliases. api.runtime members normalize to runtime.*. The inventory includes supported and deprecated references; nonempty deprecationCodes selects entries associated with existing warnings. Per-plugin inspection is available at https://clawhub.ai/api/v1/sdk-usage/plugin?package=<encoded-name>; follow its nextCursor until null to obtain the full inventory.

Interpret the result

ResultReport
Observed consumersReport public, bundled, and combined counts with their separate scopes. Inspect evidence before judging a behavior change.
No observed consumers, complete coverage“No static references detected across N public/bundled plugin identities.” Requires both scans; excludes private non-bundled plugins and unbundled dependencies. Not proof that nobody uses the API.
Partial, failed, missing, incompatible, or unresolved analysisState observed matches, gap counts, and representative gaps. Zero matches leaves impact unknown.
Empty corpusNo eligible plugins were observed; this provides no ecosystem assurance.
Unavailable endpoint, malformed result, or incomplete traversalImpact is unknown. Preserve the error and use local evidence; never substitute zero.

Coverage is tied to current release/artifact and analysis versions. Eligible ClawHub reports have inputKind: "artifact"; bundled reports use "source". A source-checkout benchmark cannot establish what a published package contains. Source-only type references still matter for SDK type and export removal; preserve the source of each match. An old scan timestamp alone does not make an immutable artifact stale. Evidence is sampled; each scan reports its evidence/unknown limits. Pages are live reads, not one snapshot: rerun if releases or visibility change during the investigation. The helper flags changes it observes but cannot establish a transaction-wide snapshot.

Do not dismiss a security issue just because no consumers were observed. Describe how usage evidence affects compatibility risk; security and SDK owners still decide the fix and any exception to the normal migration window.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.