[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APT0R6AF6BH41GFTZ603QQ":3,"skill-same:01M7APT0R6AF6BH41GFTZ603QQ":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},"01M7APT0R6AF6BH41GFTZ603QQ","drugdev-protein-structure-docking-and-molecular-dynamics",null,"Use for structure-based work: protein structure and what a crystal structure does and does not tell you, structure prediction and how to read a confidence score, docking and the gap between pose prediction and affinity ranking, molecular dynamics with force fields and sampling limits, and free energy methods including FEP and where the accuracy actually is.","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\u002Fmedicine-design-software-development\u002Fskills\u002Fdrugdev-protein-structure-docking-and-molecular-dynamics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: drugdev-protein-structure-docking-and-molecular-dynamics\ndescription: \"Use for structure-based work: protein structure and what a crystal structure does and does not tell you, structure prediction and how to read a confidence score, docking and the gap between pose prediction and affinity ranking, molecular dynamics with force fields and sampling limits, and free energy methods including FEP and where the accuracy actually is.\"\n---\n\n# Drug Discovery Software: Protein Structure, Structure Prediction, Docking, Molecular Dynamics, and Free Energy Methods\n\n> **Part 3 of 6** of the *Medicine Design Software Development* reference (plugin `medicine-design-software-development`), covering §8–§12. Sibling skills: `drugdev-pipeline-targets-and-drug-likeness` (§0–§3), `drugdev-representation-cheminformatics-data-quality-and-leakage` (§4–§7), `drugdev-qsar-admet-generative-models-and-validation` (§13–§18), `drugdev-pipeline-engineering-compute-and-regulated-software` (§19–§23), `drugdev-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The chemistry and physics are stable. Two areas moved. See §24 → `drugdev-reference` for the AI drug discovery clinical evidence, and the FDA and EMA regulatory framework for AI.\n\n> **⚠️ Written for software engineers entering computational drug discovery — a domain\n> where the code is easy and the EVALUATION is brutally hard.** ⚠️ **You can build a\n> molecular property predictor in an afternoon and get a beautiful R². It will very\n> probably be measuring leakage, not chemistry** (§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`).\n>\n> **Complements an AI\u002FML reference (model architectures), a healthcare\u002Fclinical reference\n> (the trial end), and a scientific-computing reference (HPC and reproducibility).**\n>\n> **⚠️ GOTCHA** boxes mark the evaluation traps and the places where a correct-looking\n> result is meaningless.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ The bottleneck is BIOLOGY, not compute** (§1 → `drugdev-pipeline-targets-and-drug-likeness`, §24.1 → `drugdev-reference`). **Roughly 90% of candidates\n>    entering clinical trials fail, mostly for efficacy and toxicity reasons that appear\n>    only in humans — and no amount of upstream modelling has yet moved that number.**\n> 2. **⚠️ Random train\u002Ftest splits are almost always WRONG here** (§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`). **Chemical data is\n>    clustered into analogue series, so random splitting tests interpolation within a\n>    series and reports it as generalization. This is the field's defining methodological\n>    failure.**\n> 3. **⚠️ Prediction is cheap; VALIDATION is the product** (§18 → `drugdev-qsar-admet-generative-models-and-validation`, §24.2 → `drugdev-reference`). **In a regulated\n>    context, an unvalidated model is not evidence — the FDA framework is explicitly about\n>    credibility for a stated context of use, not about accuracy in the abstract.**\n\n---\n\n## §8. Protein Structure\n\n**⚠️ Primary → secondary → tertiary → quaternary; ⚠️ the PDB as the experimental\nrepository (X-ray, cryo-EM, NMR).**\n**⚠️ What a crystallographer knows and a software engineer often doesn't:**\n⚠️ **RESOLUTION and B-factors indicate reliability — a 3.5 Å structure does not pin down\nside chain positions; ⚠️ crystal structures are one conformational snapshot under\nnon-physiological conditions; ⚠️ hydrogens are usually absent; ⚠️ and missing loops are\ncommon and are often the flexible functionally-important regions.**\n**⚠️ Binding sites**: **orthosteric vs allosteric; ⚠️ cryptic pockets that only open in\ncertain conformations and are invisible in the apo structure; and ⚠️ INDUCED FIT — the\nprotein moves when the ligand binds, which most docking ignores** (§10).\n**⚠️ Water is not a nuisance**: ⚠️ **structured waters mediate binding, and displacing a\nwater has a real free energy cost or gain.**\n\n---\n\n## §9. ⚠️ Structure Prediction\n\n**⚠️ AlphaFold2 and successors were a genuine breakthrough** — ⚠️ **reported pLDDT above 90\nfor well-determined regions, and the AlphaFold DB made predicted structures available at\nproteome scale.** **⚠️ AlphaFold3 and equivalents extend to complexes including\nprotein-ligand.**\n> **⚠️ GOTCHA — \"we solved protein structure\" overstates it in ways that matter for drug\n> design specifically.** ⚠️ **Predicted structures are typically APO-like and represent one\n> conformation; docking into AlphaFold models has repeatedly been shown to perform WORSE\n> than docking into experimental holo structures** — **because side chains in the pocket\n> are not in their ligand-bound arrangement.**\n> **⚠️ pLDDT is a CONFIDENCE score, not an accuracy guarantee, and low-pLDDT regions are\n> frequently intrinsically disordered rather than merely uncertain.**\n> **⚠️ Structure prediction did not solve binding affinity, conformational ensembles, or\n> the effect of mutations on function.**\n\n---\n\n## §10. ⚠️ Docking\n\n**⚠️ Predicts a binding POSE and scores it. Understand what each half can do.**\n```\n⚠️ POSE PREDICTION  ⚠️ reasonably good — often gets a near-native pose\n   in the top ranks for well-behaved systems\n⚠️ SCORING \u002F AFFINITY RANKING  ⚠️ POOR. ⚠️ Docking scores correlate\n   weakly with measured affinity, and this has been true for decades\n   despite continuous effort\n⚠️ THEREFORE  use docking to ENRICH and TRIAGE, never to rank a\n   final series or to claim a predicted potency\n```\n**⚠️ Programs**: **AutoDock Vina (free, widely used), Glide, GOLD, rDock, DiffDock and\nother ML pose predictors** (⚠️ **and note ML docking methods have been criticized for\nbenchmark leakage — the same protein appearing in train and test** — §7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`).\n**⚠️ Practical determinants of whether docking is useful at all**: ⚠️ **protein preparation\n(protonation, tautomers, missing atoms) matters more than the choice of program; ⚠️ the\nligand's protonation state at pH 7.4; ⚠️ receptor flexibility (ensemble docking as a\npartial answer); and ⚠️ a well-chosen box.**\n**⚠️ Virtual screening realities**: ⚠️ **enrichment factors matter more than hit rate;\ndecoy selection biases benchmarks badly (DUD-E has known artefacts that let models learn\ndecoy properties rather than binding); and ⚠️ ultra-large library screening of billions of\ncompounds is now feasible and shifts the bottleneck to synthesis and assay throughput.**\n\n---\n\n## §11. Molecular Dynamics\n\n**⚠️ Simulating atomic motion under a force field — the tool for questions docking can't\nanswer.**\n**Force fields** (**AMBER, CHARMM, OPLS, and ⚠️ increasingly ML potentials**), **and\n⚠️ the ligand parameterization problem: proteins are well-parameterized, arbitrary small\nmolecules are not, and bad ligand parameters invalidate the whole simulation.**\n**⚠️ Engines**: **GROMACS, AMBER, OpenMM (⚠️ the most programmable), NAMD, Desmond.**\n**⚠️ The timescale problem is the honest limitation**: ⚠️ **routine simulations reach\nmicroseconds; many biologically relevant motions take milliseconds to seconds.**\n**⚠️ Enhanced sampling (metadynamics, replica exchange, umbrella sampling) exists to\nattack exactly this gap.**\n**⚠️ What MD is genuinely good for**: **binding site flexibility and cryptic pockets,\nwater networks, stability of a docked pose, and generating ensembles for §10.**\n\n---\n\n## §12. Free Energy Methods\n\n**⚠️ The most accurate physics-based affinity predictions available, and the most\nexpensive.**\n```\n⚠️ FEP \u002F TI  alchemical transformation between two ligands.\n   ⚠️ RELATIVE binding free energy is the practical workhorse —\n   reported accuracy often around 1 kcal\u002Fmol for congeneric series\n⚠️ ABFE  absolute binding free energy — harder, less reliable\nMM\u002FPBSA · MM\u002FGBSA  ⚠️ cheaper, much less reliable, and widely\n   over-trusted in the literature\n```\n**⚠️ Where FEP fits in practice**: ⚠️ **lead optimization within a congeneric series where\nyou already have a good structure** — **prioritizing which of 50 analogues to synthesize.**\n**⚠️ It is not a screening tool and it does not rescue a wrong binding mode.**\n**⚠️ 1 kcal\u002Fmol ≈ a factor of ~5 in affinity at room temperature** — ⚠️ **useful context for\nwhat \"accurate to 1 kcal\u002Fmol\" actually buys you.**\n\n---\n\n# PART IV — MACHINE LEARNING\n","# Drug Discovery Software: Protein Structure, Structure Prediction, Docking, Molecular Dynamics, and Free Energy Methods\n\n> **Part 3 of 6** of the *Medicine Design Software Development* reference (plugin `medicine-design-software-development`), covering §8–§12. Sibling skills: `drugdev-pipeline-targets-and-drug-likeness` (§0–§3), `drugdev-representation-cheminformatics-data-quality-and-leakage` (§4–§7), `drugdev-qsar-admet-generative-models-and-validation` (§13–§18), `drugdev-pipeline-engineering-compute-and-regulated-software` (§19–§23), `drugdev-reference` (§24–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The chemistry and physics are stable. Two areas moved. See §24 → `drugdev-reference` for the AI drug discovery clinical evidence, and the FDA and EMA regulatory framework for AI.\n\n> **⚠️ Written for software engineers entering computational drug discovery — a domain\n> where the code is easy and the EVALUATION is brutally hard.** ⚠️ **You can build a\n> molecular property predictor in an afternoon and get a beautiful R². It will very\n> probably be measuring leakage, not chemistry** (§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`).\n>\n> **Complements an AI\u002FML reference (model architectures), a healthcare\u002Fclinical reference\n> (the trial end), and a scientific-computing reference (HPC and reproducibility).**\n>\n> **⚠️ GOTCHA** boxes mark the evaluation traps and the places where a correct-looking\n> result is meaningless.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ The bottleneck is BIOLOGY, not compute** (§1 → `drugdev-pipeline-targets-and-drug-likeness`, §24.1 → `drugdev-reference`). **Roughly 90% of candidates\n>    entering clinical trials fail, mostly for efficacy and toxicity reasons that appear\n>    only in humans — and no amount of upstream modelling has yet moved that number.**\n> 2. **⚠️ Random train\u002Ftest splits are almost always WRONG here** (§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`). **Chemical data is\n>    clustered into analogue series, so random splitting tests interpolation within a\n>    series and reports it as generalization. This is the field's defining methodological\n>    failure.**\n> 3. **⚠️ Prediction is cheap; VALIDATION is the product** (§18 → `drugdev-qsar-admet-generative-models-and-validation`, §24.2 → `drugdev-reference`). **In a regulated\n>    context, an unvalidated model is not evidence — the FDA framework is explicitly about\n>    credibility for a stated context of use, not about accuracy in the abstract.**\n\n---\n\n## §8. Protein Structure\n\n**⚠️ Primary → secondary → tertiary → quaternary; ⚠️ the PDB as the experimental\nrepository (X-ray, cryo-EM, NMR).**\n**⚠️ What a crystallographer knows and a software engineer often doesn't:**\n⚠️ **RESOLUTION and B-factors indicate reliability — a 3.5 Å structure does not pin down\nside chain positions; ⚠️ crystal structures are one conformational snapshot under\nnon-physiological conditions; ⚠️ hydrogens are usually absent; ⚠️ and missing loops are\ncommon and are often the flexible functionally-important regions.**\n**⚠️ Binding sites**: **orthosteric vs allosteric; ⚠️ cryptic pockets that only open in\ncertain conformations and are invisible in the apo structure; and ⚠️ INDUCED FIT — the\nprotein moves when the ligand binds, which most docking ignores** (§10).\n**⚠️ Water is not a nuisance**: ⚠️ **structured waters mediate binding, and displacing a\nwater has a real free energy cost or gain.**\n\n---\n\n## §9. ⚠️ Structure Prediction\n\n**⚠️ AlphaFold2 and successors were a genuine breakthrough** — ⚠️ **reported pLDDT above 90\nfor well-determined regions, and the AlphaFold DB made predicted structures available at\nproteome scale.** **⚠️ AlphaFold3 and equivalents extend to complexes including\nprotein-ligand.**\n> **⚠️ GOTCHA — \"we solved protein structure\" overstates it in ways that matter for drug\n> design specifically.** ⚠️ **Predicted structures are typically APO-like and represent one\n> conformation; docking into AlphaFold models has repeatedly been shown to perform WORSE\n> than docking into experimental holo structures** — **because side chains in the pocket\n> are not in their ligand-bound arrangement.**\n> **⚠️ pLDDT is a CONFIDENCE score, not an accuracy guarantee, and low-pLDDT regions are\n> frequently intrinsically disordered rather than merely uncertain.**\n> **⚠️ Structure prediction did not solve binding affinity, conformational ensembles, or\n> the effect of mutations on function.**\n\n---\n\n## §10. ⚠️ Docking\n\n**⚠️ Predicts a binding POSE and scores it. Understand what each half can do.**\n```\n⚠️ POSE PREDICTION  ⚠️ reasonably good — often gets a near-native pose\n   in the top ranks for well-behaved systems\n⚠️ SCORING \u002F AFFINITY RANKING  ⚠️ POOR. ⚠️ Docking scores correlate\n   weakly with measured affinity, and this has been true for decades\n   despite continuous effort\n⚠️ THEREFORE  use docking to ENRICH and TRIAGE, never to rank a\n   final series or to claim a predicted potency\n```\n**⚠️ Programs**: **AutoDock Vina (free, widely used), Glide, GOLD, rDock, DiffDock and\nother ML pose predictors** (⚠️ **and note ML docking methods have been criticized for\nbenchmark leakage — the same protein appearing in train and test** — §7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`).\n**⚠️ Practical determinants of whether docking is useful at all**: ⚠️ **protein preparation\n(protonation, tautomers, missing atoms) matters more than the choice of program; ⚠️ the\nligand's protonation state at pH 7.4; ⚠️ receptor flexibility (ensemble docking as a\npartial answer); and ⚠️ a well-chosen box.**\n**⚠️ Virtual screening realities**: ⚠️ **enrichment factors matter more than hit rate;\ndecoy selection biases benchmarks badly (DUD-E has known artefacts that let models learn\ndecoy properties rather than binding); and ⚠️ ultra-large library screening of billions of\ncompounds is now feasible and shifts the bottleneck to synthesis and assay throughput.**\n\n---\n\n## §11. Molecular Dynamics\n\n**⚠️ Simulating atomic motion under a force field — the tool for questions docking can't\nanswer.**\n**Force fields** (**AMBER, CHARMM, OPLS, and ⚠️ increasingly ML potentials**), **and\n⚠️ the ligand parameterization problem: proteins are well-parameterized, arbitrary small\nmolecules are not, and bad ligand parameters invalidate the whole simulation.**\n**⚠️ Engines**: **GROMACS, AMBER, OpenMM (⚠️ the most programmable), NAMD, Desmond.**\n**⚠️ The timescale problem is the honest limitation**: ⚠️ **routine simulations reach\nmicroseconds; many biologically relevant motions take milliseconds to seconds.**\n**⚠️ Enhanced sampling (metadynamics, replica exchange, umbrella sampling) exists to\nattack exactly this gap.**\n**⚠️ What MD is genuinely good for**: **binding site flexibility and cryptic pockets,\nwater networks, stability of a docked pose, and generating ensembles for §10.**\n\n---\n\n## §12. Free Energy Methods\n\n**⚠️ The most accurate physics-based affinity predictions available, and the most\nexpensive.**\n```\n⚠️ FEP \u002F TI  alchemical transformation between two ligands.\n   ⚠️ RELATIVE binding free energy is the practical workhorse —\n   reported accuracy often around 1 kcal\u002Fmol for congeneric series\n⚠️ ABFE  absolute binding free energy — harder, less reliable\nMM\u002FPBSA · MM\u002FGBSA  ⚠️ cheaper, much less reliable, and widely\n   over-trusted in the literature\n```\n**⚠️ Where FEP fits in practice**: ⚠️ **lead optimization within a congeneric series where\nyou already have a good structure** — **prioritizing which of 50 analogues to synthesize.**\n**⚠️ It is not a screening tool and it does not rescue a wrong binding mode.**\n**⚠️ 1 kcal\u002Fmol ≈ a factor of ~5 in affinity at room temperature** — ⚠️ **useful context for\nwhat \"accurate to 1 kcal\u002Fmol\" actually buys you.**\n\n---\n\n# PART IV — MACHINE LEARNING\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedicine-design-software-development\u002Fskills\u002Fdrugdev-protein-structure-docking-and-molecular-dynamics",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 drugdev-protein-structure-docking-and-molecular-dynamics",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill drugdev-protein-structure-docking-and-molecular-dynamics",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill drugdev-protein-structure-docking-and-molecular-dynamics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedicine-design-software-development\u002Fskills\u002Fdrugdev-protein-structure-docking-and-molecular-dynamics\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",[],[]]