Token导航 LogoToken导航

Agent Skill · 待分类

plg-ai-funnel(PLGAI 漏斗)

plg-ai-funnel 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

plg-ai-funnel 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在待分类类的 11,209 个 Skill 里排第 4,182。

总安装 792周安装 34GitHub Stars 37下载 277核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill plg-ai-funnel

这个 Skill 是做什么的

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

用于处理 GitHub 仓库、Issue 和 Pull Request 信息。适合围绕代码变更或协作事项进行整理与分析。使用时可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围和维护状态,避免触发敏感操作。plg-ai-funnel 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/plg-ai-funnel

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

plg-ai-funnel 怎么安装?

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

plg-ai-funnel 支持哪些 AI 工具?

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

plg-ai-funnel 需要什么权限?

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

plg-ai-funnel 是免费的吗?

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

plg-ai-funnel 用的人多吗?

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

plg-ai-funnel 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 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操作浏览器未明确未通过
plg-ai-funnel

PLGAI 漏斗 · 本页

79237只读未明确有提醒

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

SKILL.md 原文

PLG AI Funnel: Product-Led Growth in the Agent Era

The Paradigm Shift

Old PLG Funnel:

Landing Page → Free Trial → Activation → Conversion

New PLG Funnel:

Agent Query → Documentation Scan → Feature Match → Recommendation

The buyer's first interaction is no longer your landing page—it's an AI agent scanning your documentation to answer their question.

The Four Stages

Stage 1: Agent Query

What happens: User asks AI "What tool can help me [problem]?"

Optimization goals:

  • Brand appears in AI's consideration set
  • Correct category association
  • Problem-solution mapping exists in AI's knowledge

Tactics:

ActionWhy It Works
Entity buildingAI must know your brand exists and what category it's in
Third-party mentionsReviews, comparisons, listicles feed AI training data
Clear positioning"X is a [category] that [primary benefit]" statements

Audit questions:

  • Does AI know your brand when asked directly?
  • Does AI associate your brand with your category?
  • Do competitors appear but you don't?

Tool: entity-builder agent for authority building

Stage 2: Documentation Scan

What happens: AI scans your docs, help center, marketing pages to understand capabilities.

Optimization goals:

  • Content is AI-extractable (chunked, structured)
  • Answers are front-loaded (not buried)
  • Each page passes the "Taco Bell Test" (stands alone)

Tactics:

ActionWhy It Works
Answer-first structureAI extracts the first sentence as the answer
FAQ sectionsPre-formatted Q&A is ideal for extraction
Structured dataTables, bullets, headers signal discrete facts
Standalone sectionsAI may only see one chunk, not the full page

The Extractability Checklist:

☐ First sentence directly answers the page's implied question
☐ H2/H3 headers are questions or clear topic labels
☐ Tables used for comparisons and feature lists
☐ Each section makes sense without surrounding context
☐ No "as mentioned above" or "see below" dependencies

Tool: llm-optimizer agent for content optimization

Stage 3: Feature Match

What happens: AI matches user's specific needs to your product's capabilities.

Optimization goals:

  • Features described in user-problem terms
  • Use cases explicitly mapped to capabilities
  • Limitations clearly stated (builds trust)

Tactics:

ActionWhy It Works
Problem → Feature mapping"If you need X, [Product] does Y"
Use-case pagesDedicated pages per job-to-be-done
Integration listsAI checks compatibility requirements
Pricing clarityAI needs to match budget constraints

Feature Documentation Template:

## [Feature Name]

**Problem it solves:** [User problem in their words]

**How it works:** [1-2 sentence explanation]

**Best for:** [Specific use cases]

**Limitations:** [What it doesn't do]

**Example:** [Concrete scenario]

Anti-pattern: Feature pages that describe functionality without connecting to user problems.

Stage 4: Recommendation

What happens: AI decides whether to recommend your product and how to position it.

Optimization goals:

  • Clear differentiation from alternatives
  • Social proof AI can cite
  • Product tie-backs throughout content

Tactics:

ActionWhy It Works
Comparison content"X vs Y" pages AI directly references
Quantified outcomes"Reduces time by 40%" > "saves time"
Review presenceG2, Capterra reviews influence AI recommendations
Product mentions in answersEvery content piece connects back to product

The Product Tie-Back Rule: Every 1-2 paragraphs of educational content should include how your product relates.

  • ❌ "Lead scoring helps prioritize prospects"
  • ✅ "Lead scoring helps prioritize prospects—[Product] automates this with AI-powered scoring"

Tool: aeo-scorecard skill for measuring recommendation success

PLG × AEO Integration

PLG StageAEO ConceptMetric
Agent QueryEntity/AuthorityAI Visibility %
Documentation ScanExtractabilityCitation Rate
Feature MatchFact-DensityFeature mention accuracy
RecommendationProduct Tie-BackAI Share of Voice

Quick Audit Workflow

1. Test 10 queries your buyers ask
   → Does your brand appear? (Stage 1)

2. Check if AI cites YOUR content
   → Or competitor/third-party? (Stage 2)

3. Ask AI about specific features
   → Does it know your capabilities? (Stage 3)

4. Ask "Should I use [Product] for [use case]?"
   → What's the recommendation? (Stage 4)

Common PLG AI Gaps

SymptomStage BrokenFix
Brand unknown to AIQueryEntity building, third-party mentions
AI cites competitors' contentDocumentationImprove extractability, answer-first
AI misunderstands featuresFeature MatchRewrite feature docs with problem framing
AI recommends competitorRecommendationStrengthen differentiation, add social proof

Related Tools

  • llm-optimizer - Deep content optimization for Stage 2
  • entity-builder - Authority building for Stage 1
  • aeo-scorecard - Metrics framework for all stages
  • /aeo-workflow - Full implementation workflow
  • query-expansion-strategy - Understanding query fan-out

平台分布

Codex

37.63%
按下载量换算104

Claude

29.83%
按下载量换算83

Cursor

17.92%
按下载量换算50

Gemini CLI

8.69%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills