SHREYA GUHA
Community@RADHA0-max
Aspiring developer
Agent Skills by SHREYA GUHA
Showing 53 vetted skills indexed across 1 GitHub repositories.
RADHA0-maxadd-mnemon
Installs mnemon persistent graph-based memory into NanoClaw agent containers via Dockerfile and entrypoint changes.
RADHA0-maxadd-discord
Installs and configures a Discord bot channel adapter for NanoClaw via the Chat SDK.
RADHA0-maxadd-imessage
Installs and configures an iMessage channel adapter for the NanoClaw Chat SDK bridge.
RADHA0-maxlearn
Distills directories, URLs, notes, or conversations into reusable SKILL.md skill files.
RADHA0-maxadd-whatsapp
Installs and authenticates a native Baileys WhatsApp channel adapter with QR or pairing-code login.
RADHA0-maxadd-rtk
Installs the rtk token-compression proxy into agent containers via mounts and PreToolUse hooks.
RADHA0-maxadd-resend
Integrates a Resend email channel adapter into NanoClaw via Chat SDK.
RADHA0-maxadd-opencode
Installs and configures the OpenCode agent provider for NanoClaw container groups.
RADHA0-maxqodo-pr-resolver
Fetches Qodo code review issues from pull requests and applies fixes interactively or in batch.
RADHA0-maxadd-signal
Integrates Signal messaging into NanoClaw via a signal-cli TCP daemon adapter.
RADHA0-maxadd-matrix
Installs and configures a Matrix channel adapter for NanoClaw via the Chat SDK bridge.
RADHA0-maxmigrate-from-openclaw
Migrate OpenClaw installations into NanoClaw v2 through guided interactive phases.
RADHA0-maxadd-deltachat
Integrates a DeltaChat email-based messaging channel into NanoClaw via the stdio-rpc-server adapter.
RADHA0-maxadd-github
Integrates GitHub PR and issue comment threads as agent conversations via Chat SDK.
RADHA0-maxadd-emacs
Adds an Emacs channel to NanoClaw via a local HTTP bridge with org-mode integration.
RADHA0-maxadd-wechat
Integrates a WeChat personal account channel into NanoClaw via Tencent's iLink Bot API.
RADHA0-maxadd-dashboard
Installs a monitoring dashboard and pusher that posts NanoClaw state snapshots over HTTP.
RADHA0-maxget-qodo-rules
Fetches org- and repo-level coding rules from the Qodo API before code generation tasks.
RADHA0-maxuse-native-credential-proxy
Injects Anthropic credentials from .env into NanoClaw containers, bypassing the OneCLI gateway.
RADHA0-maxmanage-mounts
Configure host directory mount allowlists for NanoClaw agent containers.
RADHA0-maxsetup
Guides initial NanoClaw installation by directing users to run the nanoclaw.sh setup script.
RADHA0-maxadd-atomic-chat-tool
Registers an MCP server exposing local Atomic Chat models as container agent tools.
RADHA0-maxadd-codex
Installs OpenAI Codex as a per-group agent provider in NanoClaw with vault-based authentication.
RADHA0-maxadd-ollama-provider
Configure a NanoClaw agent group to route requests to a local Ollama model instead of the Anthropic API.
Frequently Asked Questions About SHREYA GUHA
FAQPage SchemaWhat tasks can I accomplish with RADHA0-max's NanoClaw skills?▼
You can add 15+ messaging channels (Slack, Telegram, WhatsApp, Teams, Matrix), route agents to providers like Codex, OpenCode, or Ollama, attach Gmail and Google Calendar MCP tools, deploy to Vercel, resolve Qodo PR review issues, and run migrations between NanoClaw versions or from OpenClaw.
Who are these NanoClaw skills designed for?▼
They target operators and developers running self-hosted NanoClaw container agents who need to wire chat channels, manage credential vaults, configure mounts, and customize agent behavior. Familiarity with the ncl CLI, containers, and provider configuration is assumed.
How do I install and run these skills in practice?▼
Start with the setup skill for first-time installation, then invoke skills by name or trigger phrase (e.g. 'add telegram', 'migrate from openclaw'). Channels are wired to agent groups via manage-channels, and updates are pulled with update-skills or update-nanoclaw.
What prerequisites and dependencies do these skills require?▼
A running NanoClaw v2 installation with container support is required. Channel skills need their respective credentials (bot tokens, QR pairing, or iLink access); Gmail and Calendar tools require OneCLI Agent Vault with OAuth; the OneCLI gateway requires HTTPS_PROXY set via 'onecli run'.
How are credentials handled when agents call external services?▼
The OneCLI gateway acts as a transparent HTTPS proxy that injects stored tokens at request time, so raw credentials never reach containers or disk. Alternatively, use-native-credential-proxy opts out of OneCLI and reads API keys or OAuth tokens directly from a .env file.