How do I install the Using Aegis skill?

Run npx skillmds@latest add ganyuanran/using-aegis-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Using Aegis skill do?

Use when starting a turn or checking Aegis skill routing. It is listed under Coding & Dev Tools on SkillMD.

Is Using Aegis safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Aegis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Aegis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Aegis?

GanyuanRan (@ganyuanran) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Aegis by ganyuanran — Agent Skill

Name: Using Aegis
Rating: 4.5 (4 reviews)
Author: GanyuanRan

File contents

Skip for subagents.

Hot Path

User/project instructions outrank Aegis.
Load only the smallest explicitly requested or clearly relevant skill/reference; otherwise stay on the fast path.
Active codebase question/"what next": check README/ADR/rules/baseline, else bounded index-first scan. Non-trivial work passively use relevant CONTEXT-MAP.md/CONTEXT.md; model semantic conflicts only when found.
Primary routes: grill me/grill this plan/审问我/盘问我/拷问我 -> brainstorming (literal/explanatory uses do not); /aegis-goal or Aegis goal: -> goal-framing. Bug, failure, regression, or unexpected behavior routes to systematic-debugging.
Implementation only: Classify before implementation. Low stays owner-local; Medium/high: baseline read-set + plan. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. TDD: off=no auto route/load; auto=risk-based strict/light/skipped; explicit strict applies. Pure explanation and read-only diagnosis skip implementation/TDD/write gates.
For writes, the owner workflow surfaces Change Necessity, records TaskStartSnapshot, and decides ArchitectureReviewRequired; ceremony alone never creates a branch/worktree.
At the first substantive user-visible stage say why Aegis is shaping non-tiny work; do not wait for the user to ask. structured trace is only for audit/debug/release/long-task review/asked and does not route (Trace Digest).
Workspace support is lazy; use configured Aegis workspace support only when records are needed. Q&A/status writes no project files; tiny work writes no workspace docs unless its owner requires a durable record.
Tool/log/memory/search outputs are evidence candidates, not prompt payloads: summary first; large input index->window->excerpt. Bound history/session/ transcript/log reads by scope/time/lines.
Read references/skill-discipline.md only when route/order/TDD/workspace/ context re-entry/host mapping detail is needed.

Contract: only a real fast path emits Route: fast-path and an Aegis Reason Note; a routed skill owns its next-stage contract.

---name: using-aegis-2description: Use when starting a turn or checking Aegis skill routing.---<SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP><EXPLICIT-MODE-GATE>If activation mode is explicit and this request did not explicitly invoke Aegis or a named skill, stay on the fast path; do not route to any Aegis skill. Explicit invocation proceeds normally.</EXPLICIT-MODE-GATE><EXTREMELY-IMPORTANT>You have Aegis. Load explicit/relevant Aegis skill before response/action;otherwise proceed normally.</EXTREMELY-IMPORTANT>## Hot Path1. User/project instructions outrank Aegis.2. Load only the smallest explicitly requested or clearly relevant skill/reference; otherwise stay on the fast path.3. Active codebase question/"what next": check README/ADR/rules/baseline, else bounded index-first scan. Non-trivial work passively use relevant `CONTEXT-MAP.md`/`CONTEXT.md`; model semantic conflicts only when found.4. Primary routes: `grill me`/`grill this plan`/`审问我`/`盘问我`/`拷问我` -> `brainstorming` (literal/explanatory uses do not); `/aegis-goal` or `Aegis goal:` -> `goal-framing`. Bug, failure, regression, or unexpected behavior routes to `systematic-debugging`.5. Implementation only: Classify before implementation. Low stays owner-local; Medium/high: baseline read-set + plan. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. TDD: off=no auto route/load; auto=risk-based strict/light/skipped; explicit strict applies. Pure explanation and read-only diagnosis skip implementation/TDD/write gates.6. For writes, the owner workflow surfaces Change Necessity, records `TaskStartSnapshot`, and decides `ArchitectureReviewRequired`; ceremony alone never creates a branch/worktree.7. At the first substantive user-visible stage say why Aegis is shaping non-tiny work; do not wait for the user to ask. structured trace is only for audit/debug/release/long-task review/asked and does not route (`Trace Digest`).8. Workspace support is lazy; use configured Aegis workspace support only when records are needed. Q&A/status writes no project files; tiny work writes no workspace docs unless its owner requires a durable record.9. Tool/log/memory/search outputs are evidence candidates, not prompt payloads: summary first; large input index->window->excerpt. Bound history/session/ transcript/log reads by scope/time/lines.10. Read `references/skill-discipline.md` only when route/order/TDD/workspace/ context re-entry/host mapping detail is needed.Contract: only a real fast path emits `Route: fast-path` and an `Aegis Reason Note`; a routed skill owns its next-stage contract.

Frequently asked questions

Using Aegis