[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS9EWET9GXP9R2KK29S5DF":3,"skill-same:01M7AS9EWET9GXP9R2KK29S5DF":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},"01M7AS9EWET9GXP9R2KK29S5DF","space-attitude-propulsion-and-edl",null,"Use when working on pointing, orbit maintenance, or getting to a surface: attitude determination and control (sensors, reaction wheels, momentum management, thrusters) and in-space propulsion including electric propulsion trade-offs, and entry, descent and landing — the entry corridor, aeroshells and heating, parachutes and terminal descent, and surface operations.","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\u002Fspace-exploration\u002Fskills\u002Fspace-attitude-propulsion-and-edl\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: space-attitude-propulsion-and-edl\ndescription: \"Use when working on pointing, orbit maintenance, or getting to a surface: attitude determination and control (sensors, reaction wheels, momentum management, thrusters) and in-space propulsion including electric propulsion trade-offs, and entry, descent and landing — the entry corridor, aeroshells and heating, parachutes and terminal descent, and surface operations.\"\n---\n\n# Space Exploration: Attitude Control, In-Space Propulsion, and Entry, Descent and Landing\n\n> **Part 3 of 5** of the *Space Exploration* reference (plugin `space-exploration`), covering §7–§8. Sibling skills: `space-mission-architecture-and-trajectory` (§0–§2), `space-power-thermal-comms-and-navigation` (§3–§6), `space-human-factors-life-support-and-reliability` (§9–§14), `space-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The physics and subsystem engineering are stable; radiation dose limits and ISRU and life-support performance have real recent data. See §17 → `space-reference` for what is genuinely open.\n\n> **How to read this.** The engineering of getting somewhere and doing something once\n> you're there. **Launch, staging, orbital mechanics and reentry heating physics are\n> covered in a rocket-science reference** — this document assumes them and points there\n> rather than duplicating. **Flight software practice** sits in a robotics-software\n> reference (§14 there).\n>\n> Two markers:\n> - **[DURABLE]** — physics, subsystem engineering, and design constraints. Most of this.\n> - **[CONTESTED]** — genuine disagreement about approach.\n>\n> **⚠️ GOTCHA** boxes mark where a mission has died, or where the constraint is harder\n> than it looks.\n>\n> **The three constraints that generate every mission design:**\n> 1. **⚠️ Mass is the currency and everything converts to it.** Power converts to mass\n>    (arrays, radioisotopes, radiators). Data rate converts to mass (antenna, power).\n>    Reliability converts to mass (redundancy). Crew time converts to mass (consumables).\n>    **You are always spending the same budget** (§1.3 → `space-mission-architecture-and-trajectory`).\n> 2. **Distance imposes latency and darkness.** Light-time makes teleoperation impossible\n>    beyond the Moon, forcing autonomy (§6 → `space-power-thermal-comms-and-navigation`); inverse-square makes both sunlight and\n>    signal scarce (§3 → `space-power-thermal-comms-and-navigation`, §5 → `space-power-thermal-comms-and-navigation`).\n> 3. **⚠️ For crewed deep space, the binding constraint is not propulsion — it's human\n>    physiology.** Radiation dose and microgravity deconditioning bound mission duration\n>    more tightly than Δv does (§9 → `space-human-factors-life-support-and-reliability`).\n\n---\n\n## §7. Attitude Control and In-Space Propulsion\n\n**Attitude sensing**: star trackers (best, arcsecond-class), sun sensors, horizon sensors,\nmagnetometers (LEO only), gyros.\n\n**Actuation**: **reaction wheels** (⚠️ **precise, but they saturate and must be\ndesaturated — and wheel failure has crippled missions; Kepler and Hayabusa both lost\nwheels**), **control moment gyros** (higher torque, used on ISS), **thrusters** (fast,\nconsume propellant), **magnetorquers** (LEO only), **spin stabilization** (⚠️ **simple and\nrobust, at the cost of pointing flexibility**), **gravity-gradient**, and\n⚠️ **solar radiation pressure**, which Kepler used as a virtual third wheel after two\nfailed — a genuinely elegant recovery.\n\n**In-space propulsion:**\n\n| Type | Isp (s) | Use |\n|---|---|---|\n| **Cold gas** | 50–70 | Simple, small ΔV, contamination-free |\n| **Monopropellant (hydrazine)** | 220–235 | ⚠️ **The RCS workhorse** |\n| **Bipropellant (MMH\u002FNTO)** | 300–330 | Orbit insertion, hypergolic and storable |\n| **Solid** | 280–300 | Single-burn kick stages |\n| **Hall thruster** | 1,500–2,500 | ⚠️ **Station-keeping and orbit raising, now standard** |\n| **Gridded ion** | 3,000–4,000 | ⚠️ **Dawn visited two main-belt bodies — impossible chemically** |\n| **Solar sail** | ∞ | No propellant; tiny thrust |\n\n**⚠️ The electric propulsion trade, stated properly**: 10× the Isp means ~1\u002F10 the\npropellant for the same Δv, **but thrust is millinewtons, so burns last months and the\npower system must be sized to feed it** — the mass moves from the propellant tank to the\nsolar arrays. **It wins when the mission has time and the Δv is large.**\n\n**Station-keeping**: **GEO needs ~50 m\u002Fs\u002Fyr** (north-south dominates, against lunisolar\nperturbations); **LEO drag makeup**; **halo orbits need small but continual maintenance**\nbecause they're unstable.\n\n---\n\n## §8. EDL and Surface Operations\n\n**[DURABLE] Entry heating physics is in a rocket-science reference §12. What matters here\nis the sequence and why it's hard.**\n\n**⚠️ Mars EDL is the canonical hard case, and the reason is a genuine physical squeeze:**\nthe atmosphere is **~1% of Earth's** — thick enough to demand a heat shield, **too thin to\nslow you to safe landing speed with parachutes alone.** Venus and Titan are easier\n(dense atmospheres); the Moon and asteroids are easier (no atmosphere, pure propulsive).\n\n**The Mars sequence, roughly seven minutes:**\n```\nEntry interface (~125 km, ~5.5–7.5 km\u002Fs)\n  → peak heating (~100 s), peak deceleration (~8–15 g)\n    → supersonic parachute deploy (Mach 1.5–2.2, ~10 km)   ⚠️ narrow box\n      → heat shield jettison → radar\u002FTRN acquisition\n        → backshell separation → powered descent\n          → touchdown: legs, airbags, or sky crane\n```\n**⚠️ Everything is autonomous** (§5.3 → `space-power-thermal-comms-and-navigation`) — the vehicle has landed or crashed before the\nfirst telemetry arrives.\n\n**Landing methods and their regimes**: **airbags** (Pathfinder, MER — ⚠️ **mass-efficient\nbut caps landed mass around a few hundred kg and requires benign terrain**), **legs**\n(Viking, Phoenix, InSight — ⚠️ **engine plume excavates regolith and can contaminate\nsamples**), **sky crane** (MSL, Perseverance — ⚠️ **bizarre-looking and the correct answer\nfor ~1-tonne rovers: it keeps the engines away from the surface and puts the wheels down\ndirectly**).\n\n**⚠️ The landed-mass ceiling**: Mars EDL has historically capped landed mass near\n**~1 tonne**, because parachute area scales badly and supersonic retropropulsion was\nunproven. **Scaling past it requires either much larger decelerators or supersonic\nretropropulsion**, which is the central open EDL problem (§17 → `space-reference`).\n\n**Surface operations**: **mobility** (rocker-bogie suspension — ⚠️ **passively keeps six\nwheels loaded on rough terrain, no active control**), ⚠️ **wheel wear**, which was a real\nmission-shaping problem for Curiosity, **dust** (⚠️ **abrasive, electrostatic, and\nmission-ending for solar-powered landers**), **thermal cycling**, **sample acquisition**\n(drilling in vacuum or low gravity is genuinely hard — ⚠️ **InSight's mole failed because\nMartian regolith didn't provide expected friction**), and **traverse planning** under\nlight-time (§6.2 → `space-power-thermal-comms-and-navigation`).\n","# Space Exploration: Attitude Control, In-Space Propulsion, and Entry, Descent and Landing\n\n> **Part 3 of 5** of the *Space Exploration* reference (plugin `space-exploration`), covering §7–§8. Sibling skills: `space-mission-architecture-and-trajectory` (§0–§2), `space-power-thermal-comms-and-navigation` (§3–§6), `space-human-factors-life-support-and-reliability` (§9–§14), `space-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The physics and subsystem engineering are stable; radiation dose limits and ISRU and life-support performance have real recent data. See §17 → `space-reference` for what is genuinely open.\n\n> **How to read this.** The engineering of getting somewhere and doing something once\n> you're there. **Launch, staging, orbital mechanics and reentry heating physics are\n> covered in a rocket-science reference** — this document assumes them and points there\n> rather than duplicating. **Flight software practice** sits in a robotics-software\n> reference (§14 there).\n>\n> Two markers:\n> - **[DURABLE]** — physics, subsystem engineering, and design constraints. Most of this.\n> - **[CONTESTED]** — genuine disagreement about approach.\n>\n> **⚠️ GOTCHA** boxes mark where a mission has died, or where the constraint is harder\n> than it looks.\n>\n> **The three constraints that generate every mission design:**\n> 1. **⚠️ Mass is the currency and everything converts to it.** Power converts to mass\n>    (arrays, radioisotopes, radiators). Data rate converts to mass (antenna, power).\n>    Reliability converts to mass (redundancy). Crew time converts to mass (consumables).\n>    **You are always spending the same budget** (§1.3 → `space-mission-architecture-and-trajectory`).\n> 2. **Distance imposes latency and darkness.** Light-time makes teleoperation impossible\n>    beyond the Moon, forcing autonomy (§6 → `space-power-thermal-comms-and-navigation`); inverse-square makes both sunlight and\n>    signal scarce (§3 → `space-power-thermal-comms-and-navigation`, §5 → `space-power-thermal-comms-and-navigation`).\n> 3. **⚠️ For crewed deep space, the binding constraint is not propulsion — it's human\n>    physiology.** Radiation dose and microgravity deconditioning bound mission duration\n>    more tightly than Δv does (§9 → `space-human-factors-life-support-and-reliability`).\n\n---\n\n## §7. Attitude Control and In-Space Propulsion\n\n**Attitude sensing**: star trackers (best, arcsecond-class), sun sensors, horizon sensors,\nmagnetometers (LEO only), gyros.\n\n**Actuation**: **reaction wheels** (⚠️ **precise, but they saturate and must be\ndesaturated — and wheel failure has crippled missions; Kepler and Hayabusa both lost\nwheels**), **control moment gyros** (higher torque, used on ISS), **thrusters** (fast,\nconsume propellant), **magnetorquers** (LEO only), **spin stabilization** (⚠️ **simple and\nrobust, at the cost of pointing flexibility**), **gravity-gradient**, and\n⚠️ **solar radiation pressure**, which Kepler used as a virtual third wheel after two\nfailed — a genuinely elegant recovery.\n\n**In-space propulsion:**\n\n| Type | Isp (s) | Use |\n|---|---|---|\n| **Cold gas** | 50–70 | Simple, small ΔV, contamination-free |\n| **Monopropellant (hydrazine)** | 220–235 | ⚠️ **The RCS workhorse** |\n| **Bipropellant (MMH\u002FNTO)** | 300–330 | Orbit insertion, hypergolic and storable |\n| **Solid** | 280–300 | Single-burn kick stages |\n| **Hall thruster** | 1,500–2,500 | ⚠️ **Station-keeping and orbit raising, now standard** |\n| **Gridded ion** | 3,000–4,000 | ⚠️ **Dawn visited two main-belt bodies — impossible chemically** |\n| **Solar sail** | ∞ | No propellant; tiny thrust |\n\n**⚠️ The electric propulsion trade, stated properly**: 10× the Isp means ~1\u002F10 the\npropellant for the same Δv, **but thrust is millinewtons, so burns last months and the\npower system must be sized to feed it** — the mass moves from the propellant tank to the\nsolar arrays. **It wins when the mission has time and the Δv is large.**\n\n**Station-keeping**: **GEO needs ~50 m\u002Fs\u002Fyr** (north-south dominates, against lunisolar\nperturbations); **LEO drag makeup**; **halo orbits need small but continual maintenance**\nbecause they're unstable.\n\n---\n\n## §8. EDL and Surface Operations\n\n**[DURABLE] Entry heating physics is in a rocket-science reference §12. What matters here\nis the sequence and why it's hard.**\n\n**⚠️ Mars EDL is the canonical hard case, and the reason is a genuine physical squeeze:**\nthe atmosphere is **~1% of Earth's** — thick enough to demand a heat shield, **too thin to\nslow you to safe landing speed with parachutes alone.** Venus and Titan are easier\n(dense atmospheres); the Moon and asteroids are easier (no atmosphere, pure propulsive).\n\n**The Mars sequence, roughly seven minutes:**\n```\nEntry interface (~125 km, ~5.5–7.5 km\u002Fs)\n  → peak heating (~100 s), peak deceleration (~8–15 g)\n    → supersonic parachute deploy (Mach 1.5–2.2, ~10 km)   ⚠️ narrow box\n      → heat shield jettison → radar\u002FTRN acquisition\n        → backshell separation → powered descent\n          → touchdown: legs, airbags, or sky crane\n```\n**⚠️ Everything is autonomous** (§5.3 → `space-power-thermal-comms-and-navigation`) — the vehicle has landed or crashed before the\nfirst telemetry arrives.\n\n**Landing methods and their regimes**: **airbags** (Pathfinder, MER — ⚠️ **mass-efficient\nbut caps landed mass around a few hundred kg and requires benign terrain**), **legs**\n(Viking, Phoenix, InSight — ⚠️ **engine plume excavates regolith and can contaminate\nsamples**), **sky crane** (MSL, Perseverance — ⚠️ **bizarre-looking and the correct answer\nfor ~1-tonne rovers: it keeps the engines away from the surface and puts the wheels down\ndirectly**).\n\n**⚠️ The landed-mass ceiling**: Mars EDL has historically capped landed mass near\n**~1 tonne**, because parachute area scales badly and supersonic retropropulsion was\nunproven. **Scaling past it requires either much larger decelerators or supersonic\nretropropulsion**, which is the central open EDL problem (§17 → `space-reference`).\n\n**Surface operations**: **mobility** (rocker-bogie suspension — ⚠️ **passively keeps six\nwheels loaded on rough terrain, no active control**), ⚠️ **wheel wear**, which was a real\nmission-shaping problem for Curiosity, **dust** (⚠️ **abrasive, electrostatic, and\nmission-ending for solar-powered landers**), **thermal cycling**, **sample acquisition**\n(drilling in vacuum or low gravity is genuinely hard — ⚠️ **InSight's mole failed because\nMartian regolith didn't provide expected friction**), and **traverse planning** under\nlight-time (§6.2 → `space-power-thermal-comms-and-navigation`).\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fspace-exploration\u002Fskills\u002Fspace-attitude-propulsion-and-edl",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 space-attitude-propulsion-and-edl",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill space-attitude-propulsion-and-edl",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill space-attitude-propulsion-and-edl","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fspace-exploration\u002Fskills\u002Fspace-attitude-propulsion-and-edl\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",[],[]]