[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARYERN30K12YY17ZZSWCB6":3,"skill-same:01M7ARYERN30K12YY17ZZSWCB6":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},"01M7ARYERN30K12YY17ZZSWCB6","robotics-planning-control-and-manipulation",null,"Use when making the robot move: motion planning with sampling-based planners, trajectory optimization and collision checking; control from PID through LQR, MPC and whole-body control and what actually matters in practice rather than in theory; and manipulation — grasping, force control, and compliant behaviour.","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\u002Frobotics-software\u002Fskills\u002Frobotics-planning-control-and-manipulation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: robotics-planning-control-and-manipulation\ndescription: \"Use when making the robot move: motion planning with sampling-based planners, trajectory optimization and collision checking; control from PID through LQR, MPC and whole-body control and what actually matters in practice rather than in theory; and manipulation — grasping, force control, and compliant behaviour.\"\n---\n\n# Robotics Software: Motion Planning, Control, and Manipulation\n\n> **Part 2 of 5** of the *Robotics Software* reference (plugin `robotics-software`), covering §5–§7. Sibling skills: `robotics-stack-ros2-and-perception` (§0–§4), `robotics-learning-simulation-and-fleets` (§8–§10), `robotics-safety-standards-and-deployment` (§11–§14), `robotics-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `robotics-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers building robots that operate in the\n> physical world with real consequences — deliberately distinct from a hobbyist kit\n> reference. Three markers:\n> - **[DURABLE]** — control theory, estimation, architecture, and safety discipline.\n>   Most of this document.\n> - **[VERSIONED]** — frameworks, models, standards, tooling.\n> - **[CONTESTED]** — genuine and active disagreement, of which this field currently has\n>   a lot.\n>\n> **⚠️ GOTCHA** boxes mark the failures that damage hardware, or people.\n>\n> **The three framings that organize everything below:**\n> 1. **Physics doesn't have an undo button.** A web service that fails returns a 500;\n>    a robot that fails puts mass through space. **This single asymmetry justifies every\n>    piece of apparently excessive rigour below** — the redundancy, the state machines,\n>    the simulation, the safety cases (§11 → `robotics-safety-standards-and-deployment`, §13 → `robotics-safety-standards-and-deployment`).\n> 2. **⚠️ Robotics is an integration discipline, and the integration is where it fails.**\n>    Perception, estimation, planning, and control each work in isolation and break at\n>    the seams — timing, coordinate frames, latency, and units. **The classic robotics bug\n>    is not a bad algorithm; it's a transform published 40ms late** (§3.4 → `robotics-stack-ros2-and-perception`, §12 → `robotics-safety-standards-and-deployment`).\n> 3. **The field is in the middle of a genuine methodological argument** between\n>    classical model-based robotics and learned end-to-end policies (§8 → `robotics-learning-simulation-and-fleets`, §16.1 → `robotics-reference`).\n>    **Neither side has won, production systems are overwhelmingly hybrid, and anyone\n>    telling you the argument is settled is selling something.**\n\n---\n\n## §5. Motion Planning\n\n**[DURABLE] The configuration-space framing**: planning happens in the space of robot\nconfigurations, not in the workspace, and obstacles map into C-space as forbidden regions.\n**Dimensionality is the enemy** — a 7-DOF arm plans in 7 dimensions.\n\n| Family | Notes |\n|---|---|\n| **Grid\u002Fgraph search** — A\\*, D\\* Lite, hybrid A\\* | ⚠️ **Optimal and complete in the discretization**; the standard for ground vehicles. Hybrid A\\* handles nonholonomic constraints |\n| **Sampling-based** — RRT, RRT\\*, PRM, BIT\\*, informed RRT\\* | ⚠️ **Probabilistically complete, scales to high DOF, non-deterministic.** The default for arms (OMPL) |\n| **Optimization-based** — CHOMP, STOMP, TrajOpt | Smooth trajectories, ⚠️ **local minima** |\n| **Reactive** — DWA, TEB, potential fields, VO\u002FORCA | Fast local avoidance. ⚠️ **Potential fields have local minima and everyone rediscovers this** |\n| **Learned** | §8 → `robotics-learning-simulation-and-fleets` |\n\n**[DURABLE] The distinction that structures every navigation stack**: a **global planner**\n(slow, complete, over a known map) and a **local planner\u002Fcontroller** (fast, reactive,\nover live sensor data). **Nav2's architecture is this made explicit.**\n\n**⚠️ The constraints that make real planning hard**: **kinodynamic limits** (a car can't\nmove sideways; an arm has torque limits), **differential constraints**, **time-varying\nobstacles**, ⚠️ **planning under uncertainty** — the plan must be robust to the fact that\n§4 → `robotics-stack-ros2-and-perception`'s estimate is wrong — and **replanning latency**, because a plan computed for where you\nwere is worthless.\n\n---\n\n## §6. Control\n\n**[DURABLE] The most durable body of theory in this document. None of it has changed in\ndecades and none of it will.**\n\n### 6.1 The ladder\n\n| Controller | Use | ⚠️ Watch |\n|---|---|---|\n| **PID** | ⚠️ **Still the workhorse of industrial robotics** | Integral windup; derivative noise amplification; **needs retuning as the plant changes** |\n| **Feedforward + feedback** | ⚠️ **The single biggest practical improvement over pure PID** — model what you can, correct the rest | Requires a model |\n| **LQR** | Optimal for linear systems with quadratic cost | Linear assumption |\n| **iLQR \u002F DDP** | Nonlinear trajectory optimization | Local |\n| **MPC** | ⚠️ **Handles constraints explicitly, and that's why it won** — the standard for AVs, legged robots, and drones | Compute cost; needs a good model and a solver that hits the deadline |\n| **Impedance \u002F admittance** | ⚠️ **Contact tasks.** Controls the *relationship* between force and motion rather than either alone | Stability at stiff contact |\n| **Whole-body control** | Humanoids and legged systems — hierarchical QP over all joints subject to balance and contact constraints | Serious complexity |\n| **Adaptive \u002F robust (H∞, sliding mode)** | Uncertain or varying plants | Chatter; conservatism |\n| **Learned policies** | §8 → `robotics-learning-simulation-and-fleets` | ⚠️ **No stability guarantees** |\n\n### 6.2 What actually matters in practice\n\n**[DURABLE] The system-level facts that dominate controller performance:**\n- **⚠️ Latency and dead time destabilize.** Every millisecond between measurement and\n  actuation reduces achievable bandwidth. **This is why §3.4 → `robotics-stack-ros2-and-perception` matters to §6.**\n- **Jitter is worse than latency.** A consistent 5ms delay can be compensated; a delay\n  varying 1–20ms cannot. ⚠️ **Determinism beats speed** (§11 → `robotics-safety-standards-and-deployment`).\n- **Actuator saturation** invalidates your linear analysis, and **integral windup is what\n  happens next.** Clamp it.\n- **Discretization**: your continuous-time design is running at a finite rate.\n  ⚠️ **Sample at least 10–20× your bandwidth of interest.**\n- **Backlash, friction, and compliance** are what separate the model from the machine.\n  Stiction in particular is nonlinear and nasty.\n- **⚠️ Series-elastic and torque-controlled actuators changed what's possible** in legged\n  and contact-rich robotics — they make force controllable rather than merely position.\n- **Safety limits belong in a separate layer** that can't be argued with by the controller\n  (§13 → `robotics-safety-standards-and-deployment`).\n\n---\n\n## §7. Manipulation\n\n**[DURABLE] Manipulation is harder than navigation, and the reason is contact.** Free-space\nmotion is smooth and modellable; **contact is discontinuous, high-bandwidth, and where the\nmodels stop working.**\n\n**Kinematics**: forward (joint angles → pose, easy), **inverse** (pose → joint angles;\n⚠️ **multiple solutions, singularities, and no closed form for many arms** — IKFast,\nTRAC-IK, or numerical), **Jacobians** (velocity mapping; ⚠️ **singularities are where it\nloses rank and joint velocities blow up**), and **redundancy resolution** for 7-DOF arms.\n\n**Grasping**: analytic (force closure, wrench space) vs. **learned** (⚠️ **now dominant\nfor unstructured objects** — GraspNet, Contact-GraspNet, Dex-Net), and the hard cases are\n**deformables, transparent and reflective objects** (⚠️ **which defeat depth sensors\noutright**), and **cluttered bins**.\n\n**⚠️ The practical reality: the last centimetre is the hard part.** Getting near the object\nis solved; the final approach, contact, and force regulation is where systems fail —\nwhich is exactly why §8 → `robotics-learning-simulation-and-fleets`'s learned policies got traction here first.\n","# Robotics Software: Motion Planning, Control, and Manipulation\n\n> **Part 2 of 5** of the *Robotics Software* reference (plugin `robotics-software`), covering §5–§7. Sibling skills: `robotics-stack-ros2-and-perception` (§0–§4), `robotics-learning-simulation-and-fleets` (§8–§10), `robotics-safety-standards-and-deployment` (§11–§14), `robotics-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `robotics-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers building robots that operate in the\n> physical world with real consequences — deliberately distinct from a hobbyist kit\n> reference. Three markers:\n> - **[DURABLE]** — control theory, estimation, architecture, and safety discipline.\n>   Most of this document.\n> - **[VERSIONED]** — frameworks, models, standards, tooling.\n> - **[CONTESTED]** — genuine and active disagreement, of which this field currently has\n>   a lot.\n>\n> **⚠️ GOTCHA** boxes mark the failures that damage hardware, or people.\n>\n> **The three framings that organize everything below:**\n> 1. **Physics doesn't have an undo button.** A web service that fails returns a 500;\n>    a robot that fails puts mass through space. **This single asymmetry justifies every\n>    piece of apparently excessive rigour below** — the redundancy, the state machines,\n>    the simulation, the safety cases (§11 → `robotics-safety-standards-and-deployment`, §13 → `robotics-safety-standards-and-deployment`).\n> 2. **⚠️ Robotics is an integration discipline, and the integration is where it fails.**\n>    Perception, estimation, planning, and control each work in isolation and break at\n>    the seams — timing, coordinate frames, latency, and units. **The classic robotics bug\n>    is not a bad algorithm; it's a transform published 40ms late** (§3.4 → `robotics-stack-ros2-and-perception`, §12 → `robotics-safety-standards-and-deployment`).\n> 3. **The field is in the middle of a genuine methodological argument** between\n>    classical model-based robotics and learned end-to-end policies (§8 → `robotics-learning-simulation-and-fleets`, §16.1 → `robotics-reference`).\n>    **Neither side has won, production systems are overwhelmingly hybrid, and anyone\n>    telling you the argument is settled is selling something.**\n\n---\n\n## §5. Motion Planning\n\n**[DURABLE] The configuration-space framing**: planning happens in the space of robot\nconfigurations, not in the workspace, and obstacles map into C-space as forbidden regions.\n**Dimensionality is the enemy** — a 7-DOF arm plans in 7 dimensions.\n\n| Family | Notes |\n|---|---|\n| **Grid\u002Fgraph search** — A\\*, D\\* Lite, hybrid A\\* | ⚠️ **Optimal and complete in the discretization**; the standard for ground vehicles. Hybrid A\\* handles nonholonomic constraints |\n| **Sampling-based** — RRT, RRT\\*, PRM, BIT\\*, informed RRT\\* | ⚠️ **Probabilistically complete, scales to high DOF, non-deterministic.** The default for arms (OMPL) |\n| **Optimization-based** — CHOMP, STOMP, TrajOpt | Smooth trajectories, ⚠️ **local minima** |\n| **Reactive** — DWA, TEB, potential fields, VO\u002FORCA | Fast local avoidance. ⚠️ **Potential fields have local minima and everyone rediscovers this** |\n| **Learned** | §8 → `robotics-learning-simulation-and-fleets` |\n\n**[DURABLE] The distinction that structures every navigation stack**: a **global planner**\n(slow, complete, over a known map) and a **local planner\u002Fcontroller** (fast, reactive,\nover live sensor data). **Nav2's architecture is this made explicit.**\n\n**⚠️ The constraints that make real planning hard**: **kinodynamic limits** (a car can't\nmove sideways; an arm has torque limits), **differential constraints**, **time-varying\nobstacles**, ⚠️ **planning under uncertainty** — the plan must be robust to the fact that\n§4 → `robotics-stack-ros2-and-perception`'s estimate is wrong — and **replanning latency**, because a plan computed for where you\nwere is worthless.\n\n---\n\n## §6. Control\n\n**[DURABLE] The most durable body of theory in this document. None of it has changed in\ndecades and none of it will.**\n\n### 6.1 The ladder\n\n| Controller | Use | ⚠️ Watch |\n|---|---|---|\n| **PID** | ⚠️ **Still the workhorse of industrial robotics** | Integral windup; derivative noise amplification; **needs retuning as the plant changes** |\n| **Feedforward + feedback** | ⚠️ **The single biggest practical improvement over pure PID** — model what you can, correct the rest | Requires a model |\n| **LQR** | Optimal for linear systems with quadratic cost | Linear assumption |\n| **iLQR \u002F DDP** | Nonlinear trajectory optimization | Local |\n| **MPC** | ⚠️ **Handles constraints explicitly, and that's why it won** — the standard for AVs, legged robots, and drones | Compute cost; needs a good model and a solver that hits the deadline |\n| **Impedance \u002F admittance** | ⚠️ **Contact tasks.** Controls the *relationship* between force and motion rather than either alone | Stability at stiff contact |\n| **Whole-body control** | Humanoids and legged systems — hierarchical QP over all joints subject to balance and contact constraints | Serious complexity |\n| **Adaptive \u002F robust (H∞, sliding mode)** | Uncertain or varying plants | Chatter; conservatism |\n| **Learned policies** | §8 → `robotics-learning-simulation-and-fleets` | ⚠️ **No stability guarantees** |\n\n### 6.2 What actually matters in practice\n\n**[DURABLE] The system-level facts that dominate controller performance:**\n- **⚠️ Latency and dead time destabilize.** Every millisecond between measurement and\n  actuation reduces achievable bandwidth. **This is why §3.4 → `robotics-stack-ros2-and-perception` matters to §6.**\n- **Jitter is worse than latency.** A consistent 5ms delay can be compensated; a delay\n  varying 1–20ms cannot. ⚠️ **Determinism beats speed** (§11 → `robotics-safety-standards-and-deployment`).\n- **Actuator saturation** invalidates your linear analysis, and **integral windup is what\n  happens next.** Clamp it.\n- **Discretization**: your continuous-time design is running at a finite rate.\n  ⚠️ **Sample at least 10–20× your bandwidth of interest.**\n- **Backlash, friction, and compliance** are what separate the model from the machine.\n  Stiction in particular is nonlinear and nasty.\n- **⚠️ Series-elastic and torque-controlled actuators changed what's possible** in legged\n  and contact-rich robotics — they make force controllable rather than merely position.\n- **Safety limits belong in a separate layer** that can't be argued with by the controller\n  (§13 → `robotics-safety-standards-and-deployment`).\n\n---\n\n## §7. Manipulation\n\n**[DURABLE] Manipulation is harder than navigation, and the reason is contact.** Free-space\nmotion is smooth and modellable; **contact is discontinuous, high-bandwidth, and where the\nmodels stop working.**\n\n**Kinematics**: forward (joint angles → pose, easy), **inverse** (pose → joint angles;\n⚠️ **multiple solutions, singularities, and no closed form for many arms** — IKFast,\nTRAC-IK, or numerical), **Jacobians** (velocity mapping; ⚠️ **singularities are where it\nloses rank and joint velocities blow up**), and **redundancy resolution** for 7-DOF arms.\n\n**Grasping**: analytic (force closure, wrench space) vs. **learned** (⚠️ **now dominant\nfor unstructured objects** — GraspNet, Contact-GraspNet, Dex-Net), and the hard cases are\n**deformables, transparent and reflective objects** (⚠️ **which defeat depth sensors\noutright**), and **cluttered bins**.\n\n**⚠️ The practical reality: the last centimetre is the hard part.** Getting near the object\nis solved; the final approach, contact, and force regulation is where systems fail —\nwhich is exactly why §8 → `robotics-learning-simulation-and-fleets`'s learned policies got traction here first.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Frobotics-software\u002Fskills\u002Frobotics-planning-control-and-manipulation",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 robotics-planning-control-and-manipulation",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill robotics-planning-control-and-manipulation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill robotics-planning-control-and-manipulation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Frobotics-software\u002Fskills\u002Frobotics-planning-control-and-manipulation\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",[],[]]