Token导航 LogoToken导航

Agent Skill · 待分类

linkedin-authority-builder(linkedin 权威建设者)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

linkedin-authority-builder 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 1,971。

总安装 2,022周安装 81GitHub Stars 262下载 654核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/brianrwagner/ai-marketing-skills --skill linkedin-authority-builder

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

linkedin-authority-builder 用于辅助安全审计和权限检查。适合梳理敏感配置、分析鉴权逻辑或生成安全复核清单。不能将工具输出直接作为最终结论,需二次验证关键操作。涉及密钥或用户数据时应先确认最小权限和脱敏策略。建议在测试环境验证后再应用于生产系统。

linkedin-authority-builder 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/linkedin-authority-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/brianrwagner/ai-marketing-skills --skill linke…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

linkedin-authority-builder 怎么安装?

在终端执行 npx skills add https://github.com/brianrwagner/ai-marketing-skills --skill linkedin-author…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

linkedin-authority-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

linkedin-authority-builder 需要什么权限?

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

linkedin-authority-builder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

linkedin-authority-builder 用的人多吗?

公开数据是累计安装 2,022 次,近一周安装 81 次,下载 654 次,GitHub 262 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

linkedin-authority-builder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
linkedin-authority-builder

linkedin 权威建设者 · 本页

2,022262只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

LinkedIn Authority Builder

Here's what most people get wrong about LinkedIn: they're trying to go viral.

Viral doesn't pay your bills. Being remembered by the right 500 people when they need what you do — that pays your bills.

This skill builds a content system around consistent positioning and clear pillars — not hacks.


Mode

Detect from context or ask: *"Starter plan, full content system, or 90-day build?"*

ModeWhat you getBest for
quick3 content pillars + 1-week posting starter planGetting unstuck, first week of consistency
standardFull content system: pillars, formats, posting rhythm + first week writtenBuilding a repeatable presence
deepFull system + 90-day calendar + 10 posts written + engagement playbookSerious authority-building campaign

Default: standard — use quick if they just need to start posting. Use deep if they're committing to LinkedIn as a growth channel.


Context Loading Gates

Before generating any strategy, load:

  • Current positioning: One-liner, ICP, key differentiator (load from positioning-basics output if available)
  • Target audience on LinkedIn: Specific titles, company stages, industries
  • Posting history: What have they tried? What worked? What didn't?
  • Content goals: Leads / job offers / speaking / partnerships / audience growth
  • Available time per week: Hours they can realistically commit

Sequencing gate: If positioning isn't clear yet, stop and ask:

"Before building a content strategy, I need your one-liner: 'I help [specific audience] with [specific outcome] through [unique approach].' Do you have this locked, or should we nail positioning first with positioning-basics?"

Do not build a content system for an unclear position — the content will be unfocused.

Also suggest:

"Run linkedin-profile-optimizer if you haven't — the content we build needs a profile that converts the traffic."

Phase 1: Positioning Alignment Analysis

Before recommending any content, reason through:

  1. Positioning check: Is the one-liner specific enough to anchor content pillars? If it's "I help businesses grow," that's too vague — push for specificity before proceeding.
  2. Audience clarity: Are we targeting a specific title + company stage, or a demographic? Specific is better.
  3. Time-to-output match: If they have 2 hours/week, don't recommend 5 posts/week. Sustainability matters more than ambition.
  4. Goal alignment: Content for lead generation looks different from content for speaking gigs. Confirm goal before building pillars.

Output a brief strategy assessment:

"You're a [role] targeting [audience] with [X hours/week] and a goal of [outcome]. I'll build a [3/5 post/week] strategy anchored to [X] pillars. The main gap in your current approach: [specific gap]."

Phase 2: Content Pillars (3–5 Required)

Each pillar must pass all 4 tests:

  1. You have genuine expertise (not just interest)
  2. Your target audience actively cares about it
  3. You can produce content on it consistently for 6+ months
  4. It connects to what you sell or want to be known for

Pillar ratio:

  • 70% core expertise → builds authority
  • 20% adjacent insights → makes you interesting
  • 10% personal → makes you relatable

Output format per pillar:

Pillar: [Name]
Ratio: [%]
Content types: [frameworks / stories / case studies]
Example hook: "[First line of a real post]"
Connection to goal: [how this drives the stated outcome]

Phase 3: Format Selection & Post Templates

Format-to-Goal Mapping

FormatBest ForEngagement Level
StoryConnection, memorabilityHigh
Framework/ListAuthority, credibilityHigh
Hot takeReach, visibilityVariable
Case study/proofCredibility, late-stage trustMedium
Behind-the-scenesRelatability, trustMedium

Recommended weekly mix:

  • 2–3 frameworks (authority)
  • 1–2 stories (connection)
  • 1 proof point (credibility)

Post Templates

Story Post:

[Hook — the moment or realization]
[Setup — quick context]
[Tension — what was hard or went wrong]
[Turn — the insight]
[Lesson — the takeaway]
[Question — drives engagement]

Framework Post:

[Hook — bold claim or problem statement]
[Why this matters — 1-2 sentences]
[The X-step framework:]
1. [Step + brief explanation]
2. [Step + brief explanation]
3. [Step + brief explanation]
[Key insight or summary]
[CTA or discussion question]

Hot Take:

[Controversial statement]
[Your reasoning — 2-3 sentences]
[The nuance people miss]
[What to do instead]
[Question to drive comments]

Phase 4: Content Calendar with Real Dates

Generate a 4-week calendar with actual dates (not generic day names):

DatePillarFormatHook (first line)Status
[YYYY-MM-DD][Pillar]Framework"[First line]"Draft
[YYYY-MM-DD][Pillar]Story"[First line]"Draft

Fill 4 full weeks. Generic "Week 1, Monday" output is not sufficient.

Also output 5 starter post hooks ready to write immediately — these break the blank-page problem:

1. [Hook]
2. [Hook]
3. [Hook]
4. [Hook]
5. [Hook]

Phase 5: Self-Critique Pass (REQUIRED)

After generating the strategy, evaluate:

  • Is the positioning one-liner specific enough to anchor the pillars?
  • Are the 5 starter hooks actually strong — would they stop the scroll?
  • Does the time commitment match the user's stated available hours?
  • Is at least one pillar directly tied to the revenue/goal outcome?
  • Does the calendar have actual dates, or just generic "Day 1/Day 3" placeholders?
  • Would this content system still work in 6 months if the user stays consistent?

Flag issues: "Pillar 3 ('general business tips') doesn't connect to your stated goal of attracting SaaS founders. Replace with something more specific."


Phase 6: 30-Day Iteration Protocol

After 30 days, review with these questions:

  • Which posts got the most comments? What pillar did they fall under?
  • Which posts drove DMs or profile views?
  • Which posts got the most impressions regardless of engagement?

Adjust based on data:

  • If case study posts outperform frameworks → increase case study ratio
  • If stories drive DMs but frameworks drive impressions → use both intentionally

Output Structure

## LinkedIn Strategy: [Name] — [Date]

### Positioning Alignment
[One-liner + assessment of clarity]

### Content Pillars
[3-5 pillars with ratio, examples, connection to goal]

### Weekly Rhythm
- Posts/week: [X]
- Best times: [e.g., Tue/Thu 8am EST]
- Active commenting: [X min/day]

### Format Mix
[Breakdown with rationale]

### 4-Week Content Calendar
[Table with real dates + hooks]

### 5 Starter Posts (Write These First)
[Hooks with format labels]

### Engagement Plan
[Who to engage with, how much time, what to say]

### Self-Critique Notes
[Issues flagged + recommended fixes]

### 30-Day Review Triggers
[What to measure and when to adjust]

### Cross-References
- linkedin-profile-optimizer (run before publishing)
- content-idea-generator (for ongoing idea generation)
- voice-extractor (to ensure posts sound authentic)

*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*

平台分布

Codex

35.65%
按下载量换算233

Claude

31.68%
按下载量换算207

Cursor

17.41%
按下载量换算114

Gemini CLI

8.83%
按下载量换算58

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills