什么是 LinkedIn 发布器？

LinkedIn 发布器是为 Openclaw Skills 生态系统设计的强大集成工具，旨在简化专业的社交媒体管理。它允许用户直接通过其 AI 智能体或命令行界面向其专业网络广播更新。通过使用安全的 OAuth 2.0 身份验证，它消除了手动登录的需要，为保持活跃的 LinkedIn 存在提供了一种流线化的方式。

该技能对于希望将社交分享集成到自动化工作流中的开发人员和营销人员特别有价值。无论您是通过 WhatsApp 从移动设备发布快速更新，还是从 CI/CD 流水线触发公司公告，Openclaw Skills 库中的这一补充都能确保一致且专业的沟通。

下载入口:https://github.com/openclaw/skills/tree/main/skills/krnbwj/openclawlinkedinposterskill

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

LinkedIn 发布器 应用场景

• 直接从开发环境自动分享项目里程碑或产品发布。
• 使用模糊名称匹配向管理的 LinkedIn 主页发布公司范围内的公告。
• 通过 WhatsApp 等文本触发方式分享专业见解或技术文章。
• 通过 AI 智能体工作流安排更新，维持一致的个人品牌。

1. 触发：用户使用自然语言模式（如“发布到 LinkedIn”）或通过直接的 CLI 执行来启动流程。
2. 授权：在初次运行时，该技能会打开浏览器窗口进行 OAuth 2.0 授权，请求个人资料和组织分享的权限。
3. 令牌存储：授权后，安全的访问令牌将存储在本地，有效期为 60 天，以便随后进行无摩擦的发布。
4. 上下文解析：该技能确定更新是针对个人资料还是公司主页，必要时执行组织匹配的模糊搜索。
5. API 发送：消息被发送到 LinkedIn 的社交元数据 API，技能向用户返回确认状态。

LinkedIn 发布器 配置指南

1. 创建应用：在 LinkedIn 开发者门户创建 LinkedIn 应用程序，并将 https://linkedin-oauth-server-production.up.railway.app/callback 添加为有效的重定向 URL。
2. 权限：确保应用程序具有访问“在 LinkedIn 上分享”和“使用 LinkedIn 登录”产品的权限。
3. 配置：将您的凭据添加到 openclaw.json 文件中：

{
  "plugins": {
    "env": {
      "LINKEDIN_CLIENT_ID": "您的客户端 ID",
      "LINKEDIN_CLIENT_SECRET": "您的客户端密钥"
}
  }
}

4. 初始化：运行以下命令并按照浏览器提示授权 Openclaw Skills：

node skills/linkedin-poster/runner.cjs "初始授权发布"

LinkedIn 发布器 数据架构与分类体系

该技能管理环境配置和本地令牌持久化，以确保在 Openclaw Skills 框架内的持续运行。

name: linkedin-poster
description: Post updates to the user's LinkedIn profile via OAuth.
metadata:
  openclaw:
    skillKey: linkedin-poster
    requires:
      env:
        - LINKEDIN_CLIENT_ID
        - LINKEDIN_CLIENT_SECRET
    invocation:
      policy: on-demand
      triggers:
        - pattern: "post to linkedin"
        - pattern: "share on linkedin"
        - pattern: "linkedin post"
        - pattern: "post to linkedin org"
        - pattern: "linkedin company post"

LinkedIn Poster

Post text updates to your LinkedIn profile directly from OpenClaw.

Features

• OAuth 2.0 authentication (one-time setup)
• Automatic token management (60-day expiry)
• Works via command line or WhatsApp
• Production-ready callback server

Setup

1. LinkedIn App Configuration

1. Create a LinkedIn app at LinkedIn Developers
2. Add redirect URL: https://linkedin-oauth-server-production.up.railway.app/callback
3. Request access to "Share on LinkedIn" and "Sign In with LinkedIn" products
4. Copy your Client ID and Client Secret

2. Environment Variables

Add to your openclaw.json:

{
  "plugins": {
    "env": {
      "LINKEDIN_CLIENT_ID": "your_client_id",
      "LINKEDIN_CLIENT_SECRET": "your_client_secret"
    }
  }
}

3. First Run Authorization

The first time you use the skill, it will:

1. Open a browser for LinkedIn authorization
2. Save the access token locally
3. Use the saved token for future posts

Usage

Via WhatsApp

Send a message to OpenClaw:

post to linkedin: Just shipped a new feature! ??

Or:

share on linkedin: Excited to announce our new product launch!

Via Command Line

node skills/linkedin-poster/runner.cjs "Your message here"

Posting to a Company Page

To post to a LinkedIn Company Page where you are an admin:

node skills/linkedin-poster/runner.cjs "Company update!" --org "My Company Name"

The skill will fuzzy search your administered organizations and post to the best match.

Note: You must have the w_organization_social permission (Marketing API/Company Page Management) enabled in your LinkedIn App settings for this to work.

How It Works

1. First use: Opens browser → Authorize → Token saved
2. Subsequent uses: Uses saved token → Posts immediately
3. Token expiry: Auto-prompts for re-authorization after 60 days

OAuth Callback Server

This skill uses a hosted callback server at: https://linkedin-oauth-server-production.up.railway.app

The server handles OAuth callbacks securely and works for anyone using the skill.

Troubleshooting

"redirect_uri does not match"

Ensure https://linkedin-oauth-server-production.up.railway.app/callback is added to your LinkedIn app's Redirect URLs.

"Authorization timeout"

The skill waits 60 seconds. Try again and authorize faster.

"Token expired"

Run the skill again - it will automatically start a new OAuth flow.