Token导航 LogoToken导航

Agent Skill · 效率

dopost(dopost 效率)

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

dopost 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 14,617。

总安装 3,340周安装 142GitHub Stars 1下载 1,170核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install dopost

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

用于补充效率相关能力,适合在 OpenClaw 中承接效率任务。可调用 Dopost REST API 发布和管理社交媒体帖子。通过编程方式实现内容排期、发布和平台管理自动化。安装前建议确认权限范围、维护状态及是否触发文件读写。涉及外部工具时应明确步骤边界和失败处理机制。

dopost 属于效率类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

dopost 怎么安装?

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

dopost 支持哪些 AI 工具?

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

dopost 需要什么权限?

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

dopost 是免费的吗?

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

dopost 用的人多吗?

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

dopost 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
dopost

dopost 效率 · 本页

3,3401接触敏感数据MIT-0通过

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

SKILL.md 原文

name
dopost-api
description
Use the Dopost REST API to publish, schedule, and manage social media posts programmatically. Use this skill when the user wants to publish to social media, schedule posts, manage media uploads, check post status, list connected accounts, or interact with any Dopost API endpoint. Also activate when the user mentions dopost, the Dopost API, social media automation, or publishing via API key.
metadata
openclaw
version
1.1.0
homepage
https://dopost.co/docs/api
requires
env
primaryEnv
DOPOST_API_KEY

Dopost API

Dopost is a social media management platform. Its REST API lets you publish and schedule posts, manage media, and inspect connected social accounts.

Base URL: https://dopost.co/api/v1 Auth: All requests require the header x-api-key: <your-key> Full docs: https://dopost.co/docs/api


Setup

Always check for an .env or .env.local file with DOPOST_API_KEY. If not present, ask the user for their key before proceeding.

export DOPOST_API_KEY="dpk_live_..."

Endpoints

Social Accounts

List connected accounts
GET /api/v1/social/accounts
Scope: social:accounts
curl -H "x-api-key: $DOPOST_API_KEY" https://dopost.co/api/v1/social/accounts

Returns { accounts: [{ id, platform, platformUsername, platformUserId }] }. The id field is the accountId needed for publishing.

Get platform limits
GET /api/v1/social/limits/:platform
Scope: social:limits

Platforms: x, instagram, instagram_direct, facebook, linkedin, linkedin_organization, tiktok, youtube, threads, bluesky, mastodon, pinterest

instagram = connected via Meta Business (Facebook Page linked). instagram_direct = connected directly via Instagram OAuth. linkedin = personal profile. linkedin_organization = company page.
curl -H "x-api-key: $DOPOST_API_KEY" https://dopost.co/api/v1/social/limits/instagram

Posts

Publish or schedule a post
POST /api/v1/post/publish
Scope: posts:create
{
  "accountId": "<accountId>",
  "text": "Post content",
  "media": ["https://..."],
  "publishAt": "2025-12-25T12:00:00Z",
  "platformOptions": {}
}
  • At least text or media is required
  • media can be an array of URL strings or objects { url: "..." }
  • Maximum 10 media items per post
  • Omit publishAt (or set to null) to publish immediately
  • Returns 202 with { success, jobId, postId, status }
  • Publishing is asynchronous — poll GET /api/v1/post/:postId to check status
Platform-specific options (platformOptions)

Instagram

FieldValuesDefault
postType"feed" \"story" \"reel""feed" (auto "carousel" with multiple media)

TikTok

FieldValuesDefault
privacyLevel"PUBLIC_TO_EVERYONE" \"MUTUAL_FOLLOW_FRIENDS" \"FOLLOWER_OF_CREATOR" \"SELF_ONLY""PUBLIC_TO_EVERYONE"
disableDuetbooleanfalse
disableStitchbooleanfalse
disableCommentbooleanfalse

YouTube

FieldValuesDefault
videoType"video" \"short""video"
titlestringFirst 100 chars of text
privacyStatus"public" \"private" \"unlisted""public"

Pinterest

FieldDescription
boardBoard ID (required for Pinterest)
Get a post
GET /api/v1/post/:postId
Scope: posts:read

Returns the full post object including publish status:

{
  "id": "cm3abc123def456",
  "status": "PUBLISHED",
  "platform": "INSTAGRAM",
  "text": "Post content",
  "media": [],
  "postUrl": "https://instagram.com/p/...",
  "account": {
    "id": "cm3xyz789ghi012",
    "platform": "INSTAGRAM",
    "platformUsername": "myaccount"
  },
  "schedule": {
    "scheduledFor": "2026-04-13T09:00:00.000Z",
    "status": "PUBLISHED",
    "publishedAt": "2026-04-13T09:00:05.000Z"
  },
  "jobId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "source": "api",
  "createdAt": "2026-04-07T10:00:00.000Z",
  "updatedAt": "2026-04-07T10:32:18.000Z"
}

schedule is null for immediate posts. postUrl is null until published. Use this endpoint to poll status after publishing.

List posts
GET /api/v1/post?status=PENDING&limit=20&cursor=<cursor>
Scope: posts:read

Status filter values: DRAFT, PENDING, PUBLISHED, FAILED

Reschedule a post
PATCH /api/v1/post/:postId
Scope: posts:reschedule
Body: { "publishAt": "2025-12-31T09:00:00Z" }

Only works on posts with status PENDING. The new date must be in the future. Returns { id, scheduledFor }.

Delete a post
DELETE /api/v1/post/delete/:postId
Scope: posts:delete

Cancels scheduling automatically if the post is PENDING. Returns { success: true, deletedPostId: "..." }.


Media

Upload media (presigned URL flow)
POST /api/v1/media
Scope: media:upload
Body: { "fileName": "photo.jpg", "contentType": "image/jpeg", "sizeInBytes": 204800 }

Returns 201 with:

{
  "id": "cm3media001xyz",
  "uploadUrl": "https://storage.example.com/...?X-Amz-Signature=...",
  "publicUrl": "https://cdn.dopost.co/media/.../photo.jpg",
  "fileName": "photo.jpg",
  "contentType": "image/jpeg",
  "expiresIn": 3600
}
  • uploadUrl is a temporary presigned URL — upload the file with a PUT request within expiresIn seconds
  • publicUrl is the permanent URL — use this as the media URL when publishing
  • Maximum file size: 1 GB
curl -X PUT -H "Content-Type: image/jpeg" --data-binary @photo.jpg "$UPLOAD_URL"
List media
GET /api/v1/media?limit=20&cursor=<cursor>
Scope: media:list
Delete media
DELETE /api/v1/media/:mediaId
Scope: media:delete

Returns { message: "Media deleted", mediaId: "..." }.


Common workflows

Publish a post now

  1. GET /api/v1/social/accounts — pick accountId
  2. POST /api/v1/post/publish with accountId + text
  3. GET /api/v1/post/:postId — poll until status is PUBLISHED or FAILED

Publish a post with an image

  1. POST /api/v1/media — get uploadUrl + publicUrl
  2. PUT the file to uploadUrl
  3. POST /api/v1/post/publish with media: [publicUrl]
  4. GET /api/v1/post/:postId — poll until published

Schedule and reschedule

  1. Publish with a future publishAt
  2. To change the date: PATCH /api/v1/post/:postId with new publishAt
  3. To cancel: DELETE /api/v1/post/delete/:postId

Error handling

StatusMeaning
400Bad request — check the request body
401Invalid or missing x-api-key
403API key lacks the required scope
404Resource not found or inactive account
429Rate limit or monthly quota exceeded. Check X-RateLimit-* headers

On 429, respect the Retry-After header before retrying.


Examples

1. List connected accounts

Request

curl -H "x-api-key: $DOPOST_API_KEY" \
  https://dopost.co/api/v1/social/accounts

Response 200 OK

{
  "accounts": [
    {
      "id": "cm3xyz789ghi012",
      "platform": "INSTAGRAM",
      "platformUsername": "myaccount",
      "platformUserId": "17841400000000001"
    },
    {
      "id": "cm3abc456def789",
      "platform": "LINKEDIN",
      "platformUsername": "johndoe",
      "platformUserId": "urn:li:person:a1B2c3D4e5"
    }
  ]
}

2. Publish a text post immediately

Request

curl -X POST \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "cm3xyz789ghi012",
    "text": "Hello from the Dopost API!"
  }' \
  https://dopost.co/api/v1/post/publish

Response 202 Accepted

{
  "success": true,
  "jobId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "postId": "cm3abc123def456",
  "status": "processing"
}

3. Check post status

Request

curl -H "x-api-key: $DOPOST_API_KEY" \
  https://dopost.co/api/v1/post/cm3abc123def456

Response — published

{
  "id": "cm3abc123def456",
  "status": "PUBLISHED",
  "platform": "INSTAGRAM",
  "text": "Hello from the Dopost API!",
  "media": [],
  "postUrl": "https://www.instagram.com/p/ABC123/",
  "account": {
    "id": "cm3xyz789ghi012",
    "platform": "INSTAGRAM",
    "platformUsername": "myaccount"
  },
  "schedule": null,
  "jobId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "source": "api",
  "createdAt": "2026-04-07T10:00:00.000Z",
  "updatedAt": "2026-04-07T10:32:18.000Z"
}

Response — failed

{
  "id": "cm3abc123def456",
  "status": "FAILED",
  "platform": "INSTAGRAM",
  "text": "Hello from the Dopost API!",
  "media": [],
  "postUrl": null,
  "account": {
    "id": "cm3xyz789ghi012",
    "platform": "INSTAGRAM",
    "platformUsername": "myaccount"
  },
  "schedule": null,
  "jobId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "source": "api",
  "createdAt": "2026-04-07T10:00:00.000Z",
  "updatedAt": "2026-04-07T10:05:00.000Z"
}

4. Publish an Instagram Reel

Request

curl -X POST \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "cm3xyz789ghi012",
    "text": "New reel! #content",
    "media": ["https://cdn.example.com/video.mp4"],
    "platformOptions": {
      "postType": "reel"
    }
  }' \
  https://dopost.co/api/v1/post/publish

Response 202 Accepted

{
  "success": true,
  "jobId": "a1b2c3d4-0000-4abc-8def-111122223333",
  "postId": "cm3reel001xyz",
  "status": "processing"
}

5. Schedule a post

Request

curl -X POST \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "cm3abc456def789",
    "text": "Scheduled post for next Monday!",
    "publishAt": "2026-04-13T09:00:00Z"
  }' \
  https://dopost.co/api/v1/post/publish

Response 202 Accepted

{
  "success": true,
  "jobId": "b2c3d4e5-1111-4bcd-9ef0-222233334444",
  "postId": "cm3sched001abc",
  "status": "scheduled"
}

6. Upload media and publish with it

Step 1 — Request presigned URL

curl -X POST \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fileName": "photo.jpg",
    "contentType": "image/jpeg",
    "sizeInBytes": 204800
  }' \
  https://dopost.co/api/v1/media

Response 201 Created

{
  "id": "cm3media001xyz",
  "uploadUrl": "https://storage.example.com/uploads/photo.jpg?X-Amz-Signature=...",
  "publicUrl": "https://cdn.dopost.co/media/cm3media001xyz/photo.jpg",
  "fileName": "photo.jpg",
  "contentType": "image/jpeg",
  "expiresIn": 3600
}

Step 2 — Upload the file

curl -X PUT \
  -H "Content-Type: image/jpeg" \
  --data-binary @photo.jpg \
  "https://storage.example.com/uploads/photo.jpg?X-Amz-Signature=..."

Returns 200 with empty body on success.

Step 3 — Publish using the public URL

curl -X POST \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "cm3xyz789ghi012",
    "text": "Check out this photo!",
    "media": ["https://cdn.dopost.co/media/cm3media001xyz/photo.jpg"]
  }' \
  https://dopost.co/api/v1/post/publish

7. Reschedule a pending post

Request

curl -X PATCH \
  -H "x-api-key: $DOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "publishAt": "2026-04-20T14:00:00Z" }' \
  https://dopost.co/api/v1/post/cm3sched001abc

Response 200 OK

{
  "id": "cm3sched001abc",
  "scheduledFor": "2026-04-20T14:00:00.000Z"
}

8. List posts with filter

Request

curl -H "x-api-key: $DOPOST_API_KEY" \
  "https://dopost.co/api/v1/post?status=PUBLISHED&limit=5"

Response 200 OK

{
  "posts": [
    {
      "id": "cm3abc123def456",
      "status": "PUBLISHED",
      "text": "Hello from the Dopost API!",
      "publishedAt": "2026-04-07T10:32:18.000Z",
      "account": {
        "id": "cm3xyz789ghi012",
        "platform": "INSTAGRAM",
        "platformUsername": "myaccount"
      }
    }
  ],
  "nextCursor": null,
  "hasMore": false
}

9. Delete a post

Request

curl -X DELETE \
  -H "x-api-key: $DOPOST_API_KEY" \
  https://dopost.co/api/v1/post/delete/cm3sched001abc

Response 200 OK

{
  "success": true,
  "deletedPostId": "cm3sched001abc"
}

MCP server (optional)

If the user has the Dopost MCP server configured, prefer using MCP tools (publish_post, list_accounts, etc.) over raw HTTP calls — they handle auth and path safety automatically.

MCP setup: https://dopost.co/docs/api

平台分布

OpenClaw

87.41%
按下载量换算1,023

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

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

安装前确认

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

继续浏览同类 Skills