Agent skill
system-init
Initialize or hydrate the agent's memory system and verify configuration.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/system-init
SKILL.md
System Initialization
This skill handles the initialization of the agent's memory system. It ensures that the necessary directory structures, configuration files, and core context templates are in place.
Usage
Run this command at the start of a new project or when you need to reset/repair the memory system structure.
uv run python .fleet/context/scripts/memory_manager.py init
Actions Performed
- Hydrates Templates: Copies
core/*.template.mdto activecore/*.mdfiles if they don't exist. - Config Setup: Ensures
.chroma/config.yamlexists (creating from template if needed). - Recall Scratchpad: Creates
recall/current.mdfor the current session context.
Chroma Cloud Setup
After initialization, set up Chroma Cloud:
-
Edit config: Add your Chroma Cloud credentials to
.fleet/context/.chroma/config.yaml:yamlcloud: tenant: "your-tenant" database: "your-database" api_key: "your-api-key" -
Create collections: Run the setup command to create collections in Chroma Cloud:
bashuv run python .fleet/context/scripts/memory_manager.py setup-chroma -
Verify status: Check that everything is connected:
bashuv run python .fleet/context/scripts/memory_manager.py status
Collections Created
| Collection | Name | Purpose |
|---|---|---|
semantic |
agentic-fleet-semantic | Facts about project and user |
procedural |
agentic-fleet-procedural | Learned skills and patterns |
episodic |
agentic-fleet-episodic | Session history and context |
Environment Variables (Optional)
Instead of config file, you can use environment variables:
CHROMA_API_KEY- Your Chroma Cloud API keyCHROMA_TENANT- Your tenant nameCHROMA_DATABASE- Your database name
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?