For compact local agents
Social media scheduling for NanoClaw
Give NanoClaw a narrow Creagency command surface for one-shot drafts, media uploads, account checks, and confirmation-gated publish actions.
This page stays conservative: use the Creagency CLI and skill unless your NanoClaw runtime exposes MCP config directly.
One-shot draft
NanoClaw creates one draft and exits cleanly.
Prompt
Use Creagency to create one LinkedIn draft from this text. Return the post id and do not publish.Scoped API key
Draft first
Confirmed publish
Quick start
Get NanoClaw working with Creagency.
Small agents still need clear social publishing boundaries.
1
Create a scoped Creagency API key
Use a key with post, asset, and integration scopes. The agent should not receive your social platform passwords.
2
Install the local tooling
Install @creagency/agent, export CREAGENCY_API_KEY, and verify the workspace with auth:status and integrations:list.
3
Add the Creagency skill
Give the agent the Creagency API rules so it knows account discovery, media upload, draft creation, and publish confirmation.
4
Run the first draft
Ask for a draft and require the agent to show the connected account and post summary before scheduling or publishing.
Setup
Use the surface that matches how NanoClaw runs.
Skill files teach the rules, CLI commands handle terminal workflows, and local stdio MCP gives supported agent clients bounded tools.
Skill
Install the Creagency skill so NanoClaw uses the real API rules instead of inventing endpoints.
Steps
Install the skill file in the agent's supported skill directory.
Tell the agent to read the skill before it drafts, uploads media, or prepares publish actions.
Keep API keys outside prompts and chat transcripts.
Install the Creagency skill
Use this for agents that read local skill files.
mkdir -p ~/.agents/skills/creagency-api
curl -fsSL https://creagency.ai/.agents/skills/creagency-api/SKILL.md \
-o ~/.agents/skills/creagency-api/SKILL.mdCLI
Use parseable terminal commands when the agent can run local shell tools.
Steps
Install @creagency/agent globally or call it with npx.
Set CREAGENCY_API_KEY and CREAGENCY_API_ORIGIN in the shell or agent environment.
Run auth:status and integrations:list before creating a post.
Creagency CLI baseline
Start every local agent setup with an auth check and account discovery.
npm install -g @creagency/agent
export CREAGENCY_API_KEY=creagency_xxx
export CREAGENCY_API_ORIGIN=https://api.creagency.ai
creagency auth:status --json
creagency integrations:list --jsonLocal MCP when available
Use creagency-mcp only when the NanoClaw runtime can launch local stdio MCP servers. Hosted remote MCP is planned as a separate OAuth-based connector. Use the local CLI and stdio MCP server today.
Steps
Prefer the CLI for short-lived one-shot runs.
Use MCP for longer sessions that support stdio server configuration.
Keep confirmation tokens tied to the target post id.
Portable MCP server entry
{
"mcpServers": {
"creagency": {
"command": "npx",
"args": ["-y", "-p", "@creagency/agent", "creagency-mcp"],
"env": {
"CREAGENCY_API_ORIGIN": "https://api.creagency.ai"
}
}
}
}Examples
NanoClaw prompts you can actually use.
One-shot draft
NanoClaw creates one draft and exits cleanly.
Prompt
Use Creagency to create one LinkedIn draft from this text. Return the post id and do not publish.Expected outcome
A single draft is created and the post id is returned.
Short-lived account check
The agent proves it can access the right workspace before creating content.
Prompt
Run Creagency auth and integrations checks. Stop if LinkedIn is not connected.Expected outcome
The run exits before content work if the requested channel is unavailable.
Media plus draft
NanoClaw uploads a file and uses it in a draft.
Prompt
Upload ./card.png with Creagency and create one Threads draft with that asset. Do not schedule.Expected outcome
A draft with media is created and left for review.
Audit-friendly publish prep
The run prepares publish and logs the target summary.
Prompt
Prepare post_123 for publishing. Print the post id, platform, account, and final copy, then stop.Expected outcome
The output is auditable and does not execute publish.
Safety
Keep the agent useful without handing over your channels.
Read connected accounts before creating or scheduling content.
Keep API keys in environment variables and never print them in chat.
Create drafts first when the user has not explicitly asked to schedule.
Prepare publish and delete actions before execution, then ask for confirmation.
Troubleshooting
When the first run does not work.
NanoClaw cannot see connected accounts.
Run creagency auth:status --json, then integrations:list --json. If the list is empty, connect social accounts in Creagency first.
A post command fails with a missing scope.
Create or rotate the API key with posts:read, posts:write, assets:read, assets:write, and integrations:read.
The agent tries to publish immediately.
Point it back to the skill rule: create or schedule a draft first unless the user explicitly confirms publish.
FAQ
What NanoClaw users usually ask first.
Can the agent publish without approval?
Creagency local MCP publish and delete flows are two-step. The agent prepares the action, shows the summary, and only executes after confirmation.
Is hosted remote MCP available now?
Not generally. The available path is the local CLI and stdio MCP package. Hosted remote MCP with OAuth is planned separately.
Does the agent need social account passwords?
No. Social channels connect through Creagency and platform OAuth. Agents use scoped Creagency API keys.
Set up NanoClaw with Creagency.
Install the skill, connect the CLI or local MCP server, and start with one draft that your team can review.