ljg-travel

lijigang/ljg-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-travel
0 commentsdiscussion
summary

一条命令完成:全维度文化研究 → 内容提炼 → org 文档 + 便携卡片。

skill.md

ljg-travel-flow: 旅行研究

一条命令完成:全维度文化研究 → 内容提炼 → org 文档 + 便携卡片。

方法论借鉴考古学 Desk-Based Assessment(DBA):到达之前,穷尽一切文献证据。

模式

强制 NATIVE 模式。 本 workflow 是多 skill 管道(Research → ContentAnalysis → ljg-card),不走 Algorithm 七步流程。

参数

参数 说明 示例
城市名 必填,目标城市 西安、洛阳、大同
-f 聚焦主题(可选) -f 唐代 -f 石窟 -f 青铜器
-q 快速模式,跳过内容提炼,只做研究+文档

执行

1. 解析参数

从用户消息中提取城市名称和可选参数。如有聚焦主题,后续所有搜索围绕该主题展开。

2. 全维度研究(Research extensive — 单次调用,12 个 Agent 并行)

调用 Skill tool 执行 Research,使用 extensive 模式。

核心设计:不分"知识底图"和"平台发现"两步——它们是同一个研究操作的不同搜索角度。 12 个 Agent 同时出发,一半做学术/百科研究,一半做平台内容搜索。

研究提纲(传入 Research 的 prompt):

对「{城市}」进行深度文化旅行研究。这不是旅游攻略,是出发前的考古学式案头研究(Desk-Based Assessment)。

研究覆盖以下维度,每个维度需要中英文双语搜索:

**维度 A — 历史分层**
该城市经历了哪些重要历史时期?每个时期在这座城市留下了什么物质遗存?朝代更迭如何影响城市格局?

**维度 B — 博物馆重点**
该城市有哪些重要博物馆?各博物馆的镇馆之宝和核心馆藏?哪些展品有重大考古意义?必须给出具体文物名称和展厅位置。

**维度 C — 古建遗存**
现存哪些重要古建筑和遗址?营造年代、建筑形制、结构特点。哪些是全国重点文物保护单位?看建筑时应关注什么细节(斗拱、彩画、碑刻等)?

**维度 D — 考古发现**
该城市及周边有哪些重大考古发现?出土文物现藏于哪些博物馆?发掘过程中有什么重要故事?

**维度 E — 人文脉络**
与该城市相关的重要历史人物、文学作品、文化传统。帮助理解这座城市的文化性格。

**维度 F — 深度内容发现**
搜索 B站(bilibili.com)、知乎(zhihu.com)、微信公众号(mp.weixin.qq.com)、抖音(douyin.com)、小红书(xiaohongshu.com)上关于该城市博物馆和古建的深度讲解内容。
筛选标准:
- 要:有知识增量的内容(讲背景、讲工艺、讲考古过程、讲建筑细节)
- 不要:纯打卡拍照、纯推荐无分析、广告软文
- B站视频优先 10 分钟以上的讲解类
- 公众号文章优先有参考文献或明确作者身份的
返回内容标题、URL、一句话摘要。

{如有聚焦主题:特别关注与「{聚焦主题}」相关的内容,其他维度作为背景补充。}

等待 Research 完成,获得全维度研究结果。

3. 内容提炼(ContentAnalysis — 可选)

如果用户指定了 -q 快速模式,跳过此步。

从步骤 2 返回的结果中,提取所有有效 URL(文章链接、视频链接)。

对每个 URL 并行启动 Agent subagent:

每个 subagent 调用 Skill tool 执行 ContentAnalysis,传入 URL,使用 fast 深度级别,提取核心知识点。

降级规则:

  • 如果 ContentAnalysis 对某个 URL 失败(无法访问、无字幕等),跳过该 URL,不阻塞
  • 如果所有 URL 都失败,流程不中断——步骤 2 的研究结果已经足够生成文档
  • ContentAnalysis 是增强层,不是必要层

收集所有成功提炼的内容摘要。

4. 合成 org-mode 文档

将步骤 2(研究结果)和步骤 3(内容提炼,如有)合成为一份结构化 org-mode 文档。

文档结构:

#+title: {城市}旅行研究
#+date: {当前日期}
#+filetags: :travel:museum:architecture:

* 城市概览
  {城市}的文明坐标——为什么值得去,去了看什么。一段话勾勒这座城市在中国文明史中的位置。

* 历史分层
** {时期1}({年代范围})
   核心事件、遗留痕迹、对应可看的实物。
** {时期2}
   ...

* 博物馆指南
** {博物馆1名称}
   地址、开放时间、预约方式(如需要)。
*** 镇馆之宝
    - {文物名}:{为什么重要} | 看什么细节:{具体观察点}
*** 重点展厅
    - {展厅名}:{核心看点}
*** 容易错过的
    - {被忽视但值得看的内容}
** {博物馆2名称}
   ...

* 古建遗存
** {古建1名称}({朝代},{保护级别})
   形制概述。
*** 看什么
    - {具体观察点1}:{为什么值得注意}
    - {具体观察点2}
** {古建2名称}
   ...

* 考古发现
** {遗址/发现1}
   发现经过、意义、出土文物现藏地。如果有有趣的发掘故事,讲出来。

* 参观路线
** 路线一:{主题名}({预计时间})
   适合谁:{描述}
   1. {地点} → 重点看 {什么}({停留建议时间})
   2. ...
** 路线二:{主题名}
   ...

* 深度内容推荐
  从各平台发现的值得在出发前看的内容。
** 视频
   - [[{URL}][{标题}]] — {一句话摘要}
** 文章
   - [[{URL}][{标题}]] — {一句话摘要}
** 书籍(如有推荐)
   - {书名} — {为什么值得读}

文件命名:使用 denote naming schema,保存到 ~/Documents/notes/ 目录: {YYYYMMDDTHHMMSS}==z--{城市}旅行研究.org

写作要求

  • 每个推荐必须有「为什么看」和「看什么细节」,不许空泛
  • 语气是给自己写的笔记,不是导游词
  • 有确切信息写确切的,没有的不编

5. 铸造便携卡片(ljg-card)

从步骤 4 的 org 文档中提取核心内容,铸造两张卡片,并行执行

卡片 A — 城市文明概览(信息图):

调用 Skill tool 执行 ljg-card -i,输入内容为:城市历史分层 + 核心博物馆清单 + 必看古建清单的精华摘要。一张图看懂这座城市的文明骨架。

卡片 B — 参观路线速查(长图):

调用 Skill tool 执行 ljg-card -l,输入内容为:参观路线建议 + 每个地点的核心看点。手机上随时查看。

6. 汇总报告

════ 旅行研究完成 ═══════════════════════
🏛️ 城市: {城市名}
📝 知识文档: {org 文件路径}
🖼️ 文明概览卡: {PNG 文件路径}
🖼️ 路线速查卡: {PNG 文件路径}
📊 研究覆盖: {N}个博物馆 | {M}座古建 | {K}处考古遗址
📎 深度内容: {X}个视频 | {Y}篇文章

关键约束

  • 步骤 2 是核心——12 个 Agent 并行覆盖学术研究和平台内容,一次完成
  • 步骤 3(内容提炼)是增强层,失败不阻塞流程
  • 步骤 5 的两张卡片之间并行
  • org 文档是主产出,卡片是衍生产出——文档质量优先
  • 不产出泛泛的旅游攻略,每个推荐必须有「为什么看」和「看什么细节」
  • Research 搜索使用中英文双语关键词,扩大覆盖面
  • 没有确切信息时宁可留空,不编造

Known Pitfalls

(首次创建,暂无记录。使用中积累。)

how to use ljg-travel

How to use ljg-travel on Cursor

AI-first code editor with Composer

1

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-travel
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-travel

The skills CLI fetches ljg-travel from GitHub repository lijigang/ljg-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ljg-travel

Reload or restart Cursor to activate ljg-travel. Access the skill through slash commands (e.g., /ljg-travel) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.864 reviews
  • Tariq Reddy· Dec 20, 2024

    I recommend ljg-travel for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Pratham Ware· Dec 12, 2024

    ljg-travel reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chinedu Lopez· Dec 4, 2024

    Useful defaults in ljg-travel — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Valentina Gonzalez· Dec 4, 2024

    Useful defaults in ljg-travel — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Tariq Sethi· Nov 23, 2024

    ljg-travel is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nikhil Huang· Nov 23, 2024

    ljg-travel is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zara Gonzalez· Nov 11, 2024

    Keeps context tight: ljg-travel is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Tariq Malhotra· Oct 14, 2024

    Keeps context tight: ljg-travel is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • James Harris· Oct 14, 2024

    Keeps context tight: ljg-travel is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Zara Anderson· Oct 2, 2024

    ljg-travel is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 64

1 / 7