agent-import
Import an agent migration bundle into Starchild from the relay service. Use when moving an agent from another platform into Starchild (e.g. import my OpenClaw export, load this 8-char migration code).
What this skill does
# Agent Import — Migration Bundle Loader
Download and load a migration bundle into this Starchild agent. The bundle is created by another agent using the `agent-export` skill.
## Quick Start
When user provides a migration code and download token:
```
1. Run the import script to download & extract
2. Review the extracted data with the user
3. Apply each component using native tools
```
## Step 1 — Download & Extract
The user will provide two values from the source agent: a **CODE** (8 chars) and a **DOWNLOAD_TOKEN**.
```bash
python3 skills/agent-import/scripts/download.py <CODE> <DOWNLOAD_TOKEN>
```
The script downloads through the **Fly internal network only** (`sc-agent-migration.internal`). Public download is forbidden by relay policy. If the internal network is unreachable, import fails and must be retried from a Fly machine. The download token authorizes the download; it is single-use and expires with the code (1 hour TTL).
On success the script extracts the bundle to `migration/` and prints a summary of what's included.
## Step 2 — Review Contents
Read and summarize what the bundle contains before applying anything:
```bash
cat migration/manifest.json
cat migration/memory/agent.json 2>/dev/null
cat migration/memory/user.json 2>/dev/null
cat migration/identity/profile.json 2>/dev/null
cat migration/identity/soul.md 2>/dev/null
cat migration/user/settings.json 2>/dev/null
cat migration/tasks/tasks.json 2>/dev/null
cat migration/env/keys.json 2>/dev/null
find migration/files/ -type f 2>/dev/null
```
**Always show the user a summary and ask for confirmation before applying.**
## Step 3 — Apply Components
Apply each component using Starchild native tools. The order matters:
### 3a. User Settings (first — sets timezone/language for everything else)
Read `migration/user/settings.json`, then call:
```
user_settings(action="update", settings={
"name": "...",
"what_to_call": "...",
"timezone": "...",
"language": "..."
})
```
Only include fields that are present in the JSON.
### 3b. Agent Identity
Read `migration/identity/profile.json`, then call:
```
agent_profile(action="update", profile={
"name": "...",
"vibe": "...",
"emoji": "...",
"creature": "..."
})
```
### 3c. SOUL.md
If `migration/identity/soul.md` exists, read it and write to `prompt/SOUL.md`.
Merge with existing SOUL.md if it has content. Don't overwrite platform defaults blindly — integrate the personality bits.
### 3d. Memory — Agent
Read `migration/memory/agent.json`, for each entry call:
```
memory(action="add", target="memory", content="<entry>")
```
⚠️ Memory has a 5000 char limit. If the bundle has many entries, prioritize the most useful ones. Check current usage with `memory(action="read")` first.
### 3e. Memory — User
Read `migration/memory/user.json`, for each entry call:
```
memory(action="add", target="user", content="<entry>")
```
⚠️ User memory has a 3000 char limit. Prioritize preferences and corrections.
### 3f. Tasks
Read `migration/tasks/tasks.json`, for each task:
1. `scheduled_task(action="register", title=..., schedule=..., description=..., channels=...)`
2. Write the `run.py` script based on the description
3. Test it: `bash("python3 tasks/{job_id}/run.py")`
4. `scheduled_task(action="activate", job_id=...)`
Tasks need actual implementation — the description is a spec, not runnable code. Use your judgment to build each task's script.
### 3g. Environment Keys
Read `migration/env/keys.json`, then call:
```
request_env_input(env_vars=[...], reason="Migration from <source>")
```
This prompts the user to enter values securely.
### 3h. Files
Copy files from `migration/files/` to the workspace:
```bash
cp -r migration/files/* . 2>/dev/null
```
Review what's being copied and skip anything that would overwrite important existing files.
## Step 4 — Cleanup
```bash
rm -rf migration/ migration-bundle.tar.gz
```
## Error Handling
| Error | Cause | Fix |
|-------|-------|-----|
| `401 unauthorized` | Wrong or missing download token | Re-check the token from the source agent output |
| `404 not found` | Code already used or never existed | Ask source agent to re-export |
| `410 expired` | Code older than 1 hour | Ask source agent to re-export |
| `403 internal_only` | Download attempted from non-Fly-internal network | Run import from a Fly machine / internal network |
| `429 rate limited` | Too many failed attempts | Wait 1 hour |
| Invalid tar.gz | Corrupted upload | Re-export from source agent |
| No manifest.json | Invalid bundle structure | Bundle must have manifest.json at root |
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.