[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMVGDDKFGAFEVV69KFVV22":3,"skill-same:01M7DMVGDDKFGAFEVV69KFVV22":54},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DMVGDDKFGAFEVV69KFVV22","clarity",null,"Reviews and repairs text that is hard to follow: unclear wording, buried answers, dense paragraphs, and structure that is hard to scan, including for readers with ADHD or dyslexia. Use whenever someone asks to make a passage clearer, easier to scan, or answer-first without changing its claims or voice.","harlan-zw\u002Fbrundlefly","harlan-zw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5326365?v=4","01M7DMV9MXAF93SM3MFPZCXJT0","Harlan Wilton","01M7DMV9P1DPERAJG1HJ84YP2C",7,"MIT","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fclarity\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fclarity\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clarity\ndescription: \"Reviews and repairs text that is hard to follow: unclear wording, buried answers, dense paragraphs, and structure that is hard to scan, including for readers with ADHD or dyslexia. Use whenever someone asks to make a passage clearer, easier to scan, or answer-first without changing its claims or voice.\"\nlicense: MIT\n---\n\n# Clarity\n\nHelp the intended reader find the point and understand the next action.\nThis pass reviews wording and structure. It does not run a full style rewrite or verify factual truth.\nFollow the target's instructions, terminology, canonical wording, and requested output format.\nInstalling this Skill does not authorize publication or unrelated edits.\n\n## Establish the reading task\n\nRead the complete passage and any supplied reader preferences.\nIdentify the reader, purpose, and requested scope. Infer them when the context is clear.\nConsider their starting knowledge and the explanation they need to understand or act.\nShow respect and empathy through clear connections, accurate meaning, and no unnecessary reading effort.\nIf a missing choice changes the result materially, ask before dependent edits.\nFor mixed documents, distinguish stories, instructions, explanations, and reference sections.\nPreserve deliberate narrative openings. Keep technical instructions predictable.\n\n## Review wording and structure\n\nDesign for readers with varied attention, working memory, and reading needs, including ADHD and dyslexia.\nDo not infer a diagnosis or claim that most readers have one. Respect stated reader preferences.\nReader comprehension takes priority over stylistic variety.\nBrevity removes unnecessary words. Keep the explanations, conditions, and connections this reader needs.\n\nReader attention is finite. Before writing or editing, predict how much attention this piece will receive.\nUse the reader, purpose, destination, and supplied preferences to make that prediction.\nTreat it as an editorial assumption, not a measured reading time.\nLet it govern scope, order, and depth across the complete output.\nSpend the most attention on what affects the reader's decision, understanding, or next action.\nKeep less important material brief, linked, or optional. Do not give every point equal space.\nPreserve critical conditions and warnings on the main reading path.\nShort sentences alone do not make an output worth the attention it requires.\n\n- **Start simple.** Lead with the answer or action. Then give the common case, an example, and deeper detail.\n  For a story, preserve a deliberate narrative opening. Apply answer-first ordering to its technical sections.\n  Define necessary terms before using them. Keep prerequisites and consequential warnings beside the action.\n  Put optional exceptions and background later. A deep dive still needs a clear entry point.\n- **Keep blocks small.** Give each sentence one main idea and each paragraph one job.\n  Prefer familiar words, explicit actors, and direct instructions. Explain necessary jargon on first use.\n  As editing defaults, aim for sentences under 20 words and paragraphs of one to three sentences.\n  Review three consecutive prose paragraphs for a useful heading, list, example, table, or diagram.\n  These numbers are review prompts, not research thresholds. Preserve meaning and deliberate literary voice.\n- **Make sections findable.** Use descriptive headings for distinct questions, tasks, or reference entries.\n  Keep a logical heading hierarchy. Avoid vague labels, decorative headings, and filler between sections.\n  Readers should find the answer by scanning headings and opening lines.\n- **Choose the useful format.** Use bullets for parallel points, numbers for ordered steps, and tables for comparisons.\n  Use diagrams for relationships or branching processes. Keep connected explanations in short prose.\n  Add an artifact only when it reduces reading effort. Avoid long lists, wide tables, and decorative visuals.\n- **Keep alternatives accessible.** Explain a visual's useful point in nearby text. Supply meaningful text alternatives for images.\n  Label table columns and keep cells short. Never make color, position, or an icon the only carrier of meaning.\n  Use whitespace and restrained emphasis. Avoid full paragraphs in bold, italics, or capitals.\n\nLeave clear sentences and useful headings unchanged. Do not split sentences mechanically or add filler for rhythm.\nPreserve stable anchors and check affected links when changing headings.\nKeep exact code, commands, names, numbers, units, attribution, uncertainty, and required wording.\nKeep conditions, negation, exceptions, permissions, and step order attached to their actions.\nNever invent an actor, explanation, experience, or example to make a passage sound clearer.\nDo not use em dashes or hyphens as sentence punctuation in new prose.\n\n## Deliver the requested pass\n\nFor review only, return concrete reading problems and proposed repairs. Leave the source unchanged.\nFor an edit, change only passages with a reading problem. Explain meaningful repairs outside the edited text.\nBefore delivery, check that the reader can find the answer, understand the terms, and follow the required steps.\nCheck whether the whole output fits the predicted attention and gives the important points enough depth.\nCompare the result with the source for changed claims, conditions, uncertainty, and voice.\nIf rendering is available, inspect the actual output at a narrow width. Otherwise report that limit when relevant.\nIf no repair is needed, say so. Do not invent findings or claim an accessibility audit passed.\n","# Clarity\n\nHelp the intended reader find the point and understand the next action.\nThis pass reviews wording and structure. It does not run a full style rewrite or verify factual truth.\nFollow the target's instructions, terminology, canonical wording, and requested output format.\nInstalling this Skill does not authorize publication or unrelated edits.\n\n## Establish the reading task\n\nRead the complete passage and any supplied reader preferences.\nIdentify the reader, purpose, and requested scope. Infer them when the context is clear.\nConsider their starting knowledge and the explanation they need to understand or act.\nShow respect and empathy through clear connections, accurate meaning, and no unnecessary reading effort.\nIf a missing choice changes the result materially, ask before dependent edits.\nFor mixed documents, distinguish stories, instructions, explanations, and reference sections.\nPreserve deliberate narrative openings. Keep technical instructions predictable.\n\n## Review wording and structure\n\nDesign for readers with varied attention, working memory, and reading needs, including ADHD and dyslexia.\nDo not infer a diagnosis or claim that most readers have one. Respect stated reader preferences.\nReader comprehension takes priority over stylistic variety.\nBrevity removes unnecessary words. Keep the explanations, conditions, and connections this reader needs.\n\nReader attention is finite. Before writing or editing, predict how much attention this piece will receive.\nUse the reader, purpose, destination, and supplied preferences to make that prediction.\nTreat it as an editorial assumption, not a measured reading time.\nLet it govern scope, order, and depth across the complete output.\nSpend the most attention on what affects the reader's decision, understanding, or next action.\nKeep less important material brief, linked, or optional. Do not give every point equal space.\nPreserve critical conditions and warnings on the main reading path.\nShort sentences alone do not make an output worth the attention it requires.\n\n- **Start simple.** Lead with the answer or action. Then give the common case, an example, and deeper detail.\n  For a story, preserve a deliberate narrative opening. Apply answer-first ordering to its technical sections.\n  Define necessary terms before using them. Keep prerequisites and consequential warnings beside the action.\n  Put optional exceptions and background later. A deep dive still needs a clear entry point.\n- **Keep blocks small.** Give each sentence one main idea and each paragraph one job.\n  Prefer familiar words, explicit actors, and direct instructions. Explain necessary jargon on first use.\n  As editing defaults, aim for sentences under 20 words and paragraphs of one to three sentences.\n  Review three consecutive prose paragraphs for a useful heading, list, example, table, or diagram.\n  These numbers are review prompts, not research thresholds. Preserve meaning and deliberate literary voice.\n- **Make sections findable.** Use descriptive headings for distinct questions, tasks, or reference entries.\n  Keep a logical heading hierarchy. Avoid vague labels, decorative headings, and filler between sections.\n  Readers should find the answer by scanning headings and opening lines.\n- **Choose the useful format.** Use bullets for parallel points, numbers for ordered steps, and tables for comparisons.\n  Use diagrams for relationships or branching processes. Keep connected explanations in short prose.\n  Add an artifact only when it reduces reading effort. Avoid long lists, wide tables, and decorative visuals.\n- **Keep alternatives accessible.** Explain a visual's useful point in nearby text. Supply meaningful text alternatives for images.\n  Label table columns and keep cells short. Never make color, position, or an icon the only carrier of meaning.\n  Use whitespace and restrained emphasis. Avoid full paragraphs in bold, italics, or capitals.\n\nLeave clear sentences and useful headings unchanged. Do not split sentences mechanically or add filler for rhythm.\nPreserve stable anchors and check affected links when changing headings.\nKeep exact code, commands, names, numbers, units, attribution, uncertainty, and required wording.\nKeep conditions, negation, exceptions, permissions, and step order attached to their actions.\nNever invent an actor, explanation, experience, or example to make a passage sound clearer.\nDo not use em dashes or hyphens as sentence punctuation in new prose.\n\n## Deliver the requested pass\n\nFor review only, return concrete reading problems and proposed repairs. Leave the source unchanged.\nFor an edit, change only passages with a reading problem. Explain meaningful repairs outside the edited text.\nBefore delivery, check that the reader can find the answer, understand the terms, and follow the required steps.\nCheck whether the whole output fits the predicted attention and gives the important points enough depth.\nCompare the result with the source for changed claims, conditions, uncertainty, and voice.\nIf rendering is available, inspect the actual output at a narrow width. Otherwise report that limit when relevant.\nIf no repair is needed, say so. Do not invent findings or claim an accessibility audit passed.\n",{"name":5,"license":15,"description":7},"main","b80e2f4ae79b4bc439817242bae19b0827730d1f","skills\u002Fclarity",0,"https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly","https:\u002F\u002Fbrundlefly.dev","https:\u002F\u002Fgithub.com\u002Fharlan-zw","https:\u002F\u002Fharlanzw.com","Self-funded open-sourcing at @nuxt ◦ @vueuse ◦ @unjs","2026-10-31 10:30:35",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add harlan-zw\u002Fbrundlefly --skill clarity",{"tool":41,"command":42},"bunx","bunx skills add harlan-zw\u002Fbrundlefly --skill clarity",{"tool":44,"command":45},"pnpm","pnpm dlx skills add harlan-zw\u002Fbrundlefly --skill clarity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fclarity\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1092,[55,63,71,79,87,95],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":20},"01M7DMX465EDXGNN79ANTB8VXQ","verify-examples","Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fverify-examples\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fverify-examples\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":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":20},"01M7DMWY727N5VRQJJ19KB176S","technical-guide","Writes, verifies, or refreshes technical guides: tutorials, how-to guides, and developer documentation, checked against current code and official sources. Use whenever someone asks for a tutorial or how-to, asks to document how developers do a task, or asks to update stale docs, even when the guide looks short.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-guide\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"01M7DMWSAP20A0CR67CV4ZE1J1","slop-naming-recovery","Finds generic technical names that obscure user tasks and proposes names grounded in the product domain. Use when vague terms enter code, features, UI copy, or GLOSSARY.md, including implicit names and explicitly approved terms.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fslop-naming-recovery\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fslop-naming-recovery\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M7DMWMZG8VBHEAYJZZVAG19C","release-notes","Writes or revises release notes, changelogs, release announcements, and upgrade guidance from verified changes. Use when someone asks what a release should say, wants GitHub release notes, or asks to make an existing release article more useful and concise.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Frelease-notes\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Frelease-notes\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":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M7DMWF7C3EARXX428A6227S1","readme","Creates or refreshes a repository README: splash, project story, supported positioning, features, verified setup, and guides or API reference. Use whenever someone asks to write a README, explain why to adopt a project, or fix an outdated README section such as install or quickstart steps.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Freadme\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Freadme\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M7DMWAQRD68G6YVWWPXTQER2","pull-request-summary","Drafts, revises, or checks a pull request description against the actual diff and the repository's template. Use whenever someone asks for a PR description or body, wants one updated after the scope changed, or wants it checked before publishing, including inside a delivery Skill.","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fpull-request-summary\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fharlan-zw\u002Fbrundlefly\u002Fblob\u002Fmain\u002Fskills\u002Fpull-request-summary\u002FSKILL.md",[],[]]