ljg-paper-flow▌
lijigang/ljg-skills · updated May 19, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
一条命令完成：读论文 → 生成解读 → 铸成卡片。支持多篇并行。
ljg-paper-flow: 论文流
一条命令完成：读论文 → 生成解读 → 铸成卡片。支持多篇并行。
模式
强制 NATIVE 模式。 本 workflow 是纯 skill 管道（ljg-paper → ljg-card），不需要 Algorithm 的七步流程。直接按下方执行步骤调用 skill，不走 OBSERVE/THINK/PLAN/BUILD/EXECUTE/VERIFY/LEARN。
参数
| 参数 | 说明 |
|---|---|
| 无参数 | 对话中已提供的论文链接/文件 |
-l |
卡片模具改用长图模式（默认 -c 漫画） |
-i |
卡片模具改用信息图模式 |
执行
1. 收集论文列表
从用户消息中提取所有论文来源（arxiv URL、PDF 路径、论文名称等）。
2. 并行处理每篇论文
对每篇论文，启动一个 Agent subagent，每个 subagent 按顺序执行两步：
步骤 A — 读论文（ljg-paper）：
调用 Skill tool 执行 ljg-paper，传入该论文的来源。等待完成，获得生成的 org 文件路径。
步骤 B — 铸卡片（ljg-card）：
读取步骤 A 生成的 org 文件，调用 Skill tool 执行 ljg-card（默认 -c，或按用户指定的模具参数），以 org 文件内容为输入。等待完成，获得 PNG 文件路径。
3. 汇总报告
所有论文处理完成后，汇总输出：
════ 论文流完成 ═══════════════════════
📄 {论文标题1}
📝 解读: {org 文件路径}
🖼️ 卡片: {PNG 文件路径}
📄 {论文标题2}
📝 解读: {org 文件路径}
🖼️ 卡片: {PNG 文件路径}
...
关键约束
- 每篇论文的两步必须串行（先 paper 后 card），但多篇论文之间并行
- ljg-paper 和 ljg-card 各自的质量标准、红线、品味准则不变
- 卡片内容来自生成的 org 文件，不是原始论文
How to use ljg-paper-flow 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-paper-flow
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ljg-paper-flow 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-paper-flow. Access the skill through slash commands (e.g., /ljg-paper-flow) 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★★★★★35 reviews- ★★★★★Chinedu Yang· Dec 24, 2024
Registry listing for ljg-paper-flow matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Diego Kapoor· Dec 16, 2024
Keeps context tight: ljg-paper-flow is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Aarav Iyer· Dec 12, 2024
We added ljg-paper-flow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Nov 23, 2024
I recommend ljg-paper-flow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kiara Nasser· Nov 15, 2024
I recommend ljg-paper-flow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kaira Ghosh· Nov 15, 2024
ljg-paper-flow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sakura Rao· Nov 7, 2024
ljg-paper-flow has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aditi Khanna· Nov 3, 2024
ljg-paper-flow reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hana Rahman· Oct 26, 2024
Solid pick for teams standardizing on skills: ljg-paper-flow is focused, and the summary matches what you get after install.
- ★★★★★Aditi Shah· Oct 22, 2024
Registry listing for ljg-paper-flow matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 35