[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APSSS2DRTK08KDGRP0EMRP":3,"skill-same:01M7APSSS2DRTK08KDGRP0EMRP":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},"01M7APSSS2DRTK08KDGRP0EMRP","drugdev-pipeline-targets-and-drug-likeness",null,"Use when orienting on a drug discovery project: the pipeline stage by stage with its attrition and where computation actually helps rather than where it is claimed to, targets and modalities from small molecules to biologics and their different constraints, and what makes a molecule a drug — potency, selectivity, exposure and the property filters worth taking seriously. Includes the router for the whole drug discovery software reference.","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-pipeline-targets-and-drug-likeness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: drugdev-pipeline-targets-and-drug-likeness\ndescription: \"Use when orienting on a drug discovery project: the pipeline stage by stage with its attrition and where computation actually helps rather than where it is claimed to, targets and modalities from small molecules to biologics and their different constraints, and what makes a molecule a drug — potency, selectivity, exposure and the property filters worth taking seriously. Includes the router for the whole drug discovery software reference.\"\n---\n\n# Drug Discovery Software: The Pipeline and Where Software Helps, Targets and Modalities, and What Makes a Molecule a Drug\n\n> **Part 1 of 6** of the *Medicine Design Software Development* reference (plugin `medicine-design-software-development`), covering §0–§3. Sibling skills: `drugdev-representation-cheminformatics-data-quality-and-leakage` (§4–§7), `drugdev-protein-structure-docking-and-molecular-dynamics` (§8–§12), `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, §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## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| **⚠️ The pipeline and the attrition** | **§1** |\n| Targets and modalities | §2 |\n| **⚠️ What makes a molecule a drug** | **§3** |\n| **Molecular representation** | **§4 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| Cheminformatics toolkits | §5 → `drugdev-representation-cheminformatics-data-quality-and-leakage` |\n| **⚠️ Data sources and quality** | **§6 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| **⚠️ Splitting and leakage** | **§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| Protein structure | §8 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| **⚠️ Structure prediction** | **§9 → `drugdev-protein-structure-docking-and-molecular-dynamics`** |\n| **⚠️ Docking** | **§10 → `drugdev-protein-structure-docking-and-molecular-dynamics`** |\n| Molecular dynamics | §11 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| Free energy methods | §12 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| QSAR and property prediction | §13 → `drugdev-qsar-admet-generative-models-and-validation` |\n| ADMET | §14 → `drugdev-qsar-admet-generative-models-and-validation` |\n| **Generative models** | **§15 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| Active learning and the DMTA loop | §16 → `drugdev-qsar-admet-generative-models-and-validation` |\n| **⚠️ Benchmarks** | **§17 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| **⚠️ Validation that means something** | **§18 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| Pipeline engineering | §19 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| Compute | §20 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| Reproducibility | §21 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| **⚠️ GxP and validation** | **§22 → `drugdev-pipeline-engineering-compute-and-regulated-software`** |\n| Software as a medical device | §23 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| **What's live** | **§24 → `drugdev-reference`** |\n| Misconceptions, numbers | §25–§26 → `drugdev-reference` |\n| Tools, quick ref, method | §27–§29 → `drugdev-reference` |\n\n---\n\n## §1. ⚠️ The Pipeline and Where Software Helps\n\n```\nTARGET ID → HIT FINDING → HIT-TO-LEAD → LEAD OPTIMIZATION →\nPRECLINICAL → PHASE I → PHASE II → PHASE III → FILING\n⚠️ Reported: 10–15 years and >$1–2B per approved drug\n⚠️ Reported attrition: >10,000 compounds screened → ~1 approved\n⚠️ ~90% of candidates entering clinical trials never gain approval\n```\n> **⚠️ GOTCHA — understand WHERE the failures happen or you will optimize the wrong\n> thing.** ⚠️ **The dominant clinical failure modes are lack of EFFICACY (reported around\n> 40–50%) and TOXICITY (reported around 30%)** — **and both are properties of the BIOLOGY\n> and the human system, not of the molecule's binding affinity.**\n> **⚠️ Computation is genuinely good at hit finding, property optimization and reducing\n> cycle time in lead optimization. ⚠️ It is much weaker at predicting whether the TARGET\n> was the right one — which is where most money is lost.**\n> **⚠️ So a platform claim of the form \"we designed a molecule 10× faster\" is compatible\n> with no improvement in the outcome that matters** (§24.1 → `drugdev-reference`).\n\n**⚠️ The DMTA cycle** (**Design–Make–Test–Analyse**) **is the operating loop of lead\noptimization, and ⚠️ the real objective of most discovery software is REDUCING THE NUMBER\nOF CYCLES**, **not maximizing predictive accuracy in isolation** (§16 → `drugdev-qsar-admet-generative-models-and-validation`).\n\n---\n\n## §2. Targets and Modalities\n\n**⚠️ Targets**: **enzymes (kinases, proteases), GPCRs, ion channels, nuclear receptors,\nprotein-protein interfaces (⚠️ historically \"undruggable\" — flat, large surfaces with no\npocket).**\n**⚠️ Target validation is the highest-value and least computational step**: ⚠️ **genetic\nevidence that modulating the target changes the disease is the strongest predictor of\nclinical success, and human genetics-supported targets have a substantially better track\nrecord.**\n**⚠️ Modalities and their very different computational problems:**\n```\nSMALL MOLECULES  ⚠️ the classic cheminformatics domain (most of this doc)\nBIOLOGICS  ⚠️ antibodies — sequence and structure problems, not SMILES\nPROTACs \u002F molecular glues  ⚠️ TERNARY complexes; conventional\n   affinity-driven design does not apply\nPEPTIDES · OLIGONUCLEOTIDES (ASO, siRNA) · ⚠️ mRNA and vaccines ·\nCELL AND GENE THERAPY\n```\n**⚠️ Do not assume small-molecule tooling transfers** — ⚠️ **RDKit and docking are largely\nirrelevant to antibody engineering, which is a sequence\u002Fstructure problem with its own\nstack.**\n\n---\n\n## §3. ⚠️ What Makes a Molecule a Drug\n\n**⚠️ Potency is the easy part. Almost everything hard is about what the body does to the\nmolecule.**\n```\n⚠️ POTENCY  IC50, Ki, Kd, EC50 — ⚠️ note these are assay-dependent and\n   NOT directly comparable across labs or formats (§6)\n⚠️ SELECTIVITY  ⚠️ hitting the target and NOT the 500 similar proteins\n⚠️ ADME  Absorption, Distribution, Metabolism, Excretion\n⚠️ TOXICITY  ⚠️ hERG (cardiac), hepatotoxicity, genotoxicity, reactive\n   metabolites\n⚠️ DEVELOPABILITY  solubility, stability, synthesizability, cost,\n   crystallinity, formulation\n⚠️ LIGAND EFFICIENCY  LE = ΔG\u002Fheavy atoms; LLE = pIC50 − logP\n   ⚠️ These exist because raw potency can be bought with lipophilicity,\n   which then wrecks everything else\n```\n> **⚠️ GOTCHA — Lipinski's Rule of Five is widely misused as a filter, and Lipinski said\n> otherwise.** ⚠️ **It was a retrospective ORAL BIOAVAILABILITY observation, explicitly not\n> a design rule, and it does not apply to natural products, actively transported\n> compounds, antibiotics, or beyond-Rule-of-5 space where important drugs live.**\n> **⚠️ Hard-filtering a virtual library on Ro5 discards real chemistry.** **⚠️ Use it as a\n> soft flag; the related PAINS filters deserve the same caution — they flag frequent\n> hitters, and treating them as a validated exclusion list has been criticized in the\n> literature.**\n\n---\n\n# PART II — REPRESENTATION AND DATA\n","# Drug Discovery Software: The Pipeline and Where Software Helps, Targets and Modalities, and What Makes a Molecule a Drug\n\n> **Part 1 of 6** of the *Medicine Design Software Development* reference (plugin `medicine-design-software-development`), covering §0–§3. Sibling skills: `drugdev-representation-cheminformatics-data-quality-and-leakage` (§4–§7), `drugdev-protein-structure-docking-and-molecular-dynamics` (§8–§12), `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, §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## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| **⚠️ The pipeline and the attrition** | **§1** |\n| Targets and modalities | §2 |\n| **⚠️ What makes a molecule a drug** | **§3** |\n| **Molecular representation** | **§4 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| Cheminformatics toolkits | §5 → `drugdev-representation-cheminformatics-data-quality-and-leakage` |\n| **⚠️ Data sources and quality** | **§6 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| **⚠️ Splitting and leakage** | **§7 → `drugdev-representation-cheminformatics-data-quality-and-leakage`** |\n| Protein structure | §8 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| **⚠️ Structure prediction** | **§9 → `drugdev-protein-structure-docking-and-molecular-dynamics`** |\n| **⚠️ Docking** | **§10 → `drugdev-protein-structure-docking-and-molecular-dynamics`** |\n| Molecular dynamics | §11 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| Free energy methods | §12 → `drugdev-protein-structure-docking-and-molecular-dynamics` |\n| QSAR and property prediction | §13 → `drugdev-qsar-admet-generative-models-and-validation` |\n| ADMET | §14 → `drugdev-qsar-admet-generative-models-and-validation` |\n| **Generative models** | **§15 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| Active learning and the DMTA loop | §16 → `drugdev-qsar-admet-generative-models-and-validation` |\n| **⚠️ Benchmarks** | **§17 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| **⚠️ Validation that means something** | **§18 → `drugdev-qsar-admet-generative-models-and-validation`** |\n| Pipeline engineering | §19 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| Compute | §20 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| Reproducibility | §21 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| **⚠️ GxP and validation** | **§22 → `drugdev-pipeline-engineering-compute-and-regulated-software`** |\n| Software as a medical device | §23 → `drugdev-pipeline-engineering-compute-and-regulated-software` |\n| **What's live** | **§24 → `drugdev-reference`** |\n| Misconceptions, numbers | §25–§26 → `drugdev-reference` |\n| Tools, quick ref, method | §27–§29 → `drugdev-reference` |\n\n---\n\n## §1. ⚠️ The Pipeline and Where Software Helps\n\n```\nTARGET ID → HIT FINDING → HIT-TO-LEAD → LEAD OPTIMIZATION →\nPRECLINICAL → PHASE I → PHASE II → PHASE III → FILING\n⚠️ Reported: 10–15 years and >$1–2B per approved drug\n⚠️ Reported attrition: >10,000 compounds screened → ~1 approved\n⚠️ ~90% of candidates entering clinical trials never gain approval\n```\n> **⚠️ GOTCHA — understand WHERE the failures happen or you will optimize the wrong\n> thing.** ⚠️ **The dominant clinical failure modes are lack of EFFICACY (reported around\n> 40–50%) and TOXICITY (reported around 30%)** — **and both are properties of the BIOLOGY\n> and the human system, not of the molecule's binding affinity.**\n> **⚠️ Computation is genuinely good at hit finding, property optimization and reducing\n> cycle time in lead optimization. ⚠️ It is much weaker at predicting whether the TARGET\n> was the right one — which is where most money is lost.**\n> **⚠️ So a platform claim of the form \"we designed a molecule 10× faster\" is compatible\n> with no improvement in the outcome that matters** (§24.1 → `drugdev-reference`).\n\n**⚠️ The DMTA cycle** (**Design–Make–Test–Analyse**) **is the operating loop of lead\noptimization, and ⚠️ the real objective of most discovery software is REDUCING THE NUMBER\nOF CYCLES**, **not maximizing predictive accuracy in isolation** (§16 → `drugdev-qsar-admet-generative-models-and-validation`).\n\n---\n\n## §2. Targets and Modalities\n\n**⚠️ Targets**: **enzymes (kinases, proteases), GPCRs, ion channels, nuclear receptors,\nprotein-protein interfaces (⚠️ historically \"undruggable\" — flat, large surfaces with no\npocket).**\n**⚠️ Target validation is the highest-value and least computational step**: ⚠️ **genetic\nevidence that modulating the target changes the disease is the strongest predictor of\nclinical success, and human genetics-supported targets have a substantially better track\nrecord.**\n**⚠️ Modalities and their very different computational problems:**\n```\nSMALL MOLECULES  ⚠️ the classic cheminformatics domain (most of this doc)\nBIOLOGICS  ⚠️ antibodies — sequence and structure problems, not SMILES\nPROTACs \u002F molecular glues  ⚠️ TERNARY complexes; conventional\n   affinity-driven design does not apply\nPEPTIDES · OLIGONUCLEOTIDES (ASO, siRNA) · ⚠️ mRNA and vaccines ·\nCELL AND GENE THERAPY\n```\n**⚠️ Do not assume small-molecule tooling transfers** — ⚠️ **RDKit and docking are largely\nirrelevant to antibody engineering, which is a sequence\u002Fstructure problem with its own\nstack.**\n\n---\n\n## §3. ⚠️ What Makes a Molecule a Drug\n\n**⚠️ Potency is the easy part. Almost everything hard is about what the body does to the\nmolecule.**\n```\n⚠️ POTENCY  IC50, Ki, Kd, EC50 — ⚠️ note these are assay-dependent and\n   NOT directly comparable across labs or formats (§6)\n⚠️ SELECTIVITY  ⚠️ hitting the target and NOT the 500 similar proteins\n⚠️ ADME  Absorption, Distribution, Metabolism, Excretion\n⚠️ TOXICITY  ⚠️ hERG (cardiac), hepatotoxicity, genotoxicity, reactive\n   metabolites\n⚠️ DEVELOPABILITY  solubility, stability, synthesizability, cost,\n   crystallinity, formulation\n⚠️ LIGAND EFFICIENCY  LE = ΔG\u002Fheavy atoms; LLE = pIC50 − logP\n   ⚠️ These exist because raw potency can be bought with lipophilicity,\n   which then wrecks everything else\n```\n> **⚠️ GOTCHA — Lipinski's Rule of Five is widely misused as a filter, and Lipinski said\n> otherwise.** ⚠️ **It was a retrospective ORAL BIOAVAILABILITY observation, explicitly not\n> a design rule, and it does not apply to natural products, actively transported\n> compounds, antibiotics, or beyond-Rule-of-5 space where important drugs live.**\n> **⚠️ Hard-filtering a virtual library on Ro5 discards real chemistry.** **⚠️ Use it as a\n> soft flag; the related PAINS filters deserve the same caution — they flag frequent\n> hitters, and treating them as a validated exclusion list has been criticized in the\n> literature.**\n\n---\n\n# PART II — REPRESENTATION AND DATA\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedicine-design-software-development\u002Fskills\u002Fdrugdev-pipeline-targets-and-drug-likeness",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-pipeline-targets-and-drug-likeness",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill drugdev-pipeline-targets-and-drug-likeness",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill drugdev-pipeline-targets-and-drug-likeness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmedicine-design-software-development\u002Fskills\u002Fdrugdev-pipeline-targets-and-drug-likeness\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",[],[]]