What is Context Scope Tags?

A lightweight convention for explicit context boundaries in chat that uses tags like [ISO], [SCOPE], [GLOBAL], [NOMEM], and [REM] at the start of messages.

Do tags override safety policies?

No. Tags do not override safety policies, tool policies, or approvals.

How do I start using it in a chat?

Place tags at the start of the message, then write normally. Use the recommended order: scope before memory intent.

Context Scope Tags

Verified

@phenomenoner

npx machina-cli add skill @phenomenoner/context-scope-tags --openclaw

Files (1)

SKILL.md

2.8 KB

Context Scope Tags (Chat Protocol)

A lightweight, portable convention for explicit context boundaries in chat.

Quick start

Put one or more tags at the very start of your message, then write normally.

Examples:

[ISO: FinLife] Debug the Windows run instructions. Don’t use any other repo context.
[SCOPE: openclaw-mem] Implement the next benchmark step. Keep the answer scoped.
[GLOBAL][REM] Remember: use UTC for cron schedules unless I say otherwise.
[ISO: marketing][NOMEM] Draft 5 ad angles; do not store any long-term memory.

Tag parsing rules

Tags must appear at the start of the user’s message.
You may place multiple tags (recommended order: scope → memory intent).
Tags do not override safety policies, tool policies, access controls, or approvals.

Supported tags

Isolation / scope

[ISO: <topic>] / [Isolated Context: <topic>]
- Treat as a fresh topic.
- Do not pull in other conversation/project context unless the user explicitly re-provides it.
- Allowed implicit carry-over: universal safety rules + a few stable user prefs (timezone, “don’t apply config changes without approval”, etc.).
[SCOPE: <topic>] / [Scoped Context: <topic>]
- Restrict reasoning to the named scope.
- If missing details inside the scope, ask clarifying questions.
[GLOBAL] / [Global Context OK]
- Cross-topic reuse is allowed.
- When reusing prior context, call out what was reused.

Memory intent

[NOMEM] / [No Memory]
- Do not store durable/long-term memories from this exchange.
[REM] / [Remember]
- If the message contains a preference/decision/setting, store it as a short durable memory.

Default behavior (no tags)

Be conservative about cross-topic mixing.
If the user complains about topic bleed, suggest using the tags above.

Command-style cheat sheet responses

If the user sends /ctx or /context_def, respond with a short copy/pasteable cheat sheet:

tags + one-line meaning
two examples

Cross-platform / chat-surface notes

Telegram slash commands cannot contain dashes.
- Use /context_def (underscore), not /context-def.
The tags themselves are just text; they work the same on Telegram/Discord/Slack/WhatsApp.
If a surface auto-formats brackets, it’s fine—just keep the tags at the very beginning.

Source

git clone https://clawhub.ai/phenomenoner/context-scope-tagsView on GitHub

Overview

Context Scope Tags provide a lightweight convention for explicit context boundaries in chat. Use tags like [ISO], [SCOPE], [GLOBAL], [NOMEM], and [REM] at the start of messages to isolate topics and control memory. This prevents cross-topic bleed and keeps conversations focused.

How This Skill Works

Place one or more tags at the very start of your message, then write normally. Tags can be ISO (isolate), SCOPE (restrict to a topic), GLOBAL (reuse context), NOMEM (no long-term memory), or REM (remember a setting). Tags don’t override safety policies, and the recommended order is scope first, then memory intent.

When to Use It

You need strict topic isolation in a chat to prevent bleed between conversations.
You want to restrict reasoning to a named scope or project.
You intend to reuse global context but want explicit acknowledgment of it.
You must avoid storing memories from this exchange for privacy or compliance.
You want to persist a preference or decision as a short-term memory.

Quick Start

Step 1: Place one or more tags at the very start of your message.
Step 2: Write your content normally after the tags.
Step 3: Use the recommended tag order and choose ISO/SCOPE for topic control, NOMEM/REM for memory intent.

Best Practices

Always place tags at the very start of the message.
Use the recommended order: scope → memory intent (e.g., [SCOPE: topic] [REM]).
Choose ISO for isolated topics and SCOPE for scoped topics to avoid bleed.
Remember that tags do not override safety, tool, or access controls.
Keep messages concise after tags to maintain clarity and performance.

Example Use Cases

[ISO: FinLife] Debug the Windows run instructions. Don’t use any other repo context.
[SCOPE: openclaw-mem] Implement the next benchmark step. Keep the answer scoped.
[GLOBAL][REM] Remember: use UTC for cron schedules unless I say otherwise.
[ISO: marketing][NOMEM] Draft 5 ad angles; do not store any long-term memory.
[SCOPE: analytics] Analyze user engagement within the analytics scope only.

Frequently Asked Questions

Add this skill to your agents