菜单
One-shot installer for the agent-monitor terminal status line. Copies statusline-bar.py to ~/.claude/ and adds the statusLine config to settings.json. Run once per machine. Idempotent and safe.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | install-statusline |
| description | One-shot installer for the agent-monitor terminal status line. Copies statusline-bar.py to ~/.claude/ and adds the statusLine config to settings.json. Run once per machine. Idempotent and safe. |
| disable-model-invocation | true |
| allowed-tools | Bash |
Run this skill once per machine to enable the agent-monitor terminal status bar (model name + color-coded context usage bar, shown below your Claude Code prompt).
statusline-bar.py from this plugin to ~/.claude/statusline-bar.py"statusLine" config into ~/.claude/settings.json (preserves all other keys)Fully restart Claude Code — not /reload-plugins. The statusLine config is
only read at startup. Press Ctrl+C or /exit, then run claude again.
Plugins cannot modify user settings.json or install files into ~/.claude/
directly. The statusline config has to be opted in via this skill.
settings.json keyssettings.json is not valid JSON (won't corrupt your config)python3 "${CLAUDE_SKILL_DIR}/scripts/install_statusline.py" \
|| python "${CLAUDE_SKILL_DIR}/scripts/install_statusline.py"
Use whichever Python binary exists on the system — modern macOS and most Linux
ship python3 only; Windows and some distros ship python only. The installer
itself then auto-detects the right binary when wiring up settings.json.
Scripts are self-contained inside this skill's scripts/ directory so the
skill doesn't depend on sibling skills or cross-directory path traversal.
Use after completing a major work batch (plan execution, feature build, multi-task subagent run) to refresh code-graph-derived data in MEMORY.md/CONTEXT.md/SKILL_MEMORY, append dated narrative entries to TODO/CHANGELOG/lessons-learned, mine cross-project structural habits, and ratchet reusable permissions to global settings. Keeps project DNS in sync with reality.
Use when orchestrating multiple ghengis-skills across a single task -- coordinates pre-action validation, execution, post-action verification, and lesson extraction via a shared JSON scratchpad. TRIGGER when dispatching a subagent, finishing a major task, or when the user mentions "run the full chain", "validate this", "fire the pipeline", or explicitly invokes a chain by name.
Use to build and maintain an evolving understanding of user preferences, communication style, and working patterns — learns from interactions and adapts behavior over time
Use when starting a new project or organizing an existing one — creates self-documenting 4-layer project structure with MEMORY.md, CONTEXT.md, modular CLAUDE.md, and workspace routing
Use to accumulate and retrieve domain knowledge from past tasks — builds a grepable plain-text knowledge base that grows over time, enabling agents to learn from experience without vector databases
Use when reorganizing an existing project's file tree based on what actually connects to what — analyzes import graph, classifies layers, proposes an ideal target tree, validates the plan adversarially, then executes file moves with atomic per-language import rewrites. Always plan-first; never moves a file before the user confirms. TRIGGER on "reorganize this project", "clean up the file tree", "the structure is a mess", "make this match a real project layout", or after project-scaffold detects layout drift.