Install
$ agentstack add skill-itechmeat-llm-code-picoclaw ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PicoClaw
PicoClaw is an ultra-lightweight AI assistant written in Go. This skill is a practical operator playbook for running the CLI, configuring ~/.picoclaw/config.json, and operating gateway + channels.
Links
Quick navigation
- Getting started + common commands:
references/quickstart.md - Config (
model_list, tools, gateway, channels, bindings):references/config.md - Tools (web search, exec guardrails, registries):
references/tools.md - Auth flows (OpenAI OAuth, Google Antigravity OAuth, token):
references/auth.md - Gateway operations (health/ready, cron, heartbeat, voice):
references/gateway.md - Channels (Telegram/Discord/WeCom/Feishu/OneBot/etc):
references/channels.md - Skills management (install/list/remove, channel commands):
references/skills.md - Hook system (observers, interceptors, approvers):
references/hooks.md - Cron scheduling via CLI:
references/cron.md - Migration notes:
references/migration.md - Troubleshooting:
references/troubleshooting.md
When to use
Use when you need to:
- Bootstrap PicoClaw on a host (onboard → config → run)
- Switch providers/models via
model_list - Run the agent in CLI mode or operate
gateway - Enable chat channels (Telegram/Discord/Slack/WeCom/...)
- Send outbound notifications to Microsoft Teams via webhook targets
- Configure tools (web search, exec deny patterns, skills registries)
- Install/remove skills into the workspace
- Use skill channel commands (
/list skills,/use) - Configure hook system (observers, interceptors, approvers)
- Configure agent bindings (route messages to different agents)
- Schedule recurring jobs (cron)
Recipes
1) Initialize + verify
- Create initial config and workspace templates:
picoclaw onboard- Verify what’s configured:
picoclaw status
2) Chat from CLI
- One-shot:
picoclaw agent -m "Hello"- Interactive:
picoclaw agent
3) Run gateway (channels + cron + health)
- Start gateway:
picoclaw gateway- Debug logs:
picoclaw gateway --debug
4) Manage auth
- OpenAI OAuth (optionally device-code for headless):
picoclaw auth login --provider openaipicoclaw auth login --provider openai --device-code- Google Antigravity OAuth:
picoclaw auth login --provider google-antigravity- Check status / list models:
picoclaw auth statuspicoclaw auth models
5) Install skills
- List installed skills:
picoclaw skills list- Install from GitHub repo slug:
picoclaw skills install sipeed/picoclaw-skills/weather- Install from registry:
picoclaw skills install --registry clawhub github
6) Add a scheduled job
- Create a cron job:
picoclaw cron add --name "Daily report" --cron "0 9 * * *" --message "Summarize my inbox"- List jobs:
picoclaw cron list
Critical safety notes
- Do not commit real API keys or OAuth tokens into a repo; keep them in
~/.picoclaw/only. - Be cautious enabling the exec tool; keep deny patterns enabled unless you fully trust the environment.
- Exposing gateway to
0.0.0.0makes health endpoints reachable from the network; do that only intentionally.
Release Highlights (v0.2.8)
- MCP operations: PicoClaw now exposes first-class MCP management commands (
show,add,list,remove,test,edit) and surfaces init/lifecycle failures more clearly. - Custom endpoints + tools: CLI/config flows add better support for custom OpenAI-compatible endpoints and a cross-platform serial hardware tool.
- Chat/web feedback: tool-call visibility, animated tool feedback, restart prompts, and reasoning visibility are more consistent across Pico web/chat surfaces and channels.
Release Highlights (v0.2.9)
- MCP and config UI: the config web UI adds an MCP section, MCP streamable HTTP support is fixed, Gemini MCP schema sanitization is hardened, and v3 config format sync docs/flows were refreshed.
- Tool feedback and edit UX:
tool_feedbackdefaults addpretty_printanddisable_escape_html, parent-session tool feedback cleanup is fixed, and edit-file diff previews improve review before applying generated edits. - Channels and voice: Slack webhook channel support lands, Telegram media groups/SVG media handling improves, queued voice follow-ups and voice media store reload behavior are fixed, and
stopcommand / MQTT channel handling are tightened. - Provider/runtime fixes: Bedrock streaming, DeepSeek vision unsupported errors, DeepSeek/Mimo reasoning replay, network-error retry, and factory reset flows were improved.
Release Highlights (v0.2.6)
- Hooks
respondaction:before_toolhooks can now return a final tool result directly, which is useful for plugin-style tools, caching, or policy-controlled mocks without registering a native tool implementation. - Teams outbound channel:
teams_webhookadds an output-only Microsoft Teams path with named webhook targets and Adaptive Card rendering for richer notifications. - Provider request shaping:
model_list[].custom_headerslets you inject extra HTTP headers per model entry, and fallback resolution now uses each fallback candidate's own provider settings. - Gateway/web reliability: PID ownership/stale-pid handling was hardened, and the web UI now derives its WebSocket endpoint from the browser-visible location instead of backend assumptions.
- Channel polish: Feishu reply context was improved for card/file replies, reducing broken follow-up threading in that connector.
Release Highlights (v0.2.4)
- Hook system: in-process and out-of-process hooks (JSON-RPC over stdio) with observer, LLM interceptor, tool interceptor, and tool approver stages. Configurable via
hooksin config. - Agent bindings: route incoming messages to different agents by channel/account/context via
bindingsconfig section. - Skill channel commands:
/list skills,/use,/use(arm for next message),/use clear. - Configurable log level:
gateway.log_level(debug/info/warn/error/fatal) in config orPICOCLAW_LOG_LEVELenv var. - Voice transcription model:
voice.model_namelets you use any multimodal model for audio transcription; Groq Whisper remains as fallback. - Security config separation:
.security.ymlfile for storing API keys/tokens separate fromconfig.json. - Workspace file hot-reload:
AGENT.md,SOUL.md,USER.md,MEMORY.mdare auto-detected via mtime tracking — no restart needed. - SubTurn error handling and logging improved. Security config precedence fixed during migration.
Links
- Upstream repo (for releases/issues): https://github.com/sipeed/picoclaw
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: itechmeat
- Source: itechmeat/llm-code
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.