メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cleven12/visit_kili_v2_cms --skill seo-faqコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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 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.
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-faq |
| description | 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. |
Turn a list of customer questions/topics into a JSON array matching
boilerplates/faq.json. FAQs feed the site's FAQPage JSON-LD schema
(see FAQ.get_faq_page_schema in apps/core/models.py), so answers are
read by Google directly — write them as standalone, complete answers, not
teasers pointing elsewhere.
Use whatever questions/topics the user supplied. If they just gave a topic area (e.g. "payment questions"), draft the most commonly-asked real questions in that area rather than inventing edge cases nobody asks.
Read boilerplates/faq.json for the exact field shape — it's a flat
array, no seo sub-object, no slugs.
Respect this DB limit:
| Field | Model limit |
|---|---|
question | 255 chars |
answer | no hard limit (TextField, supports HTML via CKEditor) |
Rules:
question: phrase exactly as a customer would type/ask it — this is what gets matched to search queries and voice search.answer: answer fully and directly in the first sentence, then add detail. Google's FAQ rich results often only show the first portion.order: sequence logically (booking → payment → on-trek → after-trek), continuing from existing FAQ order if known.is_active: default true.Write the finished JSON array to boilerplates/generated/faq-<topic>.json.
Tell the user:
question text (not a slug) — re-importing with the same question text updates it instead of duplicating. There's no dry-run preview on this importer, so review the file before uploading.