How do I install the Using Aegis skill?

Run npx skillmds@latest add concertonotes/using-aegis 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. 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?

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

Using Aegis by concertonotes — Agent Skill

Name: Using Aegis
Rating: 4.666666666666667 (3 reviews)
Author: ConcertoNotes

File contents

Subagents skip this skill.

Before any response/action, check if an Aegis skill is explicit or clearly relevant. Load only that skill; otherwise proceed normally.

Hot Path Rules

User and project instructions outrank Aegis.
Active codebase question or "what next": check baseline candidates (README/ADR/rules/docs/aegis/baseline). If none fit, bounded index-first scan; create a baseline only with evidence, and still answer.
/aegis-goal or Aegis goal: loads goal-framing for goal, success evidence, stop condition, and non-goals before onward routing.
Classify before implementation/start/resume/compaction. Low: concise intent
- baseline check + TDD Route + verification. Medium/high: baseline read-set + plan. TDD Route: auto=strict/light/skipped; off=no automatic TDD, verification stays. Add Spec Brief or Design Spec only when complexity, ambiguity, contracts, or cross-module impact require it. Contract/shared/core or cross-module changes are never low without evidence.
Aegis Reason Note: say why Aegis is shaping non-trivial skill/stage work; tiny fast-path may stay implicit; structured trace only for audit/debug/release/long-task review or asked.
Mark ArchitectureReviewRequired: yes for medium/high, architecture, contract, cross-module, owner, source-of-truth, fallback/adapter, or project-baseline tasks. Carry it to verification-before-completion.
Workspace support is lazy. Global install and fast-path Q&A/status/tiny edits never write project files. Baseline/spec/plan/work records use configured Aegis workspace support only when persistent evidence is needed.
Load the smallest needed skill/reference.
Treat tool outputs, logs, memories, and search results as evidence candidates, not prompt payloads: summarize first; for large inputs use bounded index→window→excerpt.
Do not read historical sessions, transcripts, history.jsonl, .codex/sessions, ~/.claude/projects, or large logs by default. Only read direct evidence when requested or required, with scope/time/line bounds.
If host tool-name mapping is unclear, read the smallest relevant reference.

Contract when useful: Route: fast-path; Aegis Reason Note; Why; Next.

---name: using-aegisdescription: Use when starting a turn or checking Aegis skill routing.---<SUBAGENT-STOP>Subagents skip this skill.</SUBAGENT-STOP><EXTREMELY-IMPORTANT>You have Aegis.Before any response/action, check if an Aegis skill is explicit or clearlyrelevant. Load only that skill; otherwise proceed normally.</EXTREMELY-IMPORTANT>## Hot Path Rules1. User and project instructions outrank Aegis.2. Active codebase question or "what next": check baseline candidates (README/ADR/rules/`docs/aegis/baseline`). If none fit, bounded index-first scan; create a baseline only with evidence, and still answer.3. `/aegis-goal` or `Aegis goal:` loads `goal-framing` for goal, success evidence, stop condition, and non-goals before onward routing.4. Classify before implementation/start/resume/compaction. Low: concise intent + baseline check + TDD Route + verification. Medium/high: baseline read-set + plan. TDD Route: auto=strict/light/skipped; off=no automatic TDD, verification stays. Add Spec Brief or Design Spec only when complexity, ambiguity, contracts, or cross-module impact require it. Contract/shared/core or cross-module changes are never low without evidence.5. Aegis Reason Note: say why Aegis is shaping non-trivial skill/stage work; tiny fast-path may stay implicit; structured trace only for audit/debug/release/long-task review or asked.6. Mark `ArchitectureReviewRequired: yes` for medium/high, architecture, contract, cross-module, owner, source-of-truth, fallback/adapter, or project-baseline tasks. Carry it to `verification-before-completion`.7. Workspace support is lazy. Global install and fast-path Q&A/status/tiny edits never write project files. Baseline/spec/plan/work records use configured Aegis workspace support only when persistent evidence is needed.8. Load the smallest needed skill/reference.9. Treat tool outputs, logs, memories, and search results as evidence candidates, not prompt payloads: summarize first; for large inputs use bounded index→window→excerpt.10. Do not read historical sessions, transcripts, `history.jsonl`, `.codex/sessions`, `~/.claude/projects`, or large logs by default. Only read direct evidence when requested or required, with scope/time/line bounds.11. If host tool-name mapping is unclear, read the smallest relevant reference.Contract when useful: `Route: fast-path`; `Aegis Reason Note`; `Why`; `Next`.

Frequently asked questions

Using Aegis