Token导航 LogoToken导航TokenDH.com
开发敏感数据clawhub未标认证来源可访问clear审计通过

clawpost-2爪柱 2

Agent Skill

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

总安装

20,465

周安装

836

GitHub Stars

2

下载量

6,554
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

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

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

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

80.02%
按下载量换算5,245

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

敏感数据

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

安装前确认

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

来源信息

继续浏览同类 Skills