skills.rest
kridaydave
kridaydaveCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

crew-init

Scaffolds the crew memory directory structure with agents and inbox folders.

1|Updated Jun 1, 2026
Search Tags:#scaffold#memory#handoff#persona#bootstrap#crew#gitkeep
One-click install
npx skills add https://github.com/kridaydave/My_Skills --skill crew-init-kridaydave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crew-init
Source: https://github.com/kridaydave/My_Skills/tree/main/crew-init
Command: npx skills add https://github.com/kridaydave/My_Skills --skill crew-init-kridaydave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Persona-based AI crews need a persistent place to store learned facts and hand off notes between personas, but setting up that memory layout by hand is repetitive and error-prone. This Skill creates the standard memory structure in one pass so personas can read and write from the first session. ## Core Features & Use Cases - Memory Scaffolding: Creates memory/agents/ and memory/inbox/ directories with .gitkeep files so empty folders are committable to git. - Convention Documentation: Writes a memory/README.md template explaining the three-layer memory model (per-persona files, inbox handoffs, stable filenames). - Idempotent Operation: Never overwrites existing memory files; it reports what already exists and only fills in the gaps. - Use Case: Before starting a multi-persona workflow on a new project, run this once so each persona has a dedicated memory file location and a handoff inbox from day one. ## Quick Start Ask the AI to run crew init to set up the crew memory folders in the current project.

Frequently Asked Questions about crew-init

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

FAQPage Schema
How do I set up persistent memory for AI personas in a project?▼

Run the crew-init skill once in the project root. It creates memory/agents/ for per-persona memory files and memory/inbox/ for cross-persona handoffs, plus a README documenting the convention.

How do personas pass information to each other?▼

Personas append dated one-line notes to the target persona's file in memory/inbox/. The receiving persona drains its inbox on its next activation, keeping handoffs asynchronous and auditable.

Will crew init overwrite my existing memory files?▼

No. The skill is idempotent: it checks what already exists, reports it, and only creates missing pieces. Populated agents/ or inbox/ files and existing READMEs are never overwritten or truncated.

Should I commit the memory folder to git?▼

It is your choice. Commit memory/ to share crew knowledge with the team, or add it to .gitignore to keep memory local. The skill mentions the option once but does not decide for you.

When should I not run crew init?▼

Do not run it repeatedly as a persistent mode; it is a one-shot scaffolder. It also does not pre-create per-persona files, since personas create their own memory files lazily on their first real fact.

Related Skills

Explore More Software Engineering Skills→
panaversitypanaversity
28

stories

Convert specs or PRDs into named-persona user stories with testable acceptance criteria.

Official
Advanced
sanskarbasnetsanskarbasnet
1

queue

Display a read-only multi-agent ship queue dashboard from the fstack brain.

Community
Advanced
Coverage-CreativesCoverage-Creatives

Git Configuration

Automate Git repository setup with standardized structures, hooks, and commit conventions.

Official
Advanced
kolife01kolife01

evi-daily-diary

Create a markdown daily diary and append-only JSONL conversation log.

Community
Intermediate