{ "schemaVersion": "1.0", "item": { "slug": "context-scope-tags", "name": "Context Scope Tags", "source": "tencent", "type": "skill", "category": "通讯协作", "sourceUrl": "https://clawhub.ai/phenomenoner/context-scope-tags", "canonicalUrl": "https://clawhub.ai/phenomenoner/context-scope-tags", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/context-scope-tags", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=context-scope-tags", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/context-scope-tags" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/context-scope-tags", "agentPageUrl": "https://openagent3.xyz/skills/context-scope-tags/agent", "manifestUrl": "https://openagent3.xyz/skills/context-scope-tags/agent.json", "briefUrl": "https://openagent3.xyz/skills/context-scope-tags/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Context Scope Tags (Chat Protocol)", "body": "A lightweight, portable convention for explicit context boundaries in chat." }, { "title": "Copy/paste cheat sheet (one screen)", "body": "[ISO: ] fresh slate for this message (no prior project/topic context)\n[SCOPE: ] restrict to one named scope\n[GLOBAL] cross-topic reuse allowed (call out what was reused)\n[NOMEM] do not store long-term memory from this exchange\n[REM] persist preferences/decisions (requires a memory backend; otherwise advisory)\n\nExamples:\n\n[ISO: marketing][NOMEM] Draft 5 ad angles for OpenClaw; don't store memory.\n[SCOPE: openclaw-mem] Explain why lane A is failing; keep it scoped.\n[GLOBAL][REM] Remember: display times in Asia/Taipei unless I say otherwise." }, { "title": "Quick start", "body": "Put one or more tags at the very start of your message.\nPrefer this order: scope tag(s) then memory tag(s).\nWrite normally.\n\nOptional: if your assistant supports command-style shortcuts, /ctx or /context_def can print this cheat sheet." }, { "title": "Tag parsing rules", "body": "Tags must appear at the start of the user's message.\nMultiple tags are allowed.\nTags do not override safety policies, tool access controls, approvals, or platform rules." }, { "title": "Conflicting tags", "body": "Some combinations conflict (for example [ISO] + [GLOBAL], or [REM] + [NOMEM]).\n\nRecommended policy:\n\nLast tag wins for the conflicting dimension.\nIf the combination is ambiguous, ask a clarifying question rather than guessing." }, { "title": "Isolation / scope", "body": "[ISO: ] / [Isolated Context: ]\n\nTreat as a fresh topic.\nDo not pull in other conversation/project context unless the user explicitly re-provides it.\nAllowed implicit carry-over: universal safety rules + a few stable user prefs (timezone, \"don't apply changes without approval\", etc.).\n\n\n\n[SCOPE: ] / [Scoped Context: ]\n\nRestrict reasoning to the named scope.\nIf missing details inside the scope, ask clarifying questions.\n\n\n\n[GLOBAL] / [Global Context OK]\n\nCross-topic reuse is allowed.\nWhen reusing prior context, call out what was reused." }, { "title": "Memory intent", "body": "[NOMEM] / [No Memory]\n\nDo not store durable/long-term memories from this exchange.\n\n\n\n[REM] / [Remember]\n\nSignal that preferences/decisions in the message should be persisted.\nDependency note: actual persistence requires the host agent to have a memory subsystem enabled." }, { "title": "Default behavior (no tags)", "body": "Be conservative about cross-topic mixing.\nIf the user complains about topic bleed, suggest using the tags above." }, { "title": "Cross-platform / chat-surface notes", "body": "Telegram slash commands cannot contain dashes.\n\nUse /context_def (underscore), not /context-def.\n\n\nSlash commands may collide with other bots/skills.\n\nIf /ctx is already taken, use the tag syntax directly (it works everywhere).\n\n\nThe tags themselves are just text; they work the same on Telegram/Discord/Slack/WhatsApp.\nIf a surface auto-formats brackets, it's fine - just keep the tags at the very beginning." } ], "body": "Context Scope Tags (Chat Protocol)\n\nA lightweight, portable convention for explicit context boundaries in chat.\n\nCopy/paste cheat sheet (one screen)\n[ISO: ] fresh slate for this message (no prior project/topic context)\n[SCOPE: ] restrict to one named scope\n[GLOBAL] cross-topic reuse allowed (call out what was reused)\n[NOMEM] do not store long-term memory from this exchange\n[REM] persist preferences/decisions (requires a memory backend; otherwise advisory)\n\nExamples:\n\n[ISO: marketing][NOMEM] Draft 5 ad angles for OpenClaw; don't store memory.\n[SCOPE: openclaw-mem] Explain why lane A is failing; keep it scoped.\n[GLOBAL][REM] Remember: display times in Asia/Taipei unless I say otherwise.\nQuick start\nPut one or more tags at the very start of your message.\nPrefer this order: scope tag(s) then memory tag(s).\nWrite normally.\n\nOptional: if your assistant supports command-style shortcuts, /ctx or /context_def can print this cheat sheet.\n\nTag parsing rules\nTags must appear at the start of the user's message.\nMultiple tags are allowed.\nTags do not override safety policies, tool access controls, approvals, or platform rules.\nConflicting tags\n\nSome combinations conflict (for example [ISO] + [GLOBAL], or [REM] + [NOMEM]).\n\nRecommended policy:\n\nLast tag wins for the conflicting dimension.\nIf the combination is ambiguous, ask a clarifying question rather than guessing.\nSupported tags\nIsolation / scope\n\n[ISO: ] / [Isolated Context: ]\n\nTreat as a fresh topic.\nDo not pull in other conversation/project context unless the user explicitly re-provides it.\nAllowed implicit carry-over: universal safety rules + a few stable user prefs (timezone, \"don't apply changes without approval\", etc.).\n\n[SCOPE: ] / [Scoped Context: ]\n\nRestrict reasoning to the named scope.\nIf missing details inside the scope, ask clarifying questions.\n\n[GLOBAL] / [Global Context OK]\n\nCross-topic reuse is allowed.\nWhen reusing prior context, call out what was reused.\nMemory intent\n\n[NOMEM] / [No Memory]\n\nDo not store durable/long-term memories from this exchange.\n\n[REM] / [Remember]\n\nSignal that preferences/decisions in the message should be persisted.\nDependency note: actual persistence requires the host agent to have a memory subsystem enabled.\nDefault behavior (no tags)\nBe conservative about cross-topic mixing.\nIf the user complains about topic bleed, suggest using the tags above.\nCross-platform / chat-surface notes\nTelegram slash commands cannot contain dashes.\nUse /context_def (underscore), not /context-def.\nSlash commands may collide with other bots/skills.\nIf /ctx is already taken, use the tag syntax directly (it works everywhere).\nThe tags themselves are just text; they work the same on Telegram/Discord/Slack/WhatsApp.\nIf a surface auto-formats brackets, it's fine - just keep the tags at the very beginning." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/phenomenoner/context-scope-tags", "publisherUrl": "https://clawhub.ai/phenomenoner/context-scope-tags", "owner": "phenomenoner", "version": "0.2.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/context-scope-tags", "downloadUrl": "https://openagent3.xyz/downloads/context-scope-tags", "agentUrl": "https://openagent3.xyz/skills/context-scope-tags/agent", "manifestUrl": "https://openagent3.xyz/skills/context-scope-tags/agent.json", "briefUrl": "https://openagent3.xyz/skills/context-scope-tags/agent.md" } }