Agent skill
aget-wake-up
Initialize AGET session with status briefing
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/aget-wake-up-aget-framework-template-executive-a
SKILL.md
aget-wake-up
Initialize an AGET agent session. This skill runs the wake-up protocol to display agent identity, version, fleet status, and session context.
Instructions
When this skill is invoked:
-
Run the wake-up script:
bashpython3 scripts/wake_up.py -
If the script succeeds, summarize the key information:
- Agent name and version
- Fleet status (if supervisor)
- Active projects (if any in
planning/) - Skills and Learnings counts
-
If the script fails or is not found, fall back to manual wake-up:
- Read
.aget/version.jsonfor version info - Read
AGENTS.mdheader for agent identity - Run
git statusfor current state - Count Skills:
ls .claude/skills/ 2>/dev/null | wc -l - Count Learnings:
ls .aget/evolution/L*.md 2>/dev/null | wc -l
- Read
Output Format
Present a concise briefing:
[Agent Name] v[version] ready
- Fleet: [N] agents (if supervisor)
- Location: [current directory]
- Git: [branch] ([clean/dirty])
- Skills: [N] | Learnings: [N]
- Active: [project name] (if any)
Error Handling
- If
scripts/wake_up.pyreturns exit code 1: Report validation warnings - If
scripts/wake_up.pyreturns exit code 2: Report configuration error - If script missing: Use fallback method silently
Related
- L532: Skills vs Learnings Distinction
- CAP-SESSION-001: Wake-Up Protocol
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?