Skip to content

v0.3.0 — real installation regressions and plugin context

Latest

Choose a tag to compare

@oh79 oh79 released this 21 Oct 03:06
d57d4d8

Three reported installations exposed resources that the comparison previously skipped. This release adds concrete inline docs/ and templates/ paths and makes undeclared ${CLAUDE_PLUGIN_ROOT} context a finding.

npx --yes agent-context-check@0.3.0 compare --source ./skill --artifact ./installed/skill

For complete plugin trees, declare a relative plugin location inside both roots:

npx --yes agent-context-check@0.3.0 compare \
  --source ./plugin-source --artifact ./plugin-copy \
  --plugin-root . skills/example/SKILL.md

The API accepts pluginRoot; the GitHub Action accepts plugin-root. Use oh79/agent-context-check@v0.3.0.

Validation replayed a documented copy and two actual pinned skills@1.5.25 GitHub installations, without deleting files from the outputs:

  • everyday-causal-skills: template coverage increases from 6 to 10 recognized references. Both versions fail with source-missing because shared resources are not skill-local.
  • Salesforce: five selected skills now report 10 unresolved plugin-context references instead of silently checking none. This does not inspect the runtime environment or fabricate missing-file flags.
  • ai-dotfiles: the real empty-docs installation now reports 75 artifact-missing references instead of a false clean.
  • Separate resource-complete controls pass for all three cases. They are local data copies, not upstream fixes or native plugin installations.

65 offline tests pass. The public report records exact SHAs, commands, source lines and limits; the attached JSON captures before/after reports and the final scanner source hash.

Full validation report.

The scanner remains offline, read-only and dependency-free. It does not run skill commands or agents, infer a shared parent resource root, evaluate dynamic shell paths, or prove successful agent behavior.