setup
Skill17 starsChanged 7 months agoMITView on GitHub
Bootstrap an UnClaw agent from scratch. Converts a stock Claude Code instance into a persistent personal agent with identity, memory, and scheduling.
- Pipes a download into a shell
- Reads credentials
191 other projects use a version of this.
Adopted by
Most recently taken up by
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- futorio/red-greentheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-voice-transcription, add-discord and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 5 projects that use this
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
juancruzmunozalbeloSkilladd-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 7 projects that use this
- +8 more from microsoft
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 33ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- distill-sessionSkill
- heartbeatSkill
- humanizerSkill
- memory-updateSkill
- playwright-cliSkill
- promoteSkill
- researchSkill
- search-memorySkill
- self-improveSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
44 rules. 0 are common, 18 are distinctive, and 26 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
26
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ensure these directories exist:
- Distinctive: line 23
Ensure these critical files exist:
- Very specific: line 35
If .claude/settings.json is missing or malformed, recreate it from templates/settings.json.
- Very specific: line 37
Verify these required hooks exist in .claude/settings.json:
- Very specific: line 44
If any are missing, repair .claude/settings.json from templates/settings.json.
- Distinctive: line 46
Ensure scripts are executable:
- Distinctive: line 53
Ask the user for:
- Distinctive: line 91
Keep it concise (under 20 lines).
- Very specific: line 93
Use config/agent.env as the source of truth for runtime config:
- Distinctive: line 100
Ask: "Do you want to connect a messaging channel like Telegram?"
- Distinctive: line 102
If yes, walk through the prerequisites first, then configure the channel.
- Very specific: line 110
Check ~/.claude/settings.json for "DISABLE_TELEMETRY": "1" in the env object.
- Very specific: line 111
If present, remove it. Claude Code uses feature flags for channels, and this setting causes --channels to fall back to "Channels are not …
- Distinctive: line 117
If installed, tell the user which version is present and move on.
- Very specific: line 118
If not found, install it with curl -fsSL https://bun.sh/install | bash, then verify with bun --version.
- Distinctive: line 128
Wait for the user to provide the token before proceeding.
- Very specific: line 132
Check if the Telegram plugin is already installed by running claude plugin list 2>&1 | grep -i telegram or checking …
- Distinctive: line 134
If already installed and enabled, tell the user it's present and move on.
- Distinctive: line 135
If not installed, tell the user to run these in a Claude Code session:
- Very specific: line 140
If running inside Cursor rather than the Claude Code CLI, add the Telegram MCP server entry to .cursor/mcp.json instead (see the plugin's …
- Distinctive: line 142
After either path, verify the Telegram plugin appears in the installed list.
- Very specific: line 151
Create the per-agent state directory: ~/.claude/channels/telegram-<agent-name>/ (e.g.
- Very specific: line 153
Create ~/.claude/channels/telegram-<agent-name>/.env with TELEGRAM_BOT_TOKEN=<token>
- Very specific: line 158
Write these lines into config/agent.env:
- Distinctive: line 170
After the agent is started and Telegram is connected:
- Very specific: line 173
Ask the user to paste the pairing code (a short hex string like 25255d).
- Very specific: line 174
Read ~/.claude/channels/telegram-<agent-name>/access.json to find the pending entry matching that code.
- Very specific: line 176
Add the senderId to the allowFrom array and remove it from pending.
- Very specific: line 177
Write the updated access.json.
- Very specific: line 178
Create the approval notification: mkdir -p ~/.claude/channels/telegram-<agent-name>/approved then write the senderId to …
- Very specific: line 183
Do not rely on /telegram:access pair for per-agent setups.
- Distinctive: line 187
If the user doesn't have the code yet or the pending entry hasn't appeared, wait a moment and re-read the file.
- Very specific: line 189
If no, leave AGENT_CHANNEL="" and TELEGRAM_STATE_DIR commented out in config/agent.env — tmux-only mode is valid.
- Distinctive: line 196
Ensure it contains the required hooks listed in Step 0
- Very specific: line 197
If not, overwrite it from templates/settings.json
- Distinctive: line 202
Ask: "Do you want automatic heartbeats, session logging, memory promotion, nightly self-improvement, and watchdog restarts via launchd?"
- Distinctive: line 205
Read the chosen session name and project directory
- Very specific: line 210
Write them to ~/Library/LaunchAgents/
- Very specific: line 214
If the assistant job exits with Operation not permitted or exit code 126, tell the user to grant Full Disk Access to /bin/bash in System …
- Very specific: line 216
If no, skip — the agent still works, but recurring tasks must be run manually or via /loop.
- Very specific: line 230
Check tmux session exists: tmux has-session -t <session>
- Very specific: line 231
Check .claude/settings.json exists and includes the required hooks
- Very specific: line 236
If launchd was enabled, verify the jobs are loaded: launchctl list | grep <session>
- Distinctive: line 244
if Telegram is set up, confirm the pairing worked and the bot responds
“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Setup
This skill bootstraps the entire agent. Do not assume hooks, launchd jobs, or even .claude/settings.json already exist.
Step 0: Install or repair the core scaffold
Before personalizing anything:
- Ensure these directories exist:
.claude/.claude/rules/.claude/skills/.claude/scripts/.claude/runtime/launchd/memory/daily-logs/
- Ensure these critical files exist:
CLAUDE.mdidentity/SOUL.mdidentity/user.mdidentity/memory.mdconfig/agent.env.claude/settings.json.claude/rules/*.md.claude/scripts/*.shtemplates/settings.jsontemplates/launchd/*.plist
- If
.claude/settings.jsonis missing or malformed, recreate it fromtemplates/settings.json. Verify these required hooks exist in
.claude/settings.json:SessionStartNotificationPreCompactPostCompactPostToolUse
If any are missing, repair
.claude/settings.jsonfromtemplates/settings.json.- Ensure scripts are executable:
chmod +x bin/start-agent.sh bin/setup.sh .claude/scripts/*.sh
Step 1: Gather identity and role
Ask the user for:
- Agent name (e.g. "Ray", "Jarvis", "Friday")
- Owner name and full name
- Agent role — what this agent is. Not just "engineer." Could be: software engineer, research assistant, content creator, financial analyst, habit coach, food/nutrition tracker, writing partner, ops/devops specialist, data analyst, product manager, or anything else. Let the user type a custom role. This determines the agent's identity, expertise framing, and domain-specific rules.
- Domain expertise — the equivalent of "tech stack" but for any role. Examples:
- Software engineer → "TypeScript, React, Node.js"
- Financial analyst → "equity research, DCF modeling, Bloomberg"
- Content creator → "SEO, WordPress, video editing, social media"
- Habit coach → "behavioral psychology, habit tracking, accountability"
- Research assistant → "academic papers, literature review, citation management"
- Timezone
- OS
- Editor
- Communication style
Step 2: Personalize files
Replace placeholders in:
CLAUDE.md—{{AGENT_NAME}},{{OWNER_NAME}},{{AGENT_ROLE}}identity/SOUL.md—{{AGENT_NAME}},{{OWNER_NAME}},{{AGENT_ROLE}}identity/user.md—{{OWNER_NAME}},{{OWNER_FULL_NAME}},{{TIMEZONE}},{{DOMAIN_EXPERTISE}},{{OS}},{{EDITOR}},{{COMMUNICATION_STYLE}}config/agent.env—AGENT_SESSION_NAME(lowercase agent name),AGENT_CHANNEL.claude/rules/communication.md—{{OWNER_NAME}}.claude/skills/daily-standup/SKILL.md—{{OWNER_NAME}}.claude/skills/distill-session/SKILL.md—{{OWNER_NAME}}.claude/skills/search-memory/SKILL.md—{{OWNER_NAME}}
Generate .claude/rules/domain.md
Generate this file based on the chosen role and domain expertise. It should contain role-appropriate conventions and best practices. Examples:
- Software engineer → coding conventions, testing practices, linting rules
- Content creator → tone guides, SEO checklist, publishing workflow
- Financial analyst → data sourcing rules, model conventions, disclosure practices
- Research assistant → citation style, source evaluation criteria, note-taking format
- Habit coach → tracking format, check-in cadence, encouragement style
- Any role → the file should feel like a senior practitioner wrote their working standards
Keep it concise (under 20 lines). The user can always expand it later.
Use config/agent.env as the source of truth for runtime config:
AGENT_SESSION_NAME→ lowercase agent nameAGENT_CHANNEL→ blank by default, filled if messaging is configuredTELEGRAM_STATE_DIR→ per-agent path, set only if Telegram is configured
Step 3: Messaging channel (optional)
Ask: "Do you want to connect a messaging channel like Telegram?"
If yes, walk through the prerequisites first, then configure the channel.
Prerequisites
Handle these before configuring the channel. Do each silently and report the result to the user.
1. Claude Code channels
Check ~/.claude/settings.json for "DISABLE_TELEMETRY": "1" in the env object.
- If present, remove it. Claude Code uses feature flags for channels, and this setting causes
--channelsto fall back to "Channels are not currently available." - Also check shell profiles for
DISABLE_TELEMETRYorCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC. If either is exported there, remove it and restart the terminal.
2. Bun
The Telegram MCP server runs on Bun. Run bun --version to check.
- If installed, tell the user which version is present and move on.
- If not found, install it with
curl -fsSL https://bun.sh/install | bash, then verify withbun --version. Tell the user it was installed.
3. Telegram bot token
The user needs to create a bot through BotFather — this is the one step that requires manual action on their phone/desktop. Tell the user:
Open @BotFather on Telegram and send
/newbot. It asks for a name (display name, anything) and a username (must end inbot, e.g.my_assistant_bot). BotFather replies with a token like123456789:AAHfiqksKZ8...— copy the whole thing including the number and colon, and paste it here.
Wait for the user to provide the token before proceeding.
4. Telegram plugin
Check if the Telegram plugin is already installed by running claude plugin list 2>&1 | grep -i telegram or checking ~/.claude/plugins/installed_plugins.json.
- If already installed and enabled, tell the user it's present and move on.
- If not installed, tell the user to run these in a Claude Code session:
If running inside Cursor rather than the Claude Code CLI, add the Telegram MCP server entry to/plugin install telegram@claude-plugins-official /reload-plugins.cursor/mcp.jsoninstead (see the plugin's README for the server command and args).
After either path, verify the Telegram plugin appears in the installed list. Tell the user the result. Also verify if the Telegram MCP server appears in the active MCP list.
Per-agent Telegram isolation
Each agent gets its own Telegram state directory so multiple agents can run
different bots on the same machine without conflict. The Telegram MCP plugin
reads TELEGRAM_STATE_DIR from its environment; config/agent.env vars are auto-exported
via set -a in the session scripts, so child processes (including MCP servers) inherit them.
- Create the per-agent state directory:
~/.claude/channels/telegram-<agent-name>/(e.g.telegram-tony,telegram-ray— lowercase agent name) - Create
~/.claude/channels/telegram-<agent-name>/.envwithTELEGRAM_BOT_TOKEN=<token> - Create
~/.claude/channels/telegram-<agent-name>/access.jsonwith:{"dmPolicy": "pairing", "allowFrom": [], "groups": {}, "pending": {}} - Write these lines into
config/agent.env:AGENT_CHANNEL="plugin:telegram@claude-plugins-official" TELEGRAM_STATE_DIR="$HOME/.claude/channels/telegram-<agent-name>"
Why per-agent dirs? The Telegram MCP plugin defaults to ~/.claude/channels/telegram/ for
its bot token and access list. If two agents share that path, they fight over the same bot token
(409 Conflict) and share access lists. TELEGRAM_STATE_DIR overrides this per-agent.
Auto-pair the owner's Telegram account
After the agent is started and Telegram is connected:
- Tell the user: "DM your bot on Telegram now — send any message (e.g. 'hi'). The bot will reply with a pairing code."
- Ask the user to paste the pairing code (a short hex string like
25255d). - Read
~/.claude/channels/telegram-<agent-name>/access.jsonto find the pending entry matching that code. - Extract the
senderIdfrom the pending entry. - Add the
senderIdto theallowFromarray and remove it frompending. - Write the updated
access.json. - Create the approval notification:
mkdir -p ~/.claude/channels/telegram-<agent-name>/approvedthen write thesenderIdto~/.claude/channels/telegram-<agent-name>/approved/<senderId>. The bot polls this directory and sends a "Paired!" confirmation to the user. - Tell the user they're paired — the bot will now respond to their DMs.
Do not rely on /telegram:access pair for per-agent setups. That command reads
~/.claude/channels/telegram/access.json instead of the per-agent directory.
For isolated bots, pair by editing the per-agent access.json directly.
If the user doesn't have the code yet or the pending entry hasn't appeared, wait a moment and re-read the file. The bot writes the pending entry when it receives the first DM.
If no, leave AGENT_CHANNEL="" and TELEGRAM_STATE_DIR commented out in config/agent.env — tmux-only mode is valid.
Step 4: Hooks (required)
Hooks are required for daily logs, compaction safety, and indexing.
- Ensure
.claude/settings.jsonexists - Ensure it contains the required hooks listed in Step 0
- If not, overwrite it from
templates/settings.json - Confirm to the user that hooks are installed/repaired
Step 5: launchd scheduling (optional, macOS only)
Ask: "Do you want automatic heartbeats, session logging, memory promotion, nightly self-improvement, and watchdog restarts via launchd?"
If yes:
- Read the chosen session name and project directory
- Generate plists from
templates/launchd/by replacing:{{AGENT_SESSION_NAME}}{{PROJECT_DIR}}{{AGENT_CHANNEL}}
- Write them to
~/Library/LaunchAgents/ - Validate them with
plutil -lint - Unload old versions if present, then
launchctl loadthe new ones - Verify with
launchctl list | grep <session> - If the assistant job exits with
Operation not permittedor exit code126, tell the user to grant Full Disk Access to/bin/bashin System Settings → Privacy & Security → Full Disk Access. Until then, they should start the agent manually after reboot.
If no, skip — the agent still works, but recurring tasks must be run manually or via /loop.
Step 6: Start the agent
./bin/start-agent.shThen verify the tmux session reaches the ❯ prompt. If Claude shows the workspace trust prompt,
accept it and re-check the pane. If it shows "Channels are not currently available," go back to
Step 3 prerequisite 1.
Step 7: Verify
- Check tmux session exists:
tmux has-session -t <session> - Check
.claude/settings.jsonexists and includes the required hooks - Capture the tmux pane and confirm you see:
Listening for channel messages from: plugin:telegram@...(if Telegram enabled)❯prompt (session is ready)- No "Channels are not currently available" warning
- If launchd was enabled, verify the jobs are loaded:
launchctl list | grep <session>
Step 8: Confirm
Tell the user:
- how to attach:
tmux attach -t <session> - which recurring tasks are automatic vs manual
- that hooks are installed and daily logs/memory promotion will work
- if Telegram is set up, confirm the pairing worked and the bot responds
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

