Skill - replication in v2

Это текст skill/procedure, который fresh agent должен перенести в базу пользователя как skills/agent-garden-replication-v2.md и использовать перед завершением сессии.

Trigger

Use this skill when:

  • setting up a Trip2G archive for Agent Garden;
  • finishing a fresh-agent onboarding run;
  • writing or updating replication-guide.md;
  • preparing the next agent to repeat the setup;
  • creating a new v2 folder/reproduction package.

Goal

Перед завершением работы агент должен оставить следующему агенту не просто summary, а воспроизводимый seed:

instructions + logs + folder structure + lessons + replication guide

Procedure

1. Read current state

Read:

AGENTS.md
SCHEMA.md
index.md
hot.md
log.md
agent-setup-log.md
learning-log.md

If any are missing, create them before writing replication guide.

2. Summarize setup path

In replication-guide.md, write:

  • how Trip2G docs MCP was connected;
  • what docs/tools were found;
  • how the user provided archive/URL;
  • how the archive was unpacked;
  • how the folder structure was created;
  • how sync was attempted;
  • what succeeded;
  • what failed;
  • what secrets were handled as [REDACTED].

3. Preserve exact folder skeleton

Include a tree:

.
├── AGENTS.md
├── SCHEMA.md
├── index.md
├── log.md
├── hot.md
├── tasks.md
├── learning-log.md
├── agent-setup-log.md
├── replication-guide.md
├── _raw/
├── _meta/
├── skills/
├── lessons/
├── failures/
├── proposals/
└── daily/

4. Write next-agent bootstrap prompt

Add a section:

## First prompt for next agent

You are a fresh Agent Garden agent. Start by reading `AGENTS.md`, `SCHEMA.md`, `index.md`, `hot.md`, latest `log.md`, `agent-setup-log.md`, and this `replication-guide.md`. Continue the Trip2G setup without exposing secrets. If you improve the setup, update `replication-guide.md` and create the next v2 reproduction package.

5. Write first verification task

Add:

## First verification task

Verify that the Trip2G instance can be searched/read by an agent, that `index.md` links to the core files, that `log.md` records the setup, and that `replication-guide.md` is enough for a new agent to repeat the process.

6. Create next v2 package

If the user asks for a new replication package, create/update:

v2/
├── 00 - README.md
├── 01 - Инструкция для fresh agent - Trip2G onboarding.md
├── 02 - Настройка архива как LLM Wiki.md
├── 03 - Skill - replication in v2.md
└── 04 - Шаблон лога настройки агента.md

The next package should preserve what worked and explicitly mark what changed from the previous generation.

7. Update logs

Append to log.md:

## YYYY-MM-DD HH:MM UTC — Replication guide updated

- Actions:
  - Updated `replication-guide.md`.
  - Preserved folder skeleton.
  - Wrote next-agent bootstrap prompt.
- Next:
  - New agent should run the verification task first.

Append to learning-log.md if a reusable lesson emerged.

Quality checklist

  • replication-guide.md exists.
  • It tells next agent which files to read first.
  • It explains how Trip2G docs MCP was used or why it was unavailable.
  • It records archive/sync setup without secrets.
  • It includes folder skeleton.
  • It includes first prompt and verification task.
  • Logs are updated.
  • Next v2 package can be recreated.