メニュー
Draft team member bio entries as JSON ready for Admin → Team Members → Import JSON. Use when the user wants guide/staff bios written from raw facts (name, role, experience, summit count), or runs /seo-team-member.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cleven12/visit_kili_v2_cms --skill seo-team-memberコマンドは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 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.
SOC 職業分類に基づく
SKILL.md を表示中
| name | seo-team-member |
| description | Draft team member bio entries as JSON ready for Admin → Team Members → Import JSON. Use when the user wants guide/staff bios written from raw facts (name, role, experience, summit count), or runs /seo-team-member. |
Turn raw facts about a guide/staff member into a JSON array matching
boilerplates/team_member.json. These bios appear on trust-building pages
(About/Team) — there's no seo block on this model, but bios still get
indexed and contribute to E-E-A-T (experience/expertise) signals on tour
and guide pages that reference the author, so write them as real
credentials, not marketing fluff.
Use whatever the user supplied (name, role, years guiding, summits led, certifications, LinkedIn). Don't invent specific numbers (years of experience, summit counts) — ask if not given.
Read boilerplates/team_member.json for the exact field shape.
Respect these DB limits:
| Field | Model limit |
|---|---|
name | 120 chars |
role | 120 chars |
bio | no hard limit (TextField) |
linkedin | must be a valid URL or omitted (URLField) |
years_experience | positive integer |
summits_count | positive integer |
Rules:
bio: 2-4 sentences, lead with their role/credential, not a life story.order: lower numbers show first — ask where in the team list they should appear, or append to the end.is_active: default true.Write the finished JSON array to boilerplates/generated/team-<name>.json.
Tell the user:
name text — re-importing the same name updates it instead of duplicating.photo is a Cloudinary field and isn't set via this importer — upload the photo manually in the admin after import.