ljg-invest▌
lijigang/ljg-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
生成一份投资分析报告。核心只问一个问题:这个东西在创造新秩序,还是在搬运旧秩序?
投资报告
生成一份投资分析报告。核心只问一个问题:这个东西在创造新秩序,还是在搬运旧秩序?
认知起点
财富不是钱,是被欲望照亮的秩序。投资就是拿手里的秩序去换一台更好的秩序生成器。
所以不称重,看相:
- 不问"这个公司值多少钱",问"这台机器转不转得起来"
- 不问"市场多大",问"市场在用什么过时的眼睛看它"
- 不问"能涨多少",问"我拿什么换什么,换完之后谁更聪明"
输入
公司名称、BP、文字介绍、对话记录,或任何描述项目的材料。知名公司只给名字即可——用 Research skill 或 subagent 抓取最新财报和行业数据。
报告结构
以下五个区块是骨架,不是填空题。对某个项目来说哪个区块最有料,那个区块就多写;没料的一两句带过或直接跳过。报告为判断服务,不为完整性服务。
一、这是什么
一张表 + 一句自定义赛道定义。
| 维度 | 内容 |
|---|---|
| 项目名称 | |
| 赛道定义 | 用我们自己的语言,不用市场标签 |
| 阶段 | |
| 融资情况 | 金额 / 估值 / 条款(有则填,无则标注) |
| 数据快照 | 关键运营数据 |
赛道定义要穿透表面标签。"搜索引擎公司"是隔的,"人类认知基础设施的垄断运营商"是不隔的——后者告诉你它真正在做什么。
二、秩序创造机器判定
这是整份报告的心脏。不逐项打分,而是回答一个问题:这台机器转不转得起来?
从三个角度看:
飞轮在不在转? 系统有没有越用越好的结构——用户越多数据越多,数据越多产品越好,产品越好用户越多?这个循环是已经在转、刚开始、还是停着?转了多久?加速还是匀速?如果不转,什么卡住了?
冲击后变强还是变弱? 竞争来了、技术变了、市场塌了——这台机器是碎掉、扛住、还是吃掉冲击变成自己的燃料?历史上有没有被冲击过?结果如何?
资源是被推过来的,还是自己来的? 扩张靠的是一个一个谈、一块一块买(推),还是别人主动涌过来、因为不来就亏(引力)?有没有"不推而聚"的迹象?
综合判定:
- 秩序创造机器 — 飞轮在转,冲击后变强,资源自己来
- 有潜力 — 飞轮有结构但还没验证转起来
- 秩序搬运 — 把已有的东西重新排列,没有生成新秩序
三、创生公式
每台秩序创造机器都有一个核心算法。用一句话写出来。
参考:
- 亚马逊 = 利润→再投资→降成本→降价→更多用户→更多利润
- 特斯拉 = 硬件采数据→数据训练算法→算法重新定义硬件
- Google = 每次人类找答案的方式迁移时,成为新方式的默认基础设施
然后回答:
- 这个公式被验证过几次?验证到什么程度?
- 别人在跑相似的公式吗?差异在哪?
四、市场看见的 vs 我们看见的
这一节决定投资时机。
它在 S 曲线的哪里? 积累期、拐点、加速期、平台期。如果在拐点前——什么条件能触发拐点?
市场在用什么旧眼睛看它? 市场给它贴的标签是什么?这个标签遮住了什么?我们的框架看到了什么市场看不到的?认知差有多大——这是超额收益的来源。
三个信号检测认知折价:
- 需要很复杂的解释别人才能听懂?
- 定价持续异常(部分之和 ≠ 整体)?
- 已有的类比全部失效("像 X 但又不像 X")?
它控制了什么别人拿不走的东西? 权力来源是什么——数据、分发、标准、网络效应?这种控制是静态的(品牌、专利)还是动态的(越变越强)? 这个稀缺性未来会不会位移?项目有没有能力跟着位移走?
它在搭哪趟便车? 三种成本正在坍缩——理解成本、协作成本、行动成本。这个项目骑在哪一种上?坍缩释放的能量被它捕获了多少?
五、换不换
交换建议:建议投资 / 建议观察 / 建议放弃
如果投资:建议金额范围、关键条款
核心假设:这个决策依赖哪几个假设?每个假设附退出信号——什么数据出现说明假设错了,该跑。
未解问题:3-5 个对决策至关重要但还没答案的问题,按优先级排。
最后一句
用一句话回答:这个项目的本质是什么?创造新秩序,还是搬运旧秩序?
输出
- 格式:org-mode
- 目录:
~/Documents/notes/ - 命名:denote schema —
YYYYMMDDTHHMMSS==z--投资分析-PROJECT_NAME.org- 例:
20260326153000==z--投资分析-example-ai.org
- 例:
- 用 Write 工具写入,写完告知完整路径
生成规则
- 基于真实信息,不编造。信息不足的直接标注,不硬撑
- 敢判断。"既可能好也可能坏"是废话,不许出现
- 每个判断附证据——数据、引用、具体事实
- 禁止出现:赛道很大、团队优秀、前景广阔、蓝海市场
- 以说透为准,不计字数。两千字能说清就两千字,需要七千字就七千字
- 中文撰写
How to use ljg-invest on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add ljg-invest
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ljg-invest from GitHub repository lijigang/ljg-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate ljg-invest. Access the skill through slash commands (e.g., /ljg-invest) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
We added ljg-invest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hiroshi Gonzalez· Dec 16, 2024
Useful defaults in ljg-invest — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Camila Mehta· Dec 16, 2024
ljg-invest has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aanya Kapoor· Dec 12, 2024
I recommend ljg-invest for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Rahul Santra· Nov 19, 2024
Useful defaults in ljg-invest — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Evelyn Thompson· Nov 7, 2024
We added ljg-invest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aarav Abbas· Nov 7, 2024
Solid pick for teams standardizing on skills: ljg-invest is focused, and the summary matches what you get after install.
- ★★★★★Aarav Sanchez· Oct 26, 2024
ljg-invest reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aarav Ramirez· Oct 26, 2024
ljg-invest is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Oct 10, 2024
Registry listing for ljg-invest matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 30