verifier
claudeProbe plugin for re-verifying findings recorded in research.md
24 skills · hooks
userConfig re-probe for the post-2.1.207 spec: exec-form ${user_config.*} substitution, CLAUDE_PLUGIN_OPTION_<KEY> env in hooks, skill/agent content substitution, and the manifest `default` field. Declares every documented option field (string/number/boolean, required, sensitive, default, multiple, min/max) so the input UI can be compared between Claude Desktop Code and Cowork.
Plugin cowork-userconfig2-probe from marketplace verifier-mp in kazukinagata/analyzing-claude-plugin. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
uc2-checkpost-2.1.207 の userConfig 仕様(shell-form hook は ${user_config.*} を拒否 / exec form は置換 / CLAUDE_PLUGIN_OPTION_<KEY> env / skill・agent content は非機密のみ置換)を Claude Desktop の Code タブと Cowork タブで実機検証する probe。skill body 側の置換結果を dump し、SessionStart hook が出した UC2-* 行と突き合わせる。
uc2-agentuserConfig の値が agent content でも置換されるか(docs の "skill and agent content" 主張)を確認するだけの probe agent。呼ばれたら下の行をそのまま返す。
echo 'UC2-CTL shell_form_static=alive'
echo
echo
echo
echo
echo
echo
echo
echo
echo
"${CLAUDE_PLUGIN_ROOT}/hooks/dump-opts.sh"
Problems found in this repo's manifests
Probe plugin for re-verifying findings recorded in research.md
24 skills · hooks
Companion plugin used to trigger validator errors (probes 02 and 20)
4 skills
Does a plugin-level SubagentStart hook fire on Cowork, and does its JSON additionalContext reach the subagent? Compares plain stdout, matcher-less JSON and matcher-scoped JSON in one launch.
1 skill · 1 agent · hooks
PreToolUse block-method matrix (decision/permissionDecision/exit2) CLI vs Cowork
1 skill · hooks
Skill-to-skill PreToolUse:Skill block test for CLI vs Cowork
2 skills
Tests whether a value persisted to $CLAUDE_PLUGIN_DATA from a plugin-level SessionStart hook survives across Cowork chat sessions. Write+read-back runs in the host hook (persist.sh) because the VM body has DATA unset; surfaces accumulated per-session markers so cross-session persistence is read from SessionStart context.
1 skill · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.