Manusで任意のスキルを実行
ワンクリックで
ワンクリックで
ワンクリックでManusで任意のスキルを実行
始める$pwd:
$ git log --oneline --stat
stars:400
forks:16
updated:2026年5月30日 03:04
ファイルエクスプローラー
SKILL.md
6 ファイル
readonly
package.json
$ install --global
$ download --local
$ useful --forSOC
| name | using-aegis |
| description | Use when starting a turn or checking Aegis skill routing. |
Subagents skip this skill.
You have Aegis.Before any response/action, check if an Aegis skill is explicit or clearly relevant. Load only that skill; otherwise proceed normally.
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.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.history.jsonl,
.codex/sessions, ~/.claude/projects, or large logs by default. Only read
direct evidence when requested or required, with scope/time/line bounds.Contract when useful: Route: fast-path; Aegis Reason Note; Why; Next.
Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.
Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when the user explicitly asks for first principles, first-principles review, Occam's razor, or when a complex decision has ambiguous goals, competing constraints, repeated fixes, fallback growth, duplicate owners, or architecture/product direction risk.
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Use when explicitly requesting an independent code review, after subagent-driven implementation slices, before merging high-risk work, or when verification finds evidence, baseline, architecture, compatibility, or retirement uncertainty that needs reviewer scrutiny.