system-overview
Show how vibecosystem works - agents, skills, hooks, and self-learning pipeline.
Profile →npx skills add vibeeval/vibecosystem --skill system-overview --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# System Overview Show users how Continuous Claude works - the opinionated setup with hooks, memory, and coordination. ## When to Use - User asks "how does this work?" - User asks "what can you remember?" - User asks "what's different about this setup?" - User runs `/system_overview` ## Response ``` CONTINUOUS CLAUDE SYSTEM OVERVIEW ================================= MEMORY LAYER (PostgreSQL + pgvector) ------------------------------------ - 78,000+ temporal facts from past sessions - Learnings extracted automatically at session end - Semantic search with embeddings RECALL: uv run python opc/scripts/recall_temporal_facts.py --query "your topic" HOOKS (9 event types registered) -------------------------------- SessionStart → Load continuity ledger, rebuild symbol index UserPromptSubmit → Skill activation check, context injection PreToolUse → Smart search routing (Grep → TLDR for code) PostToolUse → File claims, compiler feedback PreCompact → Save state before context compaction Stop → Extract learnings, create handoffs SubagentStart → Register spawned agents SubagentStop → Coordination, handoff creation SessionEnd → Cleanup CONTINUITY SYSTEM ----------------- Ledger: thoughts/ledgers
- When to Use
- Response
- Key Files
- Environment Variables
What does the system-overview skill do?
Show how vibecosystem works - agents, skills, hooks, and self-learning pipeline.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill system-overview --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.