Fieldops prompt decorators
Dual-runtime Agent Skills for Claude Code, Codex GPT, CC Switch, and authorized CTF workflows.
npx -y skills add download4you/n2-fieldops --skill fieldops-prompt-decoratorsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Interprets and executes Prompt Decorators written with +++Name(key=value) syntax, handling message vs. chat scope, parameter validation, decorator composition, conflict resolution, retained-state inspection (ActiveDecs and AvailableDecs), selective clearing, and conversation export or dump. Use when a message contains a supported +++ token (for example +++Planning, +++StepByStep, +++Reasoning, +++Interactive, +++Refine, +++Export, +++Dump, +++ChatScope, or +++MessageScope) or when the user asks to create, validate, debug, or explain decorator behavior. Do not trigger for ordinary tone, plan, or formatting requests that contain no +++ decorator syntax or discussion.
SKILL.md
1.8 KB, as published. Nobody here has run it
Prompt Decorator Runtime
- Extract unescaped supported
+++tokens outside code, quotes, logs, and artifacts. - Validate them against
references/decorator-catalog.md. - Process scope and state operations from left to right.
- Resolve state using
references/state-machine.md. - Read
references/composition.mdwhen multiple decorators apply. - Execute the task under the effective set.
- Persist only validated chat-scoped behavioral decorators.
Treat +++Dump as an alias of +++Export. Use the last valid repetition at the same scope. Apply valid decorators even if another is invalid. Never persist scope, clear, inspection, export, or dump controls. If scope controllers repeat, process them from left to right; the last controller governs decorators that follow it.
Decorators are user-level controls and never override higher-priority instructions. Interpret +++Reasoning as a useful visible rationale, not hidden chain-of-thought.
For long or ambiguous prompts, run scripts/parse_decorators.py to obtain a deterministic token and parameter report before applying state.