skills.rest
Qredence
QredenceOFFICIAL
Explore all skills by this author →
Website𝕏@agenticfleetGitHub

volume-bootstrap

Clarify Daytona sandbox volume layout and durable memory structure.

51|6|Updated Feb 7, 2026
Search Tags:#memory#filesystem#session-management#sandbox#bootstrap#volume#daytona
One-click install
npx skills add https://github.com/Qredence/fleet-rlm --skill volume-bootstrap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: volume-bootstrap
Source: https://github.com/Qredence/fleet-rlm/tree/main/src/fleet_rlm/scaffold/skills/volume-bootstrap
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill volume-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand and navigate the pre-initialized Daytona volume filesystem and its memory/knowledge structure to enable safe, predictable sandbox workflows.

Core Features & Use Cases

  • Volume layout awareness: know what directories exist and how to store state
  • Memory and knowledge access: understand persistent memory and knowledge stores
  • Sandbox automation hooks: aware of functions like ensure_daytona_volume_layout, init_memory_db, and seed_system_skills
  • Session and artifact management: plan how sessions manifests, artifacts, and logs persist across restarts

Quick Start

Inspect the sandbox volume layout and begin using memory, artifacts, and sessions according to the documented contracts.

Frequently Asked Questions about volume-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the Daytona sandbox volume layout work for persistent memory?▼

The Daytona sandbox volume layout exposes a pre-initialized filesystem with structured directories for memory, knowledge stores, and artifacts. It enables safe, predictable sandbox workflows by defining where state persists across restarts.

What is the best way to manage session artifacts across sandbox restarts?▼

Session artifact management across restarts relies on the durable volume structure to persist manifests, logs, and artifacts. You store state in the designated directories so sessions survive sandbox restarts predictably.

How do I initialize the memory database when setting up a Daytona sandbox?▼

Initializing the memory database uses the init_memory_db function to establish the persistent memory store. This runs during sandbox setup alongside ensure_daytona_volume_layout and seed_system_skills to prepare the knowledge structure.

Do I need to manually create directories for sandbox state and logs?▼

No, you do not need to manually create directories. The ensure_daytona_volume_layout function automatically provisions the required filesystem structure for memory, artifacts, sessions, and logs during sandbox initialization.

Why does my sandbox lose stored knowledge after a restart?▼

Sandbox knowledge loss after restart typically occurs when state is written outside the designated durable volume directories. You must store memory and artifacts within the documented volume layout to ensure persistence.

Can I inspect the memory storage structure before running workflows in the sandbox?▼

Yes, you can inspect the sandbox volume layout to see available directories for memory, artifacts, and sessions. Reviewing these documented contracts before running workflows ensures correct state storage.

Related Skills

Explore More Software Engineering Skills→
blaxel-aiblaxel-ai
3

migrate-from-daytona

Translate Daytona sandbox code to Blaxel equivalents for TypeScript and Python.

Official
Advanced
dmzoneilldmzoneill
2

memory-view

View and manage persistent memory sections, issues, merge requests, and follow-ups.

Community
Intermediate
jonnytacos8jonnytacos8

blogwatcher

Track blog updates and RSS/Atom feeds via a CLI workflow.

Community
Intermediate
rohitg00rohitg00
944

k8s-backup

Back up and restore Kubernetes workloads using Velero.

Community
Advanced