agentleFS
jaypylesjaypyles/nanoclaw-discord/.claude/skills/customize/SKILL.md

customize

Skill2 starsChanged 9 months agoMITView on GitHub

Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

43 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-atomic-chat-tool, add-dashboard 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.
  • MicrosoftSkill

    add-atomic-chat-tool

    Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.

    Also in 8 projects that use this

  • MicrosoftSkill

    add-dashboard

    Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.

    Also in 8 projects that use this

  • +10 more from microsoft

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 9 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Understand the request: - Ask clarifying questions

    line 12
  2. Distinctive:

    Should messages from this channel go to existing groups or new ones?

    line 36
  3. Very specific:

    Add connection and message handling in src/index.ts

    line 40
  4. Distinctive:

    Ensure responses route back to correct channel

    line 42
  5. Very specific:

    Add MCP server to the mcpServers config in src/index.ts

    line 52
  6. Very specific:

    Add tools to allowedTools array

    line 53
  7. Very specific:

    Add command handling in processMessage() in src/index.ts

    line 74
  8. Distinctive:

    Check for the command before the trigger pattern check

    line 75
  9. Distinctive:

    Create appropriate service files

    line 84
  10. Distinctive:

    Update paths in config

    line 85
  11. Distinctive:

    Always tell the user:

    line 90
  12. Distinctive:

    Ask: "Should Telegram use the same !nano trigger, or a different one?"

    line 102
  13. Distinctive:

    Ask: "Should Telegram messages create separate conversation contexts, or share with Discord channels?"

    line 103
  14. Very specific:

    Add connection handling in index.ts

    line 105
  15. Very specific:

    Update message storage in db.ts

    line 106

“Common” is measured: kept by at least 6 in 10 of the 40 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NanoClaw Customization

This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.

Workflow

  1. Understand the request - Ask clarifying questions
  2. Plan the changes - Identify files to modify
  3. Implement - Make changes directly to the code
  4. Test guidance - Tell user how to verify

Key Files

FilePurpose
src/config.tsAssistant name, trigger pattern, directories
src/index.tsMessage routing, Discord connection, agent invocation
src/db.tsDatabase initialization and queries
src/types.tsTypeScript interfaces
.mcp.jsonMCP server configuration (reference)
groups/CLAUDE.mdGlobal memory/persona

Common Customization Patterns

Adding a New Input Channel (e.g., Telegram, Slack, Email)

Questions to ask:

  • Which channel? (Telegram, Slack, Discord, email, SMS, etc.)
  • Same trigger word or different?
  • Same memory hierarchy or separate?
  • Should messages from this channel go to existing groups or new ones?

Implementation pattern:

  1. Find/add MCP server for the channel
  2. Add connection and message handling in src/index.ts
  3. Store messages in the database (update src/db.ts if needed)
  4. Ensure responses route back to correct channel

Adding a New MCP Integration

Questions to ask:

  • What service? (Calendar, Notion, database, etc.)
  • What operations needed? (read, write, both)
  • Which groups should have access?

Implementation:

  1. Add MCP server to the mcpServers config in src/index.ts
  2. Add tools to allowedTools array
  3. Document in groups/CLAUDE.md

Changing Assistant Behavior

Questions to ask:

  • What aspect? (name, trigger, persona, response style)
  • Apply to all groups or specific ones?

Simple changes → edit src/config.ts Persona changes → edit groups/CLAUDE.md Per-group behavior → edit specific group's CLAUDE.md

Adding New Commands

Questions to ask:

  • What should the command do?
  • Available in all groups or main only?
  • Does it need new MCP tools?

Implementation:

  1. Add command handling in processMessage() in src/index.ts
  2. Check for the command before the trigger pattern check

Changing Deployment

Questions to ask:

  • Target platform? (Linux server, Docker, different Mac)
  • Service manager? (systemd, Docker, supervisord)

Implementation:

  1. Create appropriate service files
  2. Update paths in config
  3. Provide setup instructions

After Changes

Always tell the user:

# Rebuild and restart
npm run build
launchctl unload ~/Library/LaunchAgents/com.nanoclaw.plist
launchctl load ~/Library/LaunchAgents/com.nanoclaw.plist

Example Interaction

User: "Add Telegram as an input channel"

  1. Ask: "Should Telegram use the same !nano trigger, or a different one?"
  2. Ask: "Should Telegram messages create separate conversation contexts, or share with Discord channels?"
  3. Find Telegram MCP or library
  4. Add connection handling in index.ts
  5. Update message storage in db.ts
  6. Tell user how to authenticate and test

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.