Make HTTP requests and call APIs from PicoClaw agents
A lightweight HTTP client skill for PicoClaw that lets your agent make GET, POST, PUT and DELETE requests to any API. Supports headers, auth tokens and JSON payloads.
Low blast radius on the evidence available, but it is still third-party code — a quick look at the SKILL.md costs nothing.
It contacts external services. Outbound calls are how data leaves your machine, so it is worth knowing where it connects.
This skill's own description refers to "api"
These permissions are inferred from this listing — the credentials it declares, any maintainer warning, and the operations its own description mentions. ClawVault has not audited this skill's source code. Treat it as a starting point for your own review, not a substitute for one.
PicoClaw does not have a skill-install command. Capabilities come from two places: skill packages, which are SKILL.md directories under workspace/skills/, and built-in tool groups configured in config.json under the tools field, which covers web, mcp, exec, cron and skills. MCP servers are managed through the mcp CLI command group.
mkdir -p workspace/skills/httpPicoClaw discovers skills as directories under workspace/skills/. Each one contains a SKILL.md describing the procedure, which the agent loads on demand.
$EDITOR workspace/skills/http/SKILL.mdKeep it short. Sipeed's own skill-creator guidance is explicit that the context window is a shared resource: include only what the model does not already know, and make each paragraph justify its token cost.
$EDITOR config.jsonThe tools field in config.json controls the web, mcp, exec, cron and skills groups. A skill that shells out needs exec enabled; a scheduled one needs cron. Leave filter_sensitive_data on so API keys and tokens are stripped from tool output before it reaches the model.
picoclaw mcpFor capabilities that already exist as an MCP server, the mcp command group manages those entries in your config rather than writing a skill by hand.
Commands follow the official PicoClaw documentation. Placeholders such as <owner> are filled in by the search step, because registry references are publisher-scoped.
PicoClaw filters sensitive values such as API keys and tokens out of tool results before they are sent to the model, controlled by filter_sensitive_data (on by default) and filter_min_length. Because exec grants shell access, enable it only when a skill genuinely needs it.
Deploy OpenClaw, Hermes, or PicoClaw on Bluehost with the right template for the job.
The GitHub skill gives your OpenClaw agent complete access to GitHub — creating and reviewing pull requests, managing issues, listing repositories, checking build status, browsing code and triggering workflows. For developers running OpenClaw as a coding assistant this skill is essential. It closes the loop between your agent writing code and that code actually landing in a repository. Widely used in automated PR workflows, issue triage pipelines and code review automations. Works seamlessly alongside Composio for teams that need multi-service integration.
N8N Workflow connects your OpenClaw agent to your N8N automation instance, letting the agent trigger workflows, pass data between systems and monitor automation runs through plain conversation. If you already use N8N for business automation, this skill turns your agent into the intelligent orchestration layer on top — deciding which workflows to trigger based on context rather than fixed schedules. Particularly powerful for teams using N8N as their backend automation layer who want to add AI decision-making on top.
Claude Vision enables agents to understand and analyze images, screenshots, diagrams, and visual content. Perfect for agents that process visual information, extract data from images, or analyze screenshots and diagrams.