Use when: you chat across topics and want explicit boundaries to prevent topic bleed. Tags: [ISO], [SCOPE], [GLOBAL], [NOMEM], [REM]. (Memory tags are signal...
Security Analysis
high confidenceThis is an instruction-only, self-contained tagging convention for scoping chat context and memory intent; its requirements and behavior are consistent with its description.
The skill's name and description describe a lightweight chat tagging convention; the SKILL.md only contains tag definitions and usage guidance and requests no binaries, credentials, or installs, which is proportionate and expected.
Runtime instructions are limited to tag semantics, placement rules, conflict resolution, and surface-specific notes. There are no commands, file accesses, network calls, or instructions to read unspecified environment variables—no scope creep detected.
No install spec and no code files are present. This is instruction-only, so nothing is written to disk or fetched during install.
The skill declares no environment variables, credentials, or config paths. The memory-related tags are advisory and correctly note that persistence depends on the host agent's memory backend.
always is false and the skill does not request persistent presence or elevated privileges. The SKILL.md advises that '[REM]' requires a memory backend—this is a hosted-agent concern, not a capability of the skill itself.
Guidance
This skill is a harmless, textual convention for marking message scope and memory intent. It cannot itself enforce storage or deletion—'[REM]' only works if your agent has a memory backend and the agent honors the tag, and '[NOMEM]' is advisory. Before relying on these tags for privacy or persistence guarantees, verify how your particular agent implementation interprets them and test on non-sensitive data. Also remember tags do not override platform safety policies or tool access controls.
Latest Release
v0.2.0
Add conflict-handling + clarify memory-tag dependency; improve quick-start + portability notes.
More by @phenomenoner
Published by @phenomenoner on ClawHub
