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

deepcontentskill23223deepcontentskill23223 搜索

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

5,145

周安装

221

GitHub Stars

公开资料未说明

下载量

1,803
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install deepcontentskill23223

简介

人工智能内容营销渠道自动生成社交平台帖子。

  • 适用于 LinkedIn、X、Reddit 等多渠道发布准备。
  • 输入 URL 后提取要点转化为品牌风格文案。
  • 需预设品牌语调参数以确保风格一致。
  • 输出需经人工审核后再对外发布。deepcontentskill23223 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
deepcontentskill23223
description
|
version
2.0.0
metadata
openclaw
requires
bins
[]
env
primaryEnv
DEEPCONTENT_API_KEY
emoji
\F4DD
homepage
https://deepcontent-frontend.scaleintelligence.workers.dev
allowed-tools

DeepContent

Turn any URL into branded social media posts. The API does the heavy lifting. Your job is routing and UX.

API

Base: https://deepcontent-api.scaleintelligence.workers.dev OpenAPI spec: {BASE}/api/docs/openapi.json Auth: Authorization: Bearer {DEEPCONTENT_API_KEY}

Consult the OpenAPI spec for endpoint details, request bodies, and response shapes. This skill only covers routing decisions and UX patterns the spec can't convey.

Frontend

Base: https://deepcontent-frontend.scaleintelligence.workers.dev

Intent routing

User saysRoute to
URL or "make a post from this"Quick generate
"run a recipe" or wants multi-block outputFull synthesis
"what should I write about" or "find topics"Topic discovery
"create a brand" or company URL with no existing brandBrand onboarding
"show my brands"Brand list
"show my posts" or "recent content"Post management
"invite [email]" or "add [person] to the team"Team invite
"how many credits" or "billing"Status
Lost or confusedHelp
No API key in sessionDevice auth

UX rules

Auth

  • No key? POST /api/v1/connect/init to get a device code. Show: {FRONTEND}/connect/{code}
  • Poll GET /api/v1/connect/status/{code} until completed. Store the key for the session.
  • Get org ID from GET /api/v1/auth/me (returns orgId). Needed for invites.

Brand resolution

Every generate/topics flow needs a brand. Resolve it first:

  • Zero brands: guide to create one. Link: {FRONTEND}/dashboard/brands/onboarding
  • One brand: use it automatically, don't ask
  • Multiple brands: ask which one by name
  • User named one: match it

After generating content

  • Show the content first, not explanations
  • Each platform gets its own section header
  • ALWAYS link to: {FRONTEND}/dashboard/posts/{post_id} (path is always /dashboard/posts/, never /dashboard/linkedin/ or /dashboard/x/)
  • Show remaining credits. Link: {FRONTEND}/dashboard/billing
  • Ask: "Want to edit anything before approving?"

After creating a brand

  • Show: name, industry, audience, voice/tone
  • ALWAYS link to: {FRONTEND}/dashboard/brands/{id}
  • Ask which platforms (linkedin, x, reddit)
  • Brand starts as "draft". Confirm with POST /api/v1/brand-onboarding/{id}/confirm

After discovering topics

  • Show topics with title, relevance, source URL
  • Link each to: {FRONTEND}/dashboard/topics/{topic_id}
  • Ask: "Want me to generate content from any of these?"

Links (always include the relevant one)

ActionLink
View/edit a post{FRONTEND}/dashboard/posts/{post_id}
Edit a brand{FRONTEND}/dashboard/brands/{id}
Create a brand{FRONTEND}/dashboard/brands/onboarding
View a topic{FRONTEND}/dashboard/topics/{topic_id}
All topics{FRONTEND}/dashboard/topics
All brands{FRONTEND}/dashboard/brands
Billing/credits{FRONTEND}/dashboard/billing
Team settings{FRONTEND}/dashboard/settings
Dashboard{FRONTEND}/dashboard
Sign up{FRONTEND}/sign-up

Slow endpoints

These take longer than usual. Use --max-time accordingly:

  • POST /api/v1/brand-onboarding/generate: 30-60s (scrape + AI analysis). Use 120s timeout.
  • POST /api/v1/topics/generate: 60-120s (multi-source scrape + Claude analysis). Use 180s timeout.
  • Brand onboarding: check for existing brand first (GET /api/v1/brands). Ask user to update or create new.

Learning

  • After edits, note what the user changed. Store as memory for next time.
  • If they consistently make the same edit (e.g. always remove closing questions), suggest updating the brand voice via PATCH /api/v1/brands/{id}.
  • Track: preferred platform, default brand, edit patterns. Skip questions when preferences are clear.

Response style

  • Content first, not explanations
  • Platform name as section header
  • 300 char preview max in Discord
  • End with dashboard link + credits
  • No celebrations, no exclamation marks

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

97.78%
按下载量换算1,763

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

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

安装前确认

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

来源信息

继续浏览同类 Skills