context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
Profile →npx skills add mksglu/context-mode --skill context-mode-ops --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to manage context-mode tasks across GitHub items (issues, PRs, releases) and marketing activities, coordinating a parallel team of 10-20 dynamic subagents per task to perform triage, reviews, releases, bug fixes, and related checks.
How it works
The skill directs operating as an Engineering Manager, spawning a team of subagents with ultrathink authority to work in parallel on a wave of tasks. It emphasizes reading code and git history to ground decisions, using a set of predefined commands and tools, and applying a structured, multi-hat approach (PO, OSS, Distribution). It requires that changes be validated through a TDD workflow and reviewed by architects when cross-cutting changes are involved. It enforces strict, bright-line commands to subagents and relies on an evidence base (refs/) to verify platform behavior.
When to use it
Use for every ops wave involving triage of issues, PR reviews, releases, marketing content (LinkedIn posts, release announcements), bug fixes, merging contributions, environment variable validation, adapter testing, or syncing branches, with parallel agent coordination.
What it can touch
The skill declares tools: claude-code, codex, copilot, cursor. It instructs spawning subagents and using the agent-teams roster (Staff, Architects, Skeptics, Domain Specialists) to perform work in parallel and ground outcomes with code-read evidence from refs/.
Caveats
Includes a mandatory owner operating directive that mandates parallel execution, ultrathink authority for subagents, and strict anti-hallucination practices using refs/ citations. Requires reading git history before fixes and architecture reviews for cross-subsystem changes. Skipping relevant skills is a violation. No licensing details beyond NOASSERTION are specified here; follow project governance for licensing notes.
## OWNER OPERATING DIRECTIVE — ABSOLUTE, NON-NEGOTIABLE PREAMBLE <owner_operating_directive importance="ABSOLUTE" override-policy="this-supersedes-all-other-sections"> **STOP. Read this in full before doing anything else in this skill.** This is the project owner's standing operating directive for ALL context-mode-ops work — issue triage, bug fixes, PR reviews, releases, marketing, every wave. It is the **single source of truth** for HOW you operate inside this skill. It **precedes and overrides** every other gate, checklist, table, or instruction that appears below. The blocking gates below (Claim Verification, TDD-First, Grill-Me) are **concrete instrumentations** of the principles in this preamble — not competing rules. If any later section conflicts with this preamble, THIS PREAMBLE WINS. You MUST internalize the directive verbatim, in the owner's own voice. **Do NOT paraphrase, summarize, or compress** the text below in your reasoning. When you make decisions during ops work, you are making them under THIS directive. --- > Run /diagnose for everything in parallel with an agent army. All 17 > adapters and all 3 operating systems matter equally. We do not get > to pick favorites
- OWNER OPERATING DIRECTIVE — ABSOLUTE, NON-NEGOTIABLE PREAMBLE
- Decoded operating principles (extracted from the directive — non-exhaustive)
- Timeless MUST Rules — non-negotiable for every ops cycle
- refs/ — Platform Evidence Base (anti-hallucination ground truth)
- Claim Verification: BLOCKING GATE
- TDD-First: BLOCKING GATE
- Grill-Me Review: BLOCKING GATE
- You Are the Engineering Manager
- Workflow Detection
- GitHub CLI (gh) Is Mandatory
- Agent Spawning Protocol
- Validation (Every Workflow)
- Docs Must Stay Current
- Communication (Every Workflow)
Install via skills CLI npx skills add mksglu/context-mode --skill context-mode-ops Or install all context-mode skills npx skills add mksglu/context-mode Or direct path npx skills add https://github.com/mksglu/context-mode/tree/main/skills/context-mode-ops
What does the context-mode-ops skill do?
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
How do I install it?
Run `npx skills add mksglu/context-mode --skill context-mode-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mksglu/context-mode, a repository with 19,611 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.