菜单
Draft a tight-SEO Destination JSON file ready for Admin → Destinations → Import JSON. Use when the user gives facts about a place (national park, region, mountain, beach area) and wants a destination page with FAQs and gallery, or runs /seo-destination.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/cleven12/visit_kili_v2_cms --skill seo-destination命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Draft a tight-SEO Blog Article JSON file ready for Admin → Trek Guides → Import JSON (content type "Blog Article"). Use when the user gives a blog topic/angle and wants top-of-funnel content drafted, or runs /seo-article.
Draft a batch of customer FAQ entries as JSON ready for Admin → FAQs → Import JSON. Use when the user wants new FAQ entries written (booking questions, trek logistics, payment, visas, etc.), or runs /seo-faq.
Draft a tight-SEO Trek Guide JSON file ready for Admin → Trek Guides → Import JSON (content type "Trek Guide"). Use when the user gives raw how-to / trekking-advice facts and wants a long-form guide page, or runs /seo-guide.
基于 SOC 职业分类
正在显示 SKILL.md
| name | seo-destination |
| description | Draft a tight-SEO Destination JSON file ready for Admin → Destinations → Import JSON. Use when the user gives facts about a place (national park, region, mountain, beach area) and wants a destination page with FAQs and gallery, or runs /seo-destination. |
Turn raw facts about a place into a JSON file matching
boilerplates/destination.json. Destination pages target "X things to do
in Y" / "best time to visit Y" search intent and cross-link to tours,
guides, and articles set there.
Use whatever the user supplied (location, best time to visit, altitude if relevant, what tours operate there). Ask if the description content is too thin to write a genuine page.
Read boilerplates/destination.json for the exact field shape.
Strip all _note* keys. Respect these hard DB limits — note destination
SEO limits differ from Tour/Guide/Article:
| Field | Model limit | SEO target |
|---|---|---|
name | 200 chars | |
location_name | 200 chars | |
altitude | 50 chars | |
best_time_to_visit | 200 chars | |
seo.meta_title | 100 chars (not 60 — Destination model differs from Tour/Guide) | keep it tight anyway, ~60 for SERP display, the extra room is a buffer not an invitation to pad |
seo.meta_description | no hard DB limit (TextField) | target under 155 for SERP display regardless |
seo.focus_keyword | 100 chars | e.g. "best time to visit Serengeti" |
FAQ question | 255 chars | |
gallery alt_text | 200 chars |
SEO writing rules:
short_description feeds list views and can double as a meta description fallback — make it stand alone, not a teaser cut off mid-sentence.faqs[]: write these as actual PAA (People Also Ask) targets — phrase questions the way people search them.related_tours/related_guides/related_articles: only reference slugs that already exist; this is the cross-linking mesh for the location."slug": "" unless updating an existing legacy URL.Count characters yourself on meta_title (100) and check meta_description
reads well under ~155 chars even though the DB won't reject longer.
Write the finished JSON to boilerplates/generated/<slug-or-name>.json.
Tell the user: