MANDATORY routing rules for context-mode. Invoke whenever you analyze, count, filter, compare, search, parse, or transform data; fetch a URL; or run a data-heavy command — so raw bytes stay out of the context window.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./configs/copilot-cli/skills/context-mode/SKILL.mdcontext-mode MCP tools are available in GitHub Copilot CLI. These rules protect the context window from flooding — one unrouted command can dump tens of KB into the conversation. Follow them strictly.
Analyze / count / filter / compare / search / parse / transform data: write
code via ctx_execute(language, code) and console.log() only the answer. Do
NOT read raw data into context. PROGRAM the analysis, do not COMPUTE it by
reading. One script replaces ten tool calls.
ctx_fetch_and_index(url, source) then ctx_search(queries).node -e "fetch(...)", python -c "requests.get(...)") — use
ctx_execute(language, code); only stdout enters context.ctx_execute_file(path, language, code).ctx_batch_execute(commands, queries) — runs all commands,
auto-indexes, returns search. One call replaces dozens.ctx_execute / ctx_execute_file — sandbox; only stdout enters
context.ctx_fetch_and_index(url, source) then ctx_search(queries) — raw
HTML never enters context.ctx_search(queries: [...]) — all questions in one call.Write artifacts to FILES; return a path + one-line description, not inline dumps.
mksglu/context-mode
a35dd45
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.