Token导航 LogoToken导航

Agent Skill · 开发

clawpost-2(爪柱 2)

clawpost-2 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

clawpost-2 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 2,106。

总安装 20,465周安装 836GitHub Stars 2下载 6,554核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.1.3

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:clawpost-2(爪柱 2)
来源仓库:https://github.com/acidias/clawpost-2
安装命令:
openclaw skills install clawpost-2
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install clawpost-2

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

基于 AI 的 LinkedIn 和 X (Twitter) 社交媒体发布,具有算法优化和调度功能。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install clawpost-2;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

clawpost-2 怎么安装?

在终端执行 openclaw skills install clawpost-2。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

clawpost-2 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

clawpost-2 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

clawpost-2 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

clawpost-2 用的人多吗?

公开数据是累计安装 20,465 次,近一周安装 836 次,下载 6,554 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

clawpost-2 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
clawpost-2

爪柱 2 · 本页

20,4652接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
clawpost
description
AI-powered social media publishing for LinkedIn and X (Twitter) with algorithm optimization and scheduling.
version
0.1.3
metadata
openclaw
emoji
📱
homepage
https://clawpost.dev
primaryEnv
CLAW_API_KEY
requires
env
bins

Social Media Publisher Skill

ClawPost helps you create, manage, and publish content to LinkedIn and X (Twitter) — with AI-assisted writing, drafts, scheduling, and direct publishing via API.

Getting Started

If the user doesn't have an account or API key yet, walk them through these steps:

  1. Sign up at clawpost.dev — sign in with LinkedIn.
  2. Connect platforms — In the Dashboard, connect LinkedIn and/or X (Twitter) accounts.
  3. Add credits — Go to Dashboard → Billing and top up credits (minimum $5). Credits are used for AI generation features.
  4. Generate an API key — Go to Dashboard → Settings → API Keys → Generate New Key. The key starts with claw_.
  5. Set the environment variable:
   export CLAW_API_KEY="claw_your_key_here"

Setup

Required environment variable:

  • CLAW_API_KEY — your API key (starts with claw_). Generate one following the steps above.

Optional:

  • CLAW_API_URL — defaults to https://clawpost.dev. Only set this if using a self-hosted instance.

All endpoints are under {{CLAW_API_URL}}/api/claw/v1/ (default: https://clawpost.dev/api/claw/v1/).

Authentication

Every request needs the header:

Authorization: Bearer {{CLAW_API_KEY}}

Important: Passing JSON in shell commands

When sending JSON data with curl, always use a heredoc to avoid shell escaping issues with quotes and special characters:

curl -s -X POST URL \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"key": "value"}
EOF

All examples below use this pattern. Do not use -d '{...}' with single quotes — it breaks when content contains quotes, newlines, or special characters.

Response Format

All responses follow this shape:

{
  "success": true,
  "message": "Human-readable summary",
  "data": { ... },
  "error": { "code": "ERROR_CODE", "details": "..." }
}

Always read the message field — it's designed to be relayed directly to the user.

Endpoints

Check Status

Verify your API key works and see what's connected.

curl -s {{CLAW_API_URL}}/api/claw/v1/status \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

List Connected Platforms

curl -s {{CLAW_API_URL}}/api/claw/v1/platforms \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

Check Credits

curl -s {{CLAW_API_URL}}/api/claw/v1/credits \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

List Posts

Filter by status (draft, published, scheduled, failed) and platform (linkedin, twitter).

curl -s "{{CLAW_API_URL}}/api/claw/v1/posts?status=draft&platform=linkedin&limit=10" \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

X Post History

Retrieve your X (Twitter) post history from the cached profile data. This is a read-only endpoint - no credits are used.

Query parameters:

  • type - posts, replies, or all (default: all)
  • limit - max results, 1-100 (default: 20)
  • period - 7d, 30d, 90d, or all (default: all)
curl -s "{{CLAW_API_URL}}/api/claw/v1/history/x?type=posts&period=30d&limit=10" \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

The response includes a summary object with aggregated metrics (totalPosts, totalReplies, totalLikes, totalRetweets, totalRepliesReceived, totalImpressions, topPost) and a posts array with individual tweet details, metrics, media, and reply context.

Get Single Post

curl -s {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

Each post includes an availableActions array (e.g., ["publish", "schedule", "update", "delete"]).

Post Object Fields

Every post includes a postType field:

  • "original" — a regular post composed by the user
  • "quote" — a quote tweet of another post (X only)
  • "reply" — a reply to another post (X only)
  • "remix" — an original tweet inspired by another post (X only)

When postType is "quote", "reply", or "remix", the post also includes a reference object with the original tweet's context:

{
  "postType": "quote",
  "content": "User's commentary text",
  "reference": {
    "tweetId": "1234567890",
    "text": "The original tweet text that was quoted",
    "author": "originalAuthor"
  }
}

This lets you see exactly what was quoted/replied to alongside the user's own text.

Create a Draft

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/drafts \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"content": "Your post text here", "platform": "linkedin"}
EOF

Platform: "linkedin" or "twitter". Twitter content must be ≤ 280 characters.

Update a Draft

curl -s -X PUT {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"content": "Updated post text"}
EOF

Delete a Draft

curl -s -X DELETE {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

Publish a Draft

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID/publish \
  -H "Authorization: Bearer {{CLAW_API_KEY}}"

Direct Publish (No Draft Step)

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/publish \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"content": "Publishing this directly!", "platform": "linkedin"}
EOF

Schedule a Draft

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID/schedule \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"scheduledAt": "2026-06-15T10:00:00Z"}
EOF

Direct Schedule (No Draft Step)

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/schedule \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"content": "Scheduled post!", "platform": "linkedin", "scheduledAt": "2026-06-15T10:00:00Z"}
EOF

AI Generate Post

Let AI write a post based on your prompt. Optional: tone and platform.

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/ai/generate \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"prompt": "Write about the importance of code reviews", "platform": "linkedin"}
EOF

AI Refine Post

Improve existing content with instructions.

curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/ai/refine \
  -H "Authorization: Bearer {{CLAW_API_KEY}}" \
  -H "Content-Type: application/json" \
  -d @- <<'EOF'
{"content": "Original post text...", "instructions": "Make it shorter and punchier", "platform": "linkedin"}
EOF

Workflow Tips

  1. Quick publish: Use /publish to post immediately without creating a draft.
  2. Review flow: Create a draft with /drafts, refine with /ai/refine, then publish with /posts/ID/publish.
  3. Cross-post: Make separate calls for LinkedIn and Twitter — each is a separate post.
  4. Check before publishing: Call /platforms to verify the target platform is connected.
  5. Twitter limit: Tweets must be ≤ 280 characters. The API will reject longer content with a clear message.

Error Codes

CodeMeaning
UNAUTHORIZEDInvalid or revoked API key
NOT_FOUNDPost or resource doesn't exist
VALIDATION_ERRORBad input (missing content, too long, invalid date)
CONFLICTCan't perform action (e.g., already published)
PLATFORM_NOT_CONNECTEDTarget social platform isn't linked
INSUFFICIENT_CREDITSNot enough credits for AI operations
NO_AI_KEYNo AI API key configured
RATE_LIMITEDToo many requests (60/min general, 10/min publish)
INTERNAL_ERRORSomething went wrong server-side

平台分布

OpenClaw

80.02%
按下载量换算5,245

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills