Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计提醒

plg-ai-funnelPLGAI 漏斗

Agent Skill

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

总安装

792

周安装

34

GitHub Stars

37

下载量

277
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于处理 GitHub 仓库、Issue 和 Pull Request 信息。

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

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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills