context-scope-tags
par phenomenoner
TransportationRésumé
Use when: you need strict context boundaries in chat (Telegram/Discord/Slack/etc.) and want to prevent topic bleed.
Description
Ce que fait ce skill
A portable tagging convention for setting explicit context boundaries in chat messages. Five tags control isolation, scope, and memory intent: [ISO], [SCOPE], [GLOBAL], [NOMEM], and [REM]. Tags go at the start of a message and work on any text-based chat surface.
Explicit tags give precise control over what context an agent uses, avoiding the silent cross-topic mixing that happens when no boundaries are set.
Quand l'utiliser
- Drafting ad copy without pulling in unrelated project context
- Keeping a debugging session scoped to one codebase
- Preventing a private brainstorm from being stored in long-term memory
- Reusing a cross-project decision without re-explaining it
- Setting a persistent preference like timezone once and carrying it forward
Exemple de workflow
User asks: [ISO: marketing][NOMEM] Draft 5 ad angles for OpenClaw; don't store memory.
- 1
Detects [ISO: marketing] tag at message start
- 2
Clears prior project and topic context, treats message as a fresh slate
- 3
Detects [NOMEM] tag, marks the exchange as non-persistent
- 4
Drafts 5 ad angles scoped to the marketing topic only
- 5
Returns response without storing any long-term memory
Five ad angle suggestions with no memory stored from the exchange
Installation
clawhub install phenomenoner/context-scope-tagsExécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.