← 返回
内容创作 Key 中文

SpeakNotes: YouTube, Audio & Document Summaries

Use when OpenClaw needs to call SpeakNotes API routes directly using an API key and generate transcripts/summaries from YouTube URLs, media files, or documen...
当 OpenClaw 需要使用 API 密钥直接调用 SpeakNotes API,从 YouTube 链接、媒体文件或文档生成转录或摘要时使用。
jacklillie
内容创作 clawhub v1.0.1 1 版本 100000 Key: 需要
★ 0
Stars
📥 497
下载
💾 22
安装
1
版本
#ai-notes#ai-skill#ai-summary#api#api-integration#async-processing#audio-transcription#audio-upload#automation#clawhub#developer-tools#document-processing#document-summary#docx-summary#file-upload#folders-api#knowledge-management#latest#lecture-notes#meeting-notes#note-taking#notes-api#openapi#openapi-3-1#openclaw#pdf-summary#podcast-notes#productivity#skill#speaknotes#speech-to-text#status-polling#summarization#summarize#text-summary#transcribe#transcript#transcription#transcripts#video-transcription#video-upload#youtube#youtube-summary#youtube-transcript

概述

SpeakNotes OpenClaw Skill

This skill gives OpenClaw a production-ready contract for SpeakNotes direct API usage.

When To Use

  • The user wants OpenClaw to transcribe or summarize content via SpeakNotes API.
  • Input is one of:
  • YouTube URL
  • Audio/video file
  • Document file (pdf, docx, txt, etc.)
  • The user needs note status polling, note retrieval, or folder retrieval.

Prerequisites

  1. A SpeakNotes API key from /settings/api-keys.
  2. Store it as SPEAKNOTES_API_KEY in your OpenClaw skill config/secret manager.
  3. API host allowlist: use only https://api.speaknotes.io.
  4. Send auth in Authorization header:
    • Preferred: Bearer
    • Also accepted: raw token value
  5. Never send API keys to any unverified or user-provided host.

OpenClaw config example:

{
  "skills": {
    "entries": {
      "speaknotes-openclaw": {
        "apiKey": "YOUR_SPEAKNOTES_API_KEY",
        "env": {
          "SPEAKNOTES_API_KEY": "YOUR_SPEAKNOTES_API_KEY"
        }
      }
    }
  }
}

Setup Phase (If API Key Is Missing)

Run this setup phase before any processing flow when the user has not saved an API key yet.

  1. Send the user to /pricing/pro to start or upgrade to a Pro plan if needed.
  2. Send the user to /settings/api-keys to generate and save a SpeakNotes API key.
  3. Save that key as SPEAKNOTES_API_KEY in OpenClaw skill secrets/config.
  4. Only continue with API calls after the key is available.

Implementation Rules

  1. Never print or log API keys.
  2. Always use HTTPS and only the official API host: https://api.speaknotes.io.
  3. For upload flows, always:
    • request signed URL
    • PUT bytes to signed URL
    • call complete endpoint
    • poll note status endpoint
  4. Preserve file MIME type for media uploads.
  5. Use sharedFolderId only when the caller has access.
  6. Return noteId in all create/schedule responses.

Processing Flows

YouTube

  1. POST /youtube-check
  2. If valid, POST /youtube-summary
  3. Poll GET /api/v1/notes/{id}/status until isComplete or hasError

Audio/Video File

  1. POST /upload-url
  2. PUT file bytes to returned uploadUrl
  3. POST /upload-complete
  4. Poll GET /api/v1/notes/{id}/status

Document File

  1. POST /pdf-upload-url
  2. PUT file bytes to returned uploadUrl with returned contentType
  3. POST /pdf-upload-complete
  4. Poll GET /api/v1/notes/{id}/status

OpenAPI Specification

_Generated by skills/speaknotes-openclaw/scripts/generate-openapi-spec.mjs._

Use ./openapi.json as the authoritative OpenAPI 3.1 contract for this skill.

  • Includes YouTube validation/summarization, upload flows, note status, and folder endpoints.
  • Keep this file and openapi.json in the same folder when publishing.

Output Format For Agents

For each task response:

  1. action: short description of operation performed
  2. endpoints_used: list of routes called
  3. noteId: included for create flows
  4. status: current processing status (Summarizing, Done, Error, etc.)
  5. result: concise payload summary (title, snippet, or link-ready fields)
  6. next_step: polling guidance or retry recommendation

Retry Policy

  • 403: tell user to verify/regenerate API key.
  • 429: wait Retry-After (if provided) and retry once.
  • 5xx: retry once with exponential backoff; then return actionable failure.
  • Signed URL upload failures: request a fresh upload URL and retry from step 1.

版本历史

共 1 个版本

  • v1.0.1 当前
    2026-03-30 13:12 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

content-creation

AdMapix

fly0pants
广告情报与应用数据分析助手,支持搜索广告素材、分析应用排名、下载量、收入及市场洞察,用于广告素材和竞品分析。
★ 295 📥 136,434
content-creation

YouTube

byungkyu
使用托管OAuth集成YouTube Data API,支持搜索视频、管理播放列表、获取频道数据及评论互动,适用于用户需要时使用此技能。
★ 142 📥 41,033
content-creation

Humanizer

biostartechnology
消除AI写作痕迹,使文本更自然真实。基于维基百科"AI写作特征"指南,识别并修正夸张象征、宣传用语、肤浅-ing分析、模糊归因、破折号滥用、三项排比、AI词汇、负面平行结构及冗长连接词等模式。
★ 857 📥 199,438