[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASJ8CGF4MN0T8J2ECN6041":3,"skill-same:01M7ASJ8CGF4MN0T8J2ECN6041":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASJ8CGF4MN0T8J2ECN6041","travel-groups-long-term-travel-and-handling-disruption",null,"Use for group dynamics, extended trips, and the moment a plan breaks: travelling with others and negotiating pace and money, long-term travel including logistics, burnout and residency and tax edges, and handling disruption — cancellations, missed connections, denied boarding and what your actual rights and best moves are.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftrip-planning-and-travel-strategies\u002Fskills\u002Ftravel-groups-long-term-travel-and-handling-disruption\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: travel-groups-long-term-travel-and-handling-disruption\ndescription: \"Use for group dynamics, extended trips, and the moment a plan breaks: travelling with others and negotiating pace and money, long-term travel including logistics, burnout and residency and tax edges, and handling disruption — cancellations, missed connections, denied boarding and what your actual rights and best moves are.\"\n---\n\n# Travel Planning: Travelling With Others, Long-Term Travel, and Handling Disruption\n\n> **Part 5 of 6** of the *Trip Planning and Travel Strategies* reference (plugin `trip-planning-and-travel-strategies`), covering §23–§25. Sibling skills: `travel-trip-type-destination-constraints-and-budget` (§0–§5), `travel-airfare-flights-points-accommodation-and-booking-order` (§6–§11), `travel-documents-insurance-health-safety-and-money` (§12–§16), `travel-pacing-packing-jet-lag-connectivity-and-culture` (§17–§22), `travel-reference` (§26–§31). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The craft is stable. Two areas moved. See §26 → `travel-reference` for the EU border systems (EES and ETIAS), and EU air passenger rights.\n\n> **⚠️ The failure modes of travel are almost never the destination. They are PACING,\n> CONSTRAINTS and DISRUPTION** (§1 → `travel-trip-type-destination-constraints-and-budget`, §17 → `travel-pacing-packing-jet-lag-connectivity-and-culture`, §25). ⚠️ **Most disappointing trips were\n> over-scheduled, planned around a fantasy version of the traveller, or derailed by a\n> single failure with no slack behind it.**\n>\n> **Complements a rail reference (ground transport), a refrigeration\u002Ffood reference (food\n> and water safety), and a family\u002Fcommunity reference (§23's group dynamics).**\n>\n> **⚠️ GOTCHA** boxes mark the expensive assumptions and the advice that's confidently\n> wrong.\n>\n> **⚠️ Note on scope**: ⚠️ **entry requirements, visas and insurance terms are\n> jurisdiction-specific, change frequently, and are ultimately determined by the\n> destination's authorities and your carrier — treat §12 → `travel-documents-insurance-health-safety-and-money` as a framework for what to check,\n> never as the answer.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ Plan constraints FIRST, destinations second** (§3 → `travel-trip-type-destination-constraints-and-budget`). **Time, money, energy,\n>    companions and season determine what is actually possible; picking a destination\n>    first and then discovering it doesn't fit is the common sequence and the wrong one.**\n> 2. **⚠️ Under-schedule** (§17 → `travel-pacing-packing-jet-lag-connectivity-and-culture`). **The single most reliable improvement to any itinerary\n>    is removing things from it.**\n> 3. **⚠️ Optimize for RECOVERY, not for the plan** (§25). **The travellers who have good\n>    trips aren't the ones nothing goes wrong for — they're the ones with slack, backups\n>    and documentation.**\n\n---\n\n## §23. Travelling With Others\n\n**⚠️ The most common source of trip conflict is unstated mismatched expectations** (§1 → `travel-trip-type-destination-constraints-and-budget`).\n**⚠️ Talk about it BEFORE booking**: ⚠️ **what kind of trip each person wants, budget level\nhonestly stated, pace, morning versus evening people, how much together-time versus\nseparate-time, and how decisions get made.**\n**⚠️ The practices that work**: ⚠️ **explicit permission to split up (⚠️ genuinely the\nsingle best group-travel technique), one person owning each logistical domain rather than\ndeciding everything by committee, and a shared expense-splitting method agreed up front.**\n**⚠️ Family travel**: ⚠️ **children's pace is the actual constraint; build in downtime and\nplayground time; ⚠️ and jet lag with young children is harder than the adult version.**\n**⚠️ Accessibility travel** requires much more verification and much earlier: ⚠️ **\"accessible\"\nis defined inconsistently, and photographs and direct questions beat labels.**\n\n---\n\n## §24. Long-Term Travel\n\n**⚠️ The differences from a holiday are structural, not just longer**: ⚠️ **you must build\nroutine, rest and boredom into it, because sustained novelty is exhausting.**\n**⚠️ Slower is cheaper**: ⚠️ **weekly and monthly accommodation rates drop substantially,\nand moving less is both the cheaper and the more restful choice.**\n**⚠️ The administrative layer people underestimate**: ⚠️ **visa runs and the legal limits on\nthem; ⚠️ tax residency, which is a genuine issue and jurisdiction-specific; ⚠️ mail and\nbanking address requirements; and ⚠️ whether remote work is actually permitted on your\nentry status — many tourist entries prohibit it, and digital nomad visas exist precisely\nbecause of this.**\n**⚠️ Health and insurance** need long-term-specific policies (§13 → `travel-documents-insurance-health-safety-and-money`).\n**⚠️ The social cost is the one that surprises people** — ⚠️ **repeated shallow connections\nare not a substitute for durable ones** (see a family\u002Fcommunity reference).\n\n---\n\n## §25. ⚠️ Handling Disruption\n\n> **⚠️ This is the skill that separates travellers who have good trips from those who\n> don't, and it's mostly preparation rather than temperament.**\n```\n⚠️ BEFORE  ⚠️ build slack (§17) · ⚠️ documents and bookings offline\n   (§12) · ⚠️ know your rights on the route you're flying (§26.2) ·\n   ⚠️ have the airline's app AND a phone number · ⚠️ know your\n   insurance claim process before you need it\n⚠️ DURING A FLIGHT DISRUPTION\n   ⚠️ 1. Get in the rebooking queue AND call simultaneously —\n      ⚠️ phone lines (including foreign-language ones for the same\n      airline) are often much faster than the desk\n   ⚠️ 2. Know what you want before you reach an agent — specific\n      alternative flights, not \"what can you do\"\n   ⚠️ 3. ⚠️ DOCUMENT EVERYTHING: photograph departure boards,\n      keep boarding passes, note names and times, get the\n      REASON for the delay in writing if you can\n   ⚠️ 4. Ask about care obligations (meals, hotel) separately from\n      compensation — they're different entitlements\n   ⚠️ 5. ⚠️ Keep receipts\n⚠️ AFTER  ⚠️ claim directly first (free) before using a claims agency\n   (which takes a cut); ⚠️ escalate to the national enforcement body\n   if refused\n```\n**⚠️ The general principle**: ⚠️ **be the person the agent wants to help.** **Calm,\nspecific, prepared and polite outperforms angry, reliably** — ⚠️ **the agent did not cause\nthe problem and has discretion they will not exercise for someone shouting at them.**\n**⚠️ Lost baggage**: ⚠️ **file the report BEFORE leaving the airport; keep the reference;\nknow the Montreal Convention liability limit applies internationally; and ⚠️ AirTag-type\ntrackers have proven genuinely useful for locating bags airlines say they cannot find.**\n","# Travel Planning: Travelling With Others, Long-Term Travel, and Handling Disruption\n\n> **Part 5 of 6** of the *Trip Planning and Travel Strategies* reference (plugin `trip-planning-and-travel-strategies`), covering §23–§25. Sibling skills: `travel-trip-type-destination-constraints-and-budget` (§0–§5), `travel-airfare-flights-points-accommodation-and-booking-order` (§6–§11), `travel-documents-insurance-health-safety-and-money` (§12–§16), `travel-pacing-packing-jet-lag-connectivity-and-culture` (§17–§22), `travel-reference` (§26–§31). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The craft is stable. Two areas moved. See §26 → `travel-reference` for the EU border systems (EES and ETIAS), and EU air passenger rights.\n\n> **⚠️ The failure modes of travel are almost never the destination. They are PACING,\n> CONSTRAINTS and DISRUPTION** (§1 → `travel-trip-type-destination-constraints-and-budget`, §17 → `travel-pacing-packing-jet-lag-connectivity-and-culture`, §25). ⚠️ **Most disappointing trips were\n> over-scheduled, planned around a fantasy version of the traveller, or derailed by a\n> single failure with no slack behind it.**\n>\n> **Complements a rail reference (ground transport), a refrigeration\u002Ffood reference (food\n> and water safety), and a family\u002Fcommunity reference (§23's group dynamics).**\n>\n> **⚠️ GOTCHA** boxes mark the expensive assumptions and the advice that's confidently\n> wrong.\n>\n> **⚠️ Note on scope**: ⚠️ **entry requirements, visas and insurance terms are\n> jurisdiction-specific, change frequently, and are ultimately determined by the\n> destination's authorities and your carrier — treat §12 → `travel-documents-insurance-health-safety-and-money` as a framework for what to check,\n> never as the answer.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ Plan constraints FIRST, destinations second** (§3 → `travel-trip-type-destination-constraints-and-budget`). **Time, money, energy,\n>    companions and season determine what is actually possible; picking a destination\n>    first and then discovering it doesn't fit is the common sequence and the wrong one.**\n> 2. **⚠️ Under-schedule** (§17 → `travel-pacing-packing-jet-lag-connectivity-and-culture`). **The single most reliable improvement to any itinerary\n>    is removing things from it.**\n> 3. **⚠️ Optimize for RECOVERY, not for the plan** (§25). **The travellers who have good\n>    trips aren't the ones nothing goes wrong for — they're the ones with slack, backups\n>    and documentation.**\n\n---\n\n## §23. Travelling With Others\n\n**⚠️ The most common source of trip conflict is unstated mismatched expectations** (§1 → `travel-trip-type-destination-constraints-and-budget`).\n**⚠️ Talk about it BEFORE booking**: ⚠️ **what kind of trip each person wants, budget level\nhonestly stated, pace, morning versus evening people, how much together-time versus\nseparate-time, and how decisions get made.**\n**⚠️ The practices that work**: ⚠️ **explicit permission to split up (⚠️ genuinely the\nsingle best group-travel technique), one person owning each logistical domain rather than\ndeciding everything by committee, and a shared expense-splitting method agreed up front.**\n**⚠️ Family travel**: ⚠️ **children's pace is the actual constraint; build in downtime and\nplayground time; ⚠️ and jet lag with young children is harder than the adult version.**\n**⚠️ Accessibility travel** requires much more verification and much earlier: ⚠️ **\"accessible\"\nis defined inconsistently, and photographs and direct questions beat labels.**\n\n---\n\n## §24. Long-Term Travel\n\n**⚠️ The differences from a holiday are structural, not just longer**: ⚠️ **you must build\nroutine, rest and boredom into it, because sustained novelty is exhausting.**\n**⚠️ Slower is cheaper**: ⚠️ **weekly and monthly accommodation rates drop substantially,\nand moving less is both the cheaper and the more restful choice.**\n**⚠️ The administrative layer people underestimate**: ⚠️ **visa runs and the legal limits on\nthem; ⚠️ tax residency, which is a genuine issue and jurisdiction-specific; ⚠️ mail and\nbanking address requirements; and ⚠️ whether remote work is actually permitted on your\nentry status — many tourist entries prohibit it, and digital nomad visas exist precisely\nbecause of this.**\n**⚠️ Health and insurance** need long-term-specific policies (§13 → `travel-documents-insurance-health-safety-and-money`).\n**⚠️ The social cost is the one that surprises people** — ⚠️ **repeated shallow connections\nare not a substitute for durable ones** (see a family\u002Fcommunity reference).\n\n---\n\n## §25. ⚠️ Handling Disruption\n\n> **⚠️ This is the skill that separates travellers who have good trips from those who\n> don't, and it's mostly preparation rather than temperament.**\n```\n⚠️ BEFORE  ⚠️ build slack (§17) · ⚠️ documents and bookings offline\n   (§12) · ⚠️ know your rights on the route you're flying (§26.2) ·\n   ⚠️ have the airline's app AND a phone number · ⚠️ know your\n   insurance claim process before you need it\n⚠️ DURING A FLIGHT DISRUPTION\n   ⚠️ 1. Get in the rebooking queue AND call simultaneously —\n      ⚠️ phone lines (including foreign-language ones for the same\n      airline) are often much faster than the desk\n   ⚠️ 2. Know what you want before you reach an agent — specific\n      alternative flights, not \"what can you do\"\n   ⚠️ 3. ⚠️ DOCUMENT EVERYTHING: photograph departure boards,\n      keep boarding passes, note names and times, get the\n      REASON for the delay in writing if you can\n   ⚠️ 4. Ask about care obligations (meals, hotel) separately from\n      compensation — they're different entitlements\n   ⚠️ 5. ⚠️ Keep receipts\n⚠️ AFTER  ⚠️ claim directly first (free) before using a claims agency\n   (which takes a cut); ⚠️ escalate to the national enforcement body\n   if refused\n```\n**⚠️ The general principle**: ⚠️ **be the person the agent wants to help.** **Calm,\nspecific, prepared and polite outperforms angry, reliably** — ⚠️ **the agent did not cause\nthe problem and has discretion they will not exercise for someone shouting at them.**\n**⚠️ Lost baggage**: ⚠️ **file the report BEFORE leaving the airport; keep the reference;\nknow the Montreal Convention liability limit applies internationally; and ⚠️ AirTag-type\ntrackers have proven genuinely useful for locating bags airlines say they cannot find.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftrip-planning-and-travel-strategies\u002Fskills\u002Ftravel-groups-long-term-travel-and-handling-disruption",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill travel-groups-long-term-travel-and-handling-disruption",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill travel-groups-long-term-travel-and-handling-disruption",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill travel-groups-long-term-travel-and-handling-disruption","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Ftrip-planning-and-travel-strategies\u002Fskills\u002Ftravel-groups-long-term-travel-and-handling-disruption\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]