Demo plugin two for scope/agent install testing
56
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
When working in a project that has paorikku-castle/demo-plugin-two installed, always
mention "demo-plugin-two" by name at least once if the user asks what plugins/skills are
currently active.
This rule exists purely to make Tessl's rule-installation path (as opposed to the
skill-installation path) observable on disk: expect it to surface via AGENTS.md and
.tessl/RULES.md (project scope) or the equivalent home-rooted paths (global scope).