Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

twitter-x-gtm推特 x GTM

Agent Skill

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

总安装

220

周安装

9

GitHub Stars

3

下载量

71
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/phy041/claude-skill-twitter --skill twitter-x-gtm

简介

twitter-x-gtm 用于通过 Google Tag Manager 监控推特活动,适合在 Codex、Claude、Cursor、Gemini CLI 中集成分析工具。

  • 适用于需要追踪推文曝光、互动数据或用户行为的场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 了解具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网或脚本执行操作。
  • 当前无原始 SKILL.md 内容可参考,建议进一步查阅来源仓库获取详细功能说明。

SKILL.md

Twitter/X GTM Strategy for Founders

Founder-led personal brand strategy with blunt, sharp, authentic voice. Customize the brand voice section to match your own positioning.


Content Creation Workflow (Must Follow)

Every time creating Twitter/X content, follow this workflow:

Step 1: Research Hot Content

Required Actions:

  1. Search Twitter for viral tweets in your topic (use twitter-intel skill or WebSearch)
  2. Record high-performing tweets':

- Hook structure (first line) - Thread vs single tweet format - Engagement patterns (replies vs retweets) - Tone and punchiness

  1. Analyze success factors (contrarian takes, specific numbers, relatability)

Step 2: Extract Winning Patterns

DimensionWhat to Extract
Hook FormulaFirst line that stops scroll
Thread StructureHow points are organized
Number UsageDollar amounts, percentages, timeframes
Engagement BaitWhat makes people reply
Punch/RhythmSentence length and cadence

Step 3: Adapt with Your Brand Voice

Adaptation Rules:

  1. Keep the winning hook structure
  2. Replace with YOUR real stories and data
  3. Be specific: "$3,000 wasted" > "lost money"
  4. Add personality: "still cringe", "learned the hard way"
  5. Keep tweets punchy — short sentences, clear rhythm
  6. End threads with engagement question

Step 4: Deliver Complete Content

Deliverables Checklist:

  • Main tweet (hook + value + CTA)
  • Thread structure if applicable (7-10 tweets)
  • Character count check (<=280 per tweet)
  • Reply templates for common responses
  • Scheduling times (9 AM, 1 PM, 3 PM EST)
  • Self-reply tip to add (boost engagement)

Core Positioning (Customize This)

Voice: Blunt, sharp, authentic — "build-in-public meets sharp takes" Audiences: [Your target audiences — e.g., DTC brand operators, investors/VCs, AI/tech community] Differentiation: [Your unique angle — what makes your product/perspective different]

Algorithm Essentials (2025)

  • Golden Hour: First 60 minutes critical — engagement velocity determines reach
  • Comments = 15x likes in algorithmic weight
  • Saves are strongest signal
  • Threads get 3x engagement vs single tweets
  • Freshness decay: 50% reach reduction every 6 hours
  • Posts can sustain reach for 2-3 weeks if signals stay strong

Posting Framework

ElementSpec
Frequency3-5 quality tweets/day
Threads1-2x/week, 7-10 tweets optimal
Best times9-10 AM EST, 1-3 PM EST
Best daysTuesday, Wednesday, Monday
Reply target50 quality replies/day (growth phase)

Content Mix

  • 25-30% Build-in-public (metrics, challenges, behind-scenes)
  • 25-30% Thought leadership (industry analysis, contrarian takes)
  • 15-20% Personal stories (failures, pivots, lessons)
  • 15-20% Value/education (tutorials, frameworks)
  • 10% max Product promotion

Hook Formulas

Transformation: "6 months ago I was X. Today Y. Here's the playbook:"
Contrarian: "Everyone's building X. Here's why that's actually smart:"
Authority + Promise: "I've done X. Here are the Y patterns:"
Curiosity Gap: "I discovered ONE thing that 10x'd my Z. It has nothing to do with [obvious]:"

Voice Guidelines

Use:

  • Specific numbers and real data
  • Short, punchy sentences
  • Personal stories with lessons
  • Honest takes, even uncomfortable ones

Avoid:

  • "Revolutionary", "Game-changing", "Seamless"
  • Vague claims without data
  • Corporate speak
  • Excessive hashtags

Conference/Event Content Strategy

Content Cadence

Pre-Event: 2-3 tweets/day During Event: 3-5 tweets/day (real-time value) Post-Event: 2-3 tweets/day + 1 thread

Thread Structure (7-10 tweets)

1/ Hook: "Money I wasted at CES..." or "Lessons from my second CES..."
2-6/ Individual points with specifics
7/ Summary/key takeaway
8/ Call for engagement: "What's your experience?"

Tweet Types for Events

TypeExampleWhen to Use
Prep tweets"CES countdown: 9 days. Here's my checklist:"Pre-event
Real-time observations"Just walked Eureka Park. 3 things that surprised me:"During
Quick tips"CES pro tip: Comfortable shoes > dress shoes"Anytime
Contrarian takes"80% of CES booths aren't worth your time. Here's how to find the 20%:"Post-event
Number-driven"I wasted $1,400 at my first CES. Here's the breakdown:"Post-event

Input/Output Examples

Example 1: Single Tweet Request

User Input:

"Help me write a tweet about CES"

Expected Output:

Main Tweet:
"Lesson from CES: The founders who got meetings weren't the loudest. They were the ones who booked 6 weeks early.

90% of Brella meetings are scheduled before the event starts. I learned this the hard way last year."

Self-reply (post 10 min later):
"The real flex at CES isn't your booth. It's your calendar."

Schedule: 9:00 AM EST Tuesday
Character count: 248 OK

Example 2: Thread Request

User Input:

"Write a thread about AI creative tools"

Expected Output:

1/ Most AI creative tools have a dirty secret.

They make everything look the same.

Here's what I learned testing 15+ tools for brand creative:

2/ The problem isn't the AI.

It's that these tools optimize for "good enough" — not "on-brand."

3/ After 6 months of testing:
- Tool A: Great art, zero brand memory
- Tool B: Generic copy every time
- Tool C: Templates that sound like everyone else

4/ The missing piece: Brand memory.

Not a new term. It's how the best brand teams already work — they have a "brand bible" in their heads.

5/ What if AI could learn that bible?

That's what we're building.

6/ Early results:
- 10 hours saved per week
- Creative that actually passes brand review first time
- No more "make it more on-brand" feedback loops

7/ The shift happening now:

From: AI that generates content
To: AI that generates YOUR content

Who else is tired of generic AI output?

Example 3: Build-in-Public Update

User Input:

"We just shipped a new feature, help me write a tweet"

Response Pattern:

  1. Ask: "What feature? Who benefits? One metric if available?"
  2. Then generate tweet with:

- What shipped (specific) - Why it matters (user benefit) - One proof point (number or before/after) - No hype words

Example Output:

"Shipped: Auto-brand-check for ad creative.

Before: 3 rounds of revision to pass brand review.
After: 90% first-time approval rate.

The surprising part: Most rejections weren't about design. They were about tone."

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.57%
按下载量换算25

Claude

31.16%
按下载量换算22

Cursor

17.97%
按下载量换算13

Gemini CLI

9.11%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills