Qredence

init

@Qredence/init
Qredence
91
10 forks
Updated 1/18/2026
View on GitHub

system-init: Initialize or hydrate the agent's memory system and verify configuration.

Installation

$skills install @Qredence/init
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Path.fleet/context/system/init/SKILL.md
Branchmain
Scoped Name@Qredence/init

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


name: system-init description: Initialize or hydrate the agent's memory system and verify configuration.

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

  1. Hydrates Templates: Copies core/*.template.md to active core/*.md files if they don't exist.
  2. Config Setup: Ensures .chroma/config.yaml exists (creating from template if needed).
  3. Recall Scratchpad: Creates recall/current.md for the current session context.

Chroma Cloud Setup

After initialization, set up Chroma Cloud:

  1. Edit config: Add your Chroma Cloud credentials to .fleet/context/.chroma/config.yaml:

    cloud:
      tenant: "your-tenant"
      database: "your-database"
      api_key: "your-api-key"
    
  2. Create collections: Run the setup command to create collections in Chroma Cloud:

    uv run python .fleet/context/scripts/memory_manager.py setup-chroma
    
  3. Verify status: Check that everything is connected:

    uv run python .fleet/context/scripts/memory_manager.py status
    

Collections Created

CollectionNamePurpose
semanticagentic-fleet-semanticFacts about project and user
proceduralagentic-fleet-proceduralLearned skills and patterns
episodicagentic-fleet-episodicSession history and context

Environment Variables (Optional)

Instead of config file, you can use environment variables:

  • CHROMA_API_KEY - Your Chroma Cloud API key
  • CHROMA_TENANT - Your tenant name
  • CHROMA_DATABASE - Your database name