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

twitter-poster推特海报

Agent Skill

twitter-poster 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

751

周安装

31

GitHub Stars

公开资料未说明

下载量

246
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:twitter-poster(推特海报)
来源仓库:https://github.com/rkreddyp/investrecipes
仓库路径:skills/twitter-poster
安装命令:
npx skills add rkreddyp/investrecipes --skill "twitter-poster"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

AgentSkills.tonpx skills
npx skills add rkreddyp/investrecipes --skill "twitter-poster"

简介

twitter-poster 支持生成并发布 Twitter 海报内容,适用于营销与品牌推广。

  • 能结合文本与视觉元素输出适合社交平台传播的材料。
  • 通过 npx skills add rkreddyp/investrecipes --skill "twitter-poster" 命令安装。
  • 需确认宿主是否支持图像生成或外部图床调用,注意版权与格式规范。
  • 建议参考 README 了解模板变量替换与发布时间调度功能。

SKILL.md

Twitter Poster Skill

This skill posts business news, reports, and insights to Twitter/X with intelligent formatting, thread support, and media attachment capabilities.

Purpose

  • Post insightful, educational, and intuitive business news digests and market analysis reports to Twitter
  • Create threaded tweets for longer content to improve readability and engagement
  • Provide clear, understandable context so users immediately grasp what the post is about
  • Attach images, screenshots, or media files to enhance understanding
  • Format content for optimal Twitter engagement while maintaining educational value
  • Schedule or post tweets programmatically

Content Quality Standards

CRITICAL: All Twitter posts must be:

1. Insightful

  • Go beyond simple summaries - provide analysis and context
  • Connect dots between multiple news items to reveal patterns
  • Explain WHY something matters, not just WHAT happened
  • Offer actionable insights or implications
  • Highlight trends and underlying forces

2. Educational

  • Teach concepts, explain market dynamics, or clarify complex topics
  • Use clear, accessible language (avoid jargon without explanation)
  • Provide context and background when needed
  • Break down complex topics into digestible parts
  • Help readers understand the significance of news

3. Intuitive

  • Make it immediately clear what the post is about in the first tweet
  • Use clear structure and formatting
  • Include context clues (dates, sources, categories)
  • Use emojis strategically to aid quick scanning
  • Ensure each tweet in a thread can stand alone while contributing to the whole

4. Thread-First Approach

  • ALWAYS prefer threads for content longer than a single tweet
  • Use threads to organize complex information logically
  • Break insights into digestible chunks (one idea per tweet)
  • Number threads clearly (1/5, 2/5, etc.)
  • Make the first tweet a compelling hook that encourages reading the thread

Key Features

1. Thread Support (PREFERRED METHOD)

  • Always use threads for content that requires explanation or context
  • Break long content into Twitter threads (280 characters per tweet)
  • Automatically number thread tweets (1/5, 2/5, etc.)
  • Maintain context across thread tweets
  • Structure threads logically: hook → context → insights → implications
  • Each tweet should be self-contained but contribute to the narrative

2. Insightful Content Creation

  • Synthesize multiple news sources to identify patterns
  • Explain the "why" behind market movements and trends
  • Connect related stories to show bigger picture
  • Provide actionable insights or implications
  • Highlight what matters most and why

3. Educational Formatting

  • Start threads with clear, intuitive hooks that explain what's coming
  • Use clear structure: Context → Analysis → Implications
  • Break down complex topics step-by-step
  • Use formatting (emojis, line breaks) to aid readability
  • Include source attribution for credibility

4. Media Attachments

  • Attach images (screenshots, charts, graphs) to enhance understanding
  • Support for PNG, JPG formats
  • Automatic image optimization for Twitter
  • Use images to illustrate complex concepts or data

5. Rate Limit Handling

  • Respect Twitter API rate limits
  • Queue tweets when needed
  • Handle errors gracefully

Authentication

Twitter API v2 credentials (examples shown below, replace API/Bearer keys if needed):

  • API Key (Consumer Key): KiEaJHzFUWE7BLPMrMeABVx8z
  • API Secret (Consumer Secret): GSvXTcUGpA37xZ5pKOu2aMitplfM0icbrlnVnwbZNVIJVaNQbT
  • Access Token: 1088426905634779136-fKvck5gh92Z5nrirFvkYlfM3ftyZ43
  • Access Token Secret: Rsf3g4rpADKm6U42QbIxjI82kAt2kUVbDFBrCS1ELTmU8
  • Bearer Token: AAAAAAAAAAAAAAAAAAAAALL3wQEAAAAAEU16sJsJT9zl7D0w6iGMky%2FXn5I%3D3bCPWBSMOyKAlF7LfbRTCbIlt8goxzq2lZlEC6jfcdZNzPU7Jv OAUTH2_CLIENT_SECRET_V2 = "nsWvS3dCCitBpMihAMlr2nMJBy7J-7Xw8tx7Zq_xf2WWiz8r0_"

Example for using OAuth 2.0 Client Secret in Twitter API setup

WARNING: Store this secret securely, do NOT commit to public code.

OAUTH2_CLIENT_SECRET = "nsWsS3dCCtiBpMiAhIi2nMJbYJ7-7XwBxfZq_xf2WWiz8r0_"

Best Practices

Content Quality

  1. Be Insightful: Don't just summarize - explain WHY it matters, connect patterns, provide context
  2. Be Educational: Teach concepts, explain market dynamics, clarify complex topics
  3. Be Intuitive: Make it immediately clear what the post is about in the first tweet
  4. Use Threads: Prefer threads over single tweets for better organization and readability

Thread Structure

  1. First Tweet (Hook): Clear, compelling overview that explains what the thread covers
  2. Context Tweets: Provide background and context needed to understand insights
  3. Insight Tweets: Break down key insights one per tweet for clarity
  4. Final Tweet: Synthesize takeaways or actionable implications

Technical Guidelines

  1. Character Limits: Keep individual tweets under 280 characters
  2. Thread Length: Use threads for content requiring explanation (max 25 tweets per thread)
  3. Rate Limits: Respect Twitter's rate limits (300 tweets per 3 hours)
  4. Media: Optimize images (max 5MB, recommended 1200x675px) to enhance understanding
  5. Hashtags: Use 1-3 relevant hashtags per thread (not every tweet)
  6. Mentions: Tag relevant accounts when appropriate, but don't overdo it
  7. Error Handling: Always handle API errors gracefully
  8. Testing: Test with a test account before production use

Content Guidelines

  • Clarity First: If content needs explanation, use a thread
  • One Idea Per Tweet: Each tweet in a thread should focus on one concept
  • Progressive Disclosure: Start broad, then dive deeper in subsequent tweets
  • Source Attribution: Always cite sources for credibility
  • Visual Aids: Use emojis strategically to aid quick scanning (📊 for data, 🧵 for threads, etc.)

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Claude Code

29.66%
按下载量换算73

Codex

24.3%
按下载量换算60

Antigravity

18.08%
按下载量换算44

Gemini CLI

11.05%
按下载量换算27

windsurf

7.34%
按下载量换算18

OpenCode

3.48%
按下载量换算9

安全审计

暂无安全审计结果可展示。

权限和风险

敏感数据

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

安装前确认

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

来源信息

继续浏览同类 Skills