A verbose codebase-map skill floods the main municipal chat with analysis noise. How should the skill be configured?
Select an answer to reveal the explanation.
Short Explanation
context: fork is the side office for noisy codebase maps—let the skill rant in isolation so the main chat stays clean for real decisions.
Full Explanation
Verbose skills can pollute the main conversation unless isolated. When a codebase-map skill floods the main municipal chat with analysis noise, configure context: fork so the skill’s verbose analysis stays out of the main conversation while still producing useful side-channel results.
Why the correct option works: context: fork runs the skill in an isolated context. The city team keeps the primary thread focused on decisions; the noisy map output does not consume or distract the main transcript. Quiet skills can remain in-line; verbose ones get the side office.
Why the other three fail by concept: raising verbosity further and always merging skill output into main context worsens noise. Disabling all skills including quiet ones that help the city team throws away useful automation to fix one loud skill. Forcing the skill to run only via unrestricted Bash with no isolation ignores the skill sandbox and increases risk.
Exam caveat: fork is about context isolation for skills—not a substitute for allowed-tools restrictions on dangerous actions. Operational check: set context: fork on the codebase-map skill, run it during a municipal session, and verify the main chat stays clean while the skill still completes its analysis.