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

thread-builder线程构建器

Agent Skill

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

总安装

848

周安装

35

GitHub Stars

37

下载量

277
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:thread-builder(线程构建器)
来源仓库:https://github.com/majesticlabs-dev/majestic-marketplace
仓库路径:skills/thread-builder
安装命令:
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill thread-builder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill thread-builder

简介

用于查找、检索和筛选线程构建相关的技术实现或最佳实践。

  • 适合并发编程、任务调度等场景下的线程创建与管理参考。
  • 支持按框架(如 Spring、.NET)分类获取示例代码。
  • 安装命令:npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill thread-builder。
  • 建议验证示例代码与当前项目的兼容性。

SKILL.md

Thread Builder

Structure content into engaging Twitter/X threads that hold attention and drive engagement.

Thread Anatomy

Every high-performing thread follows this structure:

Tweet 1: HOOK (stop the scroll)
Tweet 2-3: SETUP (establish context/stakes)
Tweet 4-8: BODY (deliver value, escalate)
Tweet 9-10: CLIMAX (peak insight/revelation)
Tweet 11-12: CTA (action + engagement ask)

Optimal Thread Length

Thread TypeLengthBest For
Quick insight5-7 tweetsSingle concept, high shareability
How-to guide8-12 tweetsTutorials, frameworks
Story thread10-15 tweetsNarratives, case studies
Deep dive15-20 tweetsComplex topics, research

Rule: If you can't fill 8 tweets with value, it's a post, not a thread.

Hook Formulas (Tweet 1)

The hook determines 80% of thread performance. Use these patterns:

Curiosity Gap

I spent [X time] studying [topic].

Here's what nobody tells you:

Contrarian

[Common belief] is wrong.

Here's what actually works:

Story Open

[Time ago], I [was in bad situation].

Today, I [am in good situation].

Here's exactly what changed:

Numbered Promise

[X] [unexpected adjective] ways to [achieve result].

(Most people only know #3)

Before/After

[X months] ago: [bad state]
Today: [good state]

The [X]-step system that changed everything:

Social Proof

This [thing] helped me [specific result].

[Specific number/metric] later, here's the breakdown:

Tweet-by-Tweet Structure

Tweet 1: The Hook

  • First line is everything (appears in preview)
  • Use line breaks for rhythm
  • End with colon or "Here's..." to create pull

Tweet 2: The Stakes

  • Why this matters to the reader
  • What they'll gain by reading
  • Or: Context that amplifies the hook
Example:
"This isn't theory. I've tested this on [X] campaigns.

The difference: [specific metric improvement]"

Tweets 3-8: The Body

Each tweet should:

  • Make ONE clear point
  • Include a specific example or number
  • End with momentum into next tweet

Momentum Patterns:

  • "But here's where it gets interesting..."
  • "The real secret?"
  • "Most people stop here. Don't."
  • "Here's what I mean:"
  • "Example:"

Tweet 9-10: The Climax

  • Deliver the core insight
  • This is the "aha" moment
  • Most quotable/screenshottable tweet
Example:
"The truth nobody talks about:

[Counterintuitive insight]

This single shift [specific result]."

Tweet 11-12: The CTA

Layer your CTAs:

Tweet 11 - Soft CTA:

If this helped, I share [topic] threads every [day].

Follow @handle so you don't miss them.

Tweet 12 - Engagement CTA:

What's your biggest challenge with [topic]?

Drop it below - I'll respond to everyone.

Thread Arc Patterns

The Listicle Arc

1. Hook with number promise
2. Why this matters
3. Item 1 (strongest)
4. Item 2
5. Item 3
6. Item 4
7. Item 5 (second strongest)
8. Bonus item (unexpected)
9. Key takeaway
10. CTA

The Story Arc

1. Hook (dramatic moment)
2. Context (where I was)
3. The problem
4. First attempt (failed)
5. What I learned
6. The breakthrough
7. The result
8. Key lesson 1
9. Key lesson 2
10. CTA + question

The Framework Arc

1. Hook (promise the framework)
2. Why most approaches fail
3. The framework overview
4. Step 1 (with example)
5. Step 2 (with example)
6. Step 3 (with example)
7. Common mistake to avoid
8. Advanced tip
9. Results you can expect
10. CTA

The Myth-Busting Arc

1. Hook (controversial take)
2. The common belief
3. Why people believe it
4. The evidence against
5. What actually works (part 1)
6. What actually works (part 2)
7. Case study/example
8. The real insight
9. How to apply this
10. CTA

Cliffhanger Patterns

Keep readers scrolling with these tweet endings:

PatternExample
The Tease"But that's not even the best part..."
The Question"So what happened next?"
The Contradiction"Turns out, I was completely wrong."
The Promise"Here's where it gets good:"
The Number"Result? [Specific metric]"
The Challenge"Most people won't do this. Will you?"

Formatting Rules

Line Breaks

  • Use single line breaks between thoughts
  • Double line breaks for emphasis
  • Never wall-of-text a tweet

Bad:

Here's why most people fail at X. They don't understand that Y is actually more important than Z. The research shows that...

Good:

Here's why most people fail at X:

They focus on Y.

But Z is what actually matters.

The research proves it:

Numbers and Specificity

  • "A lot of money" → "$47,000"
  • "Recently" → "Last Tuesday"
  • "Many people" → "2.3 million users"
  • "Improved results" → "47% higher conversion"

Emoji Usage

  • One emoji per tweet maximum
  • Use for visual breaks, not decoration
  • Best at start of lists or sections

Thread Types by Goal

GoalThread TypeKey Elements
Grow followersEducational how-toActionable tips, follow CTA
Build authorityDeep analysisData, unique insight, contrarian take
Drive engagementStory threadEmotion, cliffhangers, question CTA
Generate leadsFramework threadFree resource in final tweet
Viral reachListicleShareable insights, save-worthy

Anti-Patterns

Don't:

  • Start tweet 1 with "Thread:" or "1/"
  • Number every tweet (only if listicle)
  • End tweets mid-sentence to force clicks
  • Use more than one CTA type
  • Make tweets dependent on previous (each should standalone)
  • Pad with filler tweets

Do:

  • Write tweet 1 as if it's the only tweet people will see
  • Make every tweet valuable on its own
  • Use the last tweet to encourage retweets of tweet 1
  • Schedule threads for optimal times (8am, 12pm, 5pm local)

Output Format

When building a thread, present as:

## Thread: [Topic]

**Thread Type:** [Listicle/Story/Framework/Myth-Busting]
**Length:** [X] tweets
**Goal:** [Followers/Authority/Engagement/Leads]

---

### 1/ HOOK
[Tweet text]

---

### 2/ STAKES
[Tweet text]

---

### 3/ BODY
[Tweet text]

---

[Continue for all tweets...]

---

### [X]/ CTA
[Tweet text]

---

## Engagement Prediction
- **Hook strength:** [Strong/Medium/Needs work]
- **Save-worthy tweets:** [List tweet numbers]
- **Retweet triggers:** [What makes it shareable]

Quick Reference

Hook checklist:

  • First line stops the scroll
  • Creates curiosity gap
  • Promises specific value
  • Uses line breaks

Body checklist:

  • Each tweet has one clear point
  • Includes specific numbers/examples
  • Momentum into next tweet
  • Standalone value

CTA checklist:

  • Follow ask
  • Engagement question
  • Easy action (comment, not click)

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

34.78%
按下载量换算96

Claude

33.03%
按下载量换算91

Cursor

20.89%
按下载量换算58

Gemini CLI

9.11%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills