[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735BJ0ZBADJXQ9YPTYSWJZN":3,"skill-same:01M735BJ0ZBADJXQ9YPTYSWJZN":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M735BJ0ZBADJXQ9YPTYSWJZN","use-preferred-style",null,"Apply preferred writing style.","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fuse-preferred-style\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: use-preferred-style\ndescription: \"Apply preferred writing style.\"\nuser-invocable: true\nallowed-tools:\n  - Bash\n  - Read\n  - Edit\n  - Write\n---\n\n# use-preferred-style — write the way the user prefers\n\nApply the user's prose style to anything user-facing. The style is plain and\ndirect. Say the point in a short sentence. Stack fewer clauses. Drop filler.\n\nThe authority is the user's own guide, **Principles of Scientific Writing\n(PSW)**: https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002F.\nPSW covers word choice, conciseness, grammar, and avoiding clichés and AI tells --- including\nthe nested-dependent-clause rule below, in its own \"Conciseness\" chapter.\nThis skill operationalizes PSW and adds the user's own rule on joining\nindependent clauses with coordinating conjunctions rather than subordinate\nconstructions, which PSW does not state explicitly.\nWhen in doubt, defer to PSW.\n\n## When this fires\n\n- The user asks to \"use my style\", \"apply my preferred style\", \"rewrite in my\n  voice\", \"tighten this\", \"plain-language this\", or invokes `\u002Fstyle`.\n- You are drafting or revising any prose the user will read: PR\u002Fissue\u002Fcommit\n  bodies, docs, READMEs, code comments, release notes, emails, chat replies.\n- Apply it by default to your own drafts, even when not asked. This is a\n  standing preference, not just an on-demand command.\n\n## The rules\n\nRule 1 restates PSW's own \"Limit complex sentence structures\" section\n(Conciseness chapter).\nRules 2--4 are the user's own emphasis on filler and clause structure,\ndrawing on PSW's conciseness and word-choice material without matching one\nspecific section.\nRules 5--8 come straight from PSW's word-choice, conciseness, and grammar\nchapters, cited individually below.\nRules 9--11 add the user's review conventions for notes prose,\ncited individually below.\n\n1. **Limit dependent clauses.** A dependent (subordinate) clause cannot stand\n   alone. It starts with a word like *because*, *although*, *which*, *while*,\n   *since*, *when*, or *if*. One per sentence is plenty. Two or more stacked\n   together is a rewrite signal. Break the sentence apart instead.\n\n2. **Cut low-content filler and jargon.** Delete words that add no information.\n   Replace jargon with the plain word. See the swap table below.\n\n3. **Prefer simple declarative sentences.** State the fact. Put the subject\n   first, then the verb, then the rest. Short beats clever.\n\n4. **Join independent clauses with coordinating conjunctions.** Two complete\n   thoughts read better side by side than nested. Use *and*, *but*, *so*, *or*,\n   *yet*, *nor*, *for*. Prefer \"X is fast, but Y is correct\" over \"While X is\n   fast, Y is correct.\"\n\n5. **Prefer plain (Anglish) words over Latin-derived ones** (PSW, \"Word\n   choice\"). Old-English-derived words decompose into parts a reader already\n   knows. Latin roots must be memorized. So write *before*, not *prior to*;\n   *needed*, not *necessary*; *use*, not *utilize*. This is a heuristic, not a\n   purity rule — pick whatever word the reader grasps fastest.\n\n6. **Prefer active voice** (PSW, \"Conciseness\"). Name the actor, then the\n   action. Prefer \"The researchers ran the experiment\" over \"The experiment was\n   run by the researchers.\" Passive is fine when the actor is unknown or beside\n   the point.\n\n7. **Keep relative pronouns** (PSW, \"Grammar\").\n   English lets you drop *that*, *which*, or *who* in some sentences, but\n   dropping it forces the reader to backtrack once they realize a describing\n   clause has started.\n   Prefer \"the groundwork *that* I now apply\" over \"the groundwork I now\n   apply.\"\n   Also use *that* for a restrictive clause (identifies which thing you mean,\n   no comma) and *which* for a non-restrictive one (adds a detail, set off by\n   commas): \"the dataset *that* we collected in 2023\" versus \"our dataset,\n   *which* contains 4,000 records,\".\n\n8. **Name a demonstrative's referent** (PSW, \"Grammar\").\n   *This*, *that*, *these*, and *those* used standalone as pronouns send the\n   reader searching backward for what they mean, often across a whole\n   preceding clause rather than one noun.\n   Follow the demonstrative with the noun it refers to.\n\n   > ❌ The model overfit the training data.\n   > **This** poses a problem for deployment.\n   >\n   > ✅ The model overfit the training data.\n   > **This overfitting** poses a problem for deployment.\n\n9. **Test every word for literal truth** (PSW: \"Avoid vague and\n   metaphorical language\").\n   Whatever its part of speech, a word must be literally true of what it names\n   or describes.\n   A point does not \"sit\" at a height,\n   and an estimate does not \"live\" in an interval.\n   Write that the point is at the height and the estimate is in the interval.\n   No list of phrases is complete,\n   so apply the test to each word you wrote.\n   Run each phrase through the test\n   before you copy it from a neighbouring figure or paragraph.\n\n10. **Make a caption stand alone** (PSW, \"Slides, posters, and figures\").\n    A caption states what its own figure shows.\n    It does not rely on another figure's caption: never write \"the same paths\n    as @fig-x\" or \"the surface of @fig-x\" in place of the content.\n\n11. **Break clauses onto their own lines in notes sources** (Ezra's review\n    rule for `.qmd` prose).\n    Put one sentence per line, and break before \"and\", \"but\", \"so\", \"as\",\n    \"which\", \"then\", and \"toward\" when a line holds two clauses.\n    Link the first use of every defined term in a div to its definition.\n\n## Filler and jargon to cut or swap\n\n| Cut \u002F avoid | Use instead |\n|-------------|-------------|\n| in order to | to |\n| due to the fact that | because |\n| at this point in time | now |\n| prior to | before |\n| in the event that | if |\n| necessary | needed |\n| has the ability to, is able to | can |\n| utilize, leverage | use |\n| facilitate | help, let |\n| make a decision | decide |\n| give consideration to | consider |\n| a large number of, a number of | many, some, N |\n| it is worth noting that | (delete) |\n| it should be noted that | (delete) |\n| needless to say | (delete) |\n| as a matter of fact | (delete) |\n| basically, essentially, actually | (delete) |\n| very, really, quite, simply | (delete) |\n| in terms of | (rephrase or delete) |\n| with regard to | about |\n\nTreat the table as a starting set, not a closed list. Any word that carries no\ninformation is filler. Cut it. Most of these swaps come from PSW's \"Conciseness\"\nand \"Word choice\" chapters.\n\n## Procedure\n\n1. **Read the target prose.** A file, a diff, a draft, or text the user pasted.\n2. **Find the long sentences first.** A sentence over ~25 words usually hides a\n   dependent clause you can split out. Split it.\n3. **Strip filler and swap for plain words.** Run the swap table over the text.\n   Delete dead words. Prefer the Anglish word over the Latin one.\n4. **Flatten subordination.** Turn \"Although A, B\" into \"A. But B.\" or\n   \"A, but B.\" Turn \"which\" relative clauses into a second sentence.\n5. **Restore dropped relative pronouns, and name what a demonstrative refers\n   to.**\n   Check every describing clause still has its *that*\u002F*which*\u002F*who*, and\n   every standalone *this*\u002F*that*\u002F*these*\u002F*those* is followed by the noun it\n   means.\n6. **Switch passive to active** where the actor matters.\n   Name the actor first.\n7. **Keep the meaning exact.**\n   Style edits must not change facts, scope, hedges the user meant, or\n   technical precision.\n   When a hedge is load-bearing, keep it.\n   Plainness is the goal, not false confidence.\n8. **Read it back.**\n   Each sentence should make one point.\n   The data should flow top to bottom.\n9. **Apply rules 9 to 11** to every added line of notes prose, such as a\n   caption, exercise, or solution, before the one push on a branch.\n   Run gha's `check-term-links`, `check-new-line-breaks` (with\n   `NLB_CLAUSE_BREAKS=true`), `check-self-contained-captions`, and\n   `check-serial-comma` locally, with the environment variables from the\n   repo's workflow files.\n   A clean script run does not cover rule 9, so do that one by reading.\n\n## Before \u002F after\n\n> **Before:** It is worth noting that, due to the fact that the cache was not\n> being invalidated when the user updated their profile, which caused stale data\n> to be served, we decided to utilize a new eviction strategy in order to\n> resolve the issue.\n\n> **After:** The cache was not invalidated on profile update. So it served stale\n> data. We switched to a new eviction strategy to fix it.\n\nThe \"after\" is three sentences. Each makes one point. No filler, no `utilize`,\nno stacked `which`\u002F`due to the fact that` clauses.\n\n## When to keep the nesting\n\nThis is a default, not an absolute rule. Keep a dependent clause when splitting\nit would read worse or lose a real logical link. Keep a technical term when it\nis the precise word and the plain swap would be wrong. Readability wins, not\nminimalism for its own sake. (Mirrors the \"avoid nesting, but not blindly\"\nstance in the coding-style rule.)\n\n## Further reading — PSW\n\nThe user's guide, **Principles of Scientific Writing**, is the source of record.\nPull the latest rules from it, not from this summary:\n\n- Guide home: https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002F\n- [Word choice](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fword-choice.html) --- Anglish over Latin; avoiding vague\u002Fmetaphorical language; minimizing jargon.\n- [Conciseness](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fconciseness.html) --- cut redundancy; active voice; the swap list; limiting nested clauses.\n- [Grammar](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fgrammar.html) --- rules 7--8 above: relative and demonstrative pronouns.\n- [Avoiding clichés](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Favoid-cliches.html) --- overused vocabulary, rhetorical reflexes, formatting habits;\n  see also the `find-ai-tells` skill below.\n- [Defining terms clearly](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fdefining-terms.html)\n- [Paper organization](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fpaper-organization.html)\n\nPSW is a work in progress. When it and this skill disagree, PSW wins — and flag\nthe drift so this skill gets updated.\n\n## Relationship to other skills\n\n- **`prose-editor` agent** ([`.claude\u002Fagents\u002Fprose-editor.md`](..\u002F..\u002F.claude\u002Fagents\u002Fprose-editor.md)) --- the dedicated editor subagent.\n  Writing agents work iteratively: draft substantively-correct content first,\n  then hand off to `prose-editor` to tighten prose style and enforce PSW compliance.\n  See [`shared\u002Fworkflow\u002Fiterative-editing.md`](..\u002F..\u002Fshared\u002Fworkflow\u002Fiterative-editing.md).\n- **`find-ai-tells`** --- the detector counterpart.\n  It *scans* finished text for AI-authorship tells.\n  This skill *prescribes* how to write up front.\n  Run `find-ai-tells` after; run `use-preferred-style` during.\n- **`simplify` \u002F `tidy`** — the same \"cut what adds no value\" instinct, applied\n  to code instead of prose.\n- **`memorize` \u002F `remember`** — for a one-off wording preference, write a memory\n  instead of editing this skill.\n\n## Anti-patterns\n\n- ❌ Changing the meaning, scope, or technical precision while \"tightening.\"\n- ❌ Dropping a hedge the user meant to keep (turning honest uncertainty into\n  false confidence).\n- ❌ Chopping every sentence to staccato fragments — vary length; aim for clear,\n  not robotic.\n- ❌ Applying it to code identifiers or quoted material that must stay verbatim.\n","# use-preferred-style — write the way the user prefers\n\nApply the user's prose style to anything user-facing. The style is plain and\ndirect. Say the point in a short sentence. Stack fewer clauses. Drop filler.\n\nThe authority is the user's own guide, **Principles of Scientific Writing\n(PSW)**: https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002F.\nPSW covers word choice, conciseness, grammar, and avoiding clichés and AI tells --- including\nthe nested-dependent-clause rule below, in its own \"Conciseness\" chapter.\nThis skill operationalizes PSW and adds the user's own rule on joining\nindependent clauses with coordinating conjunctions rather than subordinate\nconstructions, which PSW does not state explicitly.\nWhen in doubt, defer to PSW.\n\n## When this fires\n\n- The user asks to \"use my style\", \"apply my preferred style\", \"rewrite in my\n  voice\", \"tighten this\", \"plain-language this\", or invokes `\u002Fstyle`.\n- You are drafting or revising any prose the user will read: PR\u002Fissue\u002Fcommit\n  bodies, docs, READMEs, code comments, release notes, emails, chat replies.\n- Apply it by default to your own drafts, even when not asked. This is a\n  standing preference, not just an on-demand command.\n\n## The rules\n\nRule 1 restates PSW's own \"Limit complex sentence structures\" section\n(Conciseness chapter).\nRules 2--4 are the user's own emphasis on filler and clause structure,\ndrawing on PSW's conciseness and word-choice material without matching one\nspecific section.\nRules 5--8 come straight from PSW's word-choice, conciseness, and grammar\nchapters, cited individually below.\nRules 9--11 add the user's review conventions for notes prose,\ncited individually below.\n\n1. **Limit dependent clauses.** A dependent (subordinate) clause cannot stand\n   alone. It starts with a word like *because*, *although*, *which*, *while*,\n   *since*, *when*, or *if*. One per sentence is plenty. Two or more stacked\n   together is a rewrite signal. Break the sentence apart instead.\n\n2. **Cut low-content filler and jargon.** Delete words that add no information.\n   Replace jargon with the plain word. See the swap table below.\n\n3. **Prefer simple declarative sentences.** State the fact. Put the subject\n   first, then the verb, then the rest. Short beats clever.\n\n4. **Join independent clauses with coordinating conjunctions.** Two complete\n   thoughts read better side by side than nested. Use *and*, *but*, *so*, *or*,\n   *yet*, *nor*, *for*. Prefer \"X is fast, but Y is correct\" over \"While X is\n   fast, Y is correct.\"\n\n5. **Prefer plain (Anglish) words over Latin-derived ones** (PSW, \"Word\n   choice\"). Old-English-derived words decompose into parts a reader already\n   knows. Latin roots must be memorized. So write *before*, not *prior to*;\n   *needed*, not *necessary*; *use*, not *utilize*. This is a heuristic, not a\n   purity rule — pick whatever word the reader grasps fastest.\n\n6. **Prefer active voice** (PSW, \"Conciseness\"). Name the actor, then the\n   action. Prefer \"The researchers ran the experiment\" over \"The experiment was\n   run by the researchers.\" Passive is fine when the actor is unknown or beside\n   the point.\n\n7. **Keep relative pronouns** (PSW, \"Grammar\").\n   English lets you drop *that*, *which*, or *who* in some sentences, but\n   dropping it forces the reader to backtrack once they realize a describing\n   clause has started.\n   Prefer \"the groundwork *that* I now apply\" over \"the groundwork I now\n   apply.\"\n   Also use *that* for a restrictive clause (identifies which thing you mean,\n   no comma) and *which* for a non-restrictive one (adds a detail, set off by\n   commas): \"the dataset *that* we collected in 2023\" versus \"our dataset,\n   *which* contains 4,000 records,\".\n\n8. **Name a demonstrative's referent** (PSW, \"Grammar\").\n   *This*, *that*, *these*, and *those* used standalone as pronouns send the\n   reader searching backward for what they mean, often across a whole\n   preceding clause rather than one noun.\n   Follow the demonstrative with the noun it refers to.\n\n   > ❌ The model overfit the training data.\n   > **This** poses a problem for deployment.\n   >\n   > ✅ The model overfit the training data.\n   > **This overfitting** poses a problem for deployment.\n\n9. **Test every word for literal truth** (PSW: \"Avoid vague and\n   metaphorical language\").\n   Whatever its part of speech, a word must be literally true of what it names\n   or describes.\n   A point does not \"sit\" at a height,\n   and an estimate does not \"live\" in an interval.\n   Write that the point is at the height and the estimate is in the interval.\n   No list of phrases is complete,\n   so apply the test to each word you wrote.\n   Run each phrase through the test\n   before you copy it from a neighbouring figure or paragraph.\n\n10. **Make a caption stand alone** (PSW, \"Slides, posters, and figures\").\n    A caption states what its own figure shows.\n    It does not rely on another figure's caption: never write \"the same paths\n    as @fig-x\" or \"the surface of @fig-x\" in place of the content.\n\n11. **Break clauses onto their own lines in notes sources** (Ezra's review\n    rule for `.qmd` prose).\n    Put one sentence per line, and break before \"and\", \"but\", \"so\", \"as\",\n    \"which\", \"then\", and \"toward\" when a line holds two clauses.\n    Link the first use of every defined term in a div to its definition.\n\n## Filler and jargon to cut or swap\n\n| Cut \u002F avoid | Use instead |\n|-------------|-------------|\n| in order to | to |\n| due to the fact that | because |\n| at this point in time | now |\n| prior to | before |\n| in the event that | if |\n| necessary | needed |\n| has the ability to, is able to | can |\n| utilize, leverage | use |\n| facilitate | help, let |\n| make a decision | decide |\n| give consideration to | consider |\n| a large number of, a number of | many, some, N |\n| it is worth noting that | (delete) |\n| it should be noted that | (delete) |\n| needless to say | (delete) |\n| as a matter of fact | (delete) |\n| basically, essentially, actually | (delete) |\n| very, really, quite, simply | (delete) |\n| in terms of | (rephrase or delete) |\n| with regard to | about |\n\nTreat the table as a starting set, not a closed list. Any word that carries no\ninformation is filler. Cut it. Most of these swaps come from PSW's \"Conciseness\"\nand \"Word choice\" chapters.\n\n## Procedure\n\n1. **Read the target prose.** A file, a diff, a draft, or text the user pasted.\n2. **Find the long sentences first.** A sentence over ~25 words usually hides a\n   dependent clause you can split out. Split it.\n3. **Strip filler and swap for plain words.** Run the swap table over the text.\n   Delete dead words. Prefer the Anglish word over the Latin one.\n4. **Flatten subordination.** Turn \"Although A, B\" into \"A. But B.\" or\n   \"A, but B.\" Turn \"which\" relative clauses into a second sentence.\n5. **Restore dropped relative pronouns, and name what a demonstrative refers\n   to.**\n   Check every describing clause still has its *that*\u002F*which*\u002F*who*, and\n   every standalone *this*\u002F*that*\u002F*these*\u002F*those* is followed by the noun it\n   means.\n6. **Switch passive to active** where the actor matters.\n   Name the actor first.\n7. **Keep the meaning exact.**\n   Style edits must not change facts, scope, hedges the user meant, or\n   technical precision.\n   When a hedge is load-bearing, keep it.\n   Plainness is the goal, not false confidence.\n8. **Read it back.**\n   Each sentence should make one point.\n   The data should flow top to bottom.\n9. **Apply rules 9 to 11** to every added line of notes prose, such as a\n   caption, exercise, or solution, before the one push on a branch.\n   Run gha's `check-term-links`, `check-new-line-breaks` (with\n   `NLB_CLAUSE_BREAKS=true`), `check-self-contained-captions`, and\n   `check-serial-comma` locally, with the environment variables from the\n   repo's workflow files.\n   A clean script run does not cover rule 9, so do that one by reading.\n\n## Before \u002F after\n\n> **Before:** It is worth noting that, due to the fact that the cache was not\n> being invalidated when the user updated their profile, which caused stale data\n> to be served, we decided to utilize a new eviction strategy in order to\n> resolve the issue.\n\n> **After:** The cache was not invalidated on profile update. So it served stale\n> data. We switched to a new eviction strategy to fix it.\n\nThe \"after\" is three sentences. Each makes one point. No filler, no `utilize`,\nno stacked `which`\u002F`due to the fact that` clauses.\n\n## When to keep the nesting\n\nThis is a default, not an absolute rule. Keep a dependent clause when splitting\nit would read worse or lose a real logical link. Keep a technical term when it\nis the precise word and the plain swap would be wrong. Readability wins, not\nminimalism for its own sake. (Mirrors the \"avoid nesting, but not blindly\"\nstance in the coding-style rule.)\n\n## Further reading — PSW\n\nThe user's guide, **Principles of Scientific Writing**, is the source of record.\nPull the latest rules from it, not from this summary:\n\n- Guide home: https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002F\n- [Word choice](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fword-choice.html) --- Anglish over Latin; avoiding vague\u002Fmetaphorical language; minimizing jargon.\n- [Conciseness](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fconciseness.html) --- cut redundancy; active voice; the swap list; limiting nested clauses.\n- [Grammar](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fgrammar.html) --- rules 7--8 above: relative and demonstrative pronouns.\n- [Avoiding clichés](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Favoid-cliches.html) --- overused vocabulary, rhetorical reflexes, formatting habits;\n  see also the `find-ai-tells` skill below.\n- [Defining terms clearly](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fdefining-terms.html)\n- [Paper organization](https:\u002F\u002Fmorrison-lab.github.io\u002Fpsw\u002Fchapters\u002Fpaper-organization.html)\n\nPSW is a work in progress. When it and this skill disagree, PSW wins — and flag\nthe drift so this skill gets updated.\n\n## Relationship to other skills\n\n- **`prose-editor` agent** ([`.claude\u002Fagents\u002Fprose-editor.md`](..\u002F..\u002F.claude\u002Fagents\u002Fprose-editor.md)) --- the dedicated editor subagent.\n  Writing agents work iteratively: draft substantively-correct content first,\n  then hand off to `prose-editor` to tighten prose style and enforce PSW compliance.\n  See [`shared\u002Fworkflow\u002Fiterative-editing.md`](..\u002F..\u002Fshared\u002Fworkflow\u002Fiterative-editing.md).\n- **`find-ai-tells`** --- the detector counterpart.\n  It *scans* finished text for AI-authorship tells.\n  This skill *prescribes* how to write up front.\n  Run `find-ai-tells` after; run `use-preferred-style` during.\n- **`simplify` \u002F `tidy`** — the same \"cut what adds no value\" instinct, applied\n  to code instead of prose.\n- **`memorize` \u002F `remember`** — for a one-off wording preference, write a memory\n  instead of editing this skill.\n\n## Anti-patterns\n\n- ❌ Changing the meaning, scope, or technical precision while \"tightening.\"\n- ❌ Dropping a hedge the user meant to keep (turning honest uncertainty into\n  false confidence).\n- ❌ Chopping every sentence to staccato fragments — vary length; aim for clear,\n  not robotic.\n- ❌ Applying it to code identifiers or quoted material that must stay verbatim.\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":29},[25,26,27,28],"Bash","Read","Edit","Write",true,"main","0f720481f8ce3b3d9fef485f6e230d8b3035748e","skills\u002Fuse-preferred-style",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-15 04:39:15",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Morrison-Lab\u002Fai-config --skill use-preferred-style",{"tool":44,"command":45},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill use-preferred-style",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill use-preferred-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fuse-preferred-style\u002FSKILL.md",[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735BVYCGR5VEC65AFDVSNKW","wrap-up","End-of-session verification and UMS.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M735BTH469T1CQ8G2Q9GENCR","workaround-watcher","Watch upstream issue for fix.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fworkaround-watcher\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M735BRKZWFANSQ0GM380B4TD","wn","→ whats-next.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwn\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M735BPE9V830B3B6NGXQ56J6","whats-next","Recommend concrete next step or action.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M735BMHQ60EAD5B7QAWXC5A0","wait-for-results","Wait for pipeline\u002FCI results.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwait-for-results\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M735BKGZHPN1PEMJ7YBD5VJ8","wai","→ send-notes.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwai\u002FSKILL.md",[],[]]