customize

Other Community

Repo stars 0
Author repo nano-core

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Add new capabilities or modify nano-core behavior. Use when user wants to add channels (Telegram, Slack, email input), change tr…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Workflow”, “Key Files”, “Common Customization Patterns”, “Adding a New Input Channel (e.g., Telegram, Slack, Email)”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name customize directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Workflow / Key Files / Common Customization Patterns” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

nano-core Customization

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

Workflow

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

Key Files

File	Purpose
`src/config.ts`	Assistant name, trigger pattern, directories
`src/index.ts`	Message routing, WhatsApp connection, agent invocation
`src/db.ts`	Database initialization and queries
`src/types.ts`	TypeScript interfaces
`src/whatsapp-auth.ts`	Standalone WhatsApp authentication script
`.mcp.json`	MCP server configuration (reference)
`groups/CLAUDE.md`	Global 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:

Find/add MCP server for the channel
Add connection and message handling in src/index.ts
Store messages in the database (update src/db.ts if needed)
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:

Add MCP server to the mcpServers config in src/index.ts
Add tools to allowedTools array
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:

Add command handling in processMessage() in src/index.ts
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:

Create appropriate service files
Update paths in config
Provide setup instructions

After Changes

Always tell the user:

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

Example Interaction

User: "Add Telegram as an input channel"

Ask: "Should Telegram use the same @Andy trigger, or a different one?"
Ask: "Should Telegram messages create separate conversation contexts, or share with WhatsApp groups?"
Find Telegram MCP or library
Add connection handling in index.ts
Update message storage in db.ts
Tell user how to authenticate and test

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Linux · Docker
Runtime requirements: Docker
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview customize.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# nano-core 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

| File | Purpose |
|------|---------|
| `src/config.ts` | Assistant name, trigger pattern, directories |
| `src/index.ts` | Message routing, WhatsApp connection, agent invocation |
| `src/db.ts` | Database initialization and queries |
| `src/types.ts` | TypeScript interfaces |
| `src/whatsapp-auth.ts` | Standalone WhatsApp authentication script |
| `.mcp.json` | MCP server configuration (reference) |
| `groups/CLAUDE.md` | Global 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:

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Workflow → Key Files → Common Customization Patterns → Adding a New Input Channel (e.g., Telegram, Slack, Email) → Adding a New MCP Integration → Changing Assistant Behavior
terms    -> Understand the request · Plan the changes · Implement · Test guidance
files/cmd -> src/config.ts · src/index.ts · src/db.ts · src/types.ts · src/whatsapp-auth.ts · .mcp.json · groups/CLAUDE.md · mcpServers
body sha256 -> 534cc0730492

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

nano-core Customization

Workflow

Key Files

Common Customization Patterns

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

Adding a New MCP Integration

Changing Assistant Behavior

Adding New Commands

Changing Deployment

After Changes

Example Interaction

Discussion