[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF3HXD2XAT34B9PZ25HSW4":3,"skill-same:01M6AF3HXD2XAT34B9PZ25HSW4":131},{"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":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6AF3HXD2XAT34B9PZ25HSW4","writing-clearly-and-concisely",null,"Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"writing clearly and concisely","concisely","writing","read","professional writing","when","for","more","timeless","error","professional","reports","use","Rules","text","commit messages","messages","error messages","ui","documentation","commit","2026-11-10 10:12:30",false,"---\nname: writing-clearly-and-concisely\ndescription: Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.\n---\n\n# Writing Clearly and Concisely\n\n## Overview\n\nWrite with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).\n\n## When to Use This Skill\n\nUse this skill whenever you write prose for humans:\n\n- Documentation, README files, technical explanations\n- Commit messages, pull request descriptions\n- Error messages, UI copy, help text, comments\n- Reports, summaries, or any explanation\n- Editing to improve clarity\n\n**If you're writing sentences for a human to read, use this skill.**\n\n## Limited Context Strategy\n\nWhen context is tight:\n\n1. Write your draft using judgment\n2. Dispatch a subagent with your draft and the relevant section file\n3. Have the subagent copyedit and return the revision\n\nLoading a single section (~1,000-4,500 tokens) instead of everything saves significant context.\n\n## Elements of Style\n\nWilliam Strunk Jr.'s *The Elements of Style* (1918) teaches you to write clearly and cut ruthlessly.\n\n### Rules\n\n**Elementary Rules of Usage (Grammar\u002FPunctuation)**:\n\n1. Form possessive singular by adding 's\n2. Use comma after each term in series except last\n3. Enclose parenthetic expressions between commas\n4. Comma before conjunction introducing co-ordinate clause\n5. Don't join independent clauses by comma\n6. Don't break sentences in two\n7. Participial phrase at beginning refers to grammatical subject\n\n**Elementary Principles of Composition**:\n\n8. One paragraph per topic\n9. Begin paragraph with topic sentence\n10. **Use active voice**\n11. **Put statements in positive form**\n12. **Use definite, specific, concrete language**\n13. **Omit needless words**\n14. Avoid succession of loose sentences\n15. Express co-ordinate ideas in similar form\n16. **Keep related words together**\n17. Keep to one tense in summaries\n18. **Place emphatic words at end of sentence**\n\n### Reference Files\n\nThe rules above are summarized from Strunk's original text. For complete explanations with examples:\n\n| Section | File | ~Tokens |\n|---------|------|---------|\n| Grammar, punctuation, comma rules | `02-elementary-rules-of-usage.md` | 2,500 |\n| Paragraph structure, active voice, concision | `03-elementary-principles-of-composition.md` | 4,500 |\n| Headings, quotations, formatting | `04-a-few-matters-of-form.md` | 1,000 |\n| Word choice, common errors | `05-words-and-expressions-commonly-misused.md` | 4,000 |\n\n**Most tasks need only `03-elementary-principles-of-composition.md`** — it covers active voice, positive form, concrete language, and omitting needless words.\n\n## AI Writing Patterns to Avoid\n\nLLMs regress to statistical means, producing generic, puffy prose. Avoid:\n\n- **Puffery:** pivotal, crucial, vital, testament, enduring legacy\n- **Empty \"-ing\" phrases:** ensuring reliability, showcasing features, highlighting capabilities\n- **Promotional adjectives:** groundbreaking, seamless, robust, cutting-edge\n- **Overused AI vocabulary:** delve, leverage, multifaceted, foster, realm, tapestry\n- **Formatting overuse:** excessive bullets, emoji decorations, bold on every other word\n\nBe specific, not grandiose. Say what it actually does.\n\nFor comprehensive research on why these patterns occur, see `signs-of-ai-writing.md`. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.\n\n## Bottom Line\n\nWriting for humans? Load the relevant section from `elements-of-style\u002F` and apply the rules. For most tasks, `03-elementary-principles-of-composition.md` covers what matters most.\n","# Writing Clearly and Concisely\n\n## Overview\n\nWrite with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).\n\n## When to Use This Skill\n\nUse this skill whenever you write prose for humans:\n\n- Documentation, README files, technical explanations\n- Commit messages, pull request descriptions\n- Error messages, UI copy, help text, comments\n- Reports, summaries, or any explanation\n- Editing to improve clarity\n\n**If you're writing sentences for a human to read, use this skill.**\n\n## Limited Context Strategy\n\nWhen context is tight:\n\n1. Write your draft using judgment\n2. Dispatch a subagent with your draft and the relevant section file\n3. Have the subagent copyedit and return the revision\n\nLoading a single section (~1,000-4,500 tokens) instead of everything saves significant context.\n\n## Elements of Style\n\nWilliam Strunk Jr.'s *The Elements of Style* (1918) teaches you to write clearly and cut ruthlessly.\n\n### Rules\n\n**Elementary Rules of Usage (Grammar\u002FPunctuation)**:\n\n1. Form possessive singular by adding 's\n2. Use comma after each term in series except last\n3. Enclose parenthetic expressions between commas\n4. Comma before conjunction introducing co-ordinate clause\n5. Don't join independent clauses by comma\n6. Don't break sentences in two\n7. Participial phrase at beginning refers to grammatical subject\n\n**Elementary Principles of Composition**:\n\n8. One paragraph per topic\n9. Begin paragraph with topic sentence\n10. **Use active voice**\n11. **Put statements in positive form**\n12. **Use definite, specific, concrete language**\n13. **Omit needless words**\n14. Avoid succession of loose sentences\n15. Express co-ordinate ideas in similar form\n16. **Keep related words together**\n17. Keep to one tense in summaries\n18. **Place emphatic words at end of sentence**\n\n### Reference Files\n\nThe rules above are summarized from Strunk's original text. For complete explanations with examples:\n\n| Section | File | ~Tokens |\n|---------|------|---------|\n| Grammar, punctuation, comma rules | `02-elementary-rules-of-usage.md` | 2,500 |\n| Paragraph structure, active voice, concision | `03-elementary-principles-of-composition.md` | 4,500 |\n| Headings, quotations, formatting | `04-a-few-matters-of-form.md` | 1,000 |\n| Word choice, common errors | `05-words-and-expressions-commonly-misused.md` | 4,000 |\n\n**Most tasks need only `03-elementary-principles-of-composition.md`** — it covers active voice, positive form, concrete language, and omitting needless words.\n\n## AI Writing Patterns to Avoid\n\nLLMs regress to statistical means, producing generic, puffy prose. Avoid:\n\n- **Puffery:** pivotal, crucial, vital, testament, enduring legacy\n- **Empty \"-ing\" phrases:** ensuring reliability, showcasing features, highlighting capabilities\n- **Promotional adjectives:** groundbreaking, seamless, robust, cutting-edge\n- **Overused AI vocabulary:** delve, leverage, multifaceted, foster, realm, tapestry\n- **Formatting overuse:** excessive bullets, emoji decorations, bold on every other word\n\nBe specific, not grandiose. Say what it actually does.\n\nFor comprehensive research on why these patterns occur, see `signs-of-ai-writing.md`. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.\n\n## Bottom Line\n\nWriting for humans? Load the relevant section from `elements-of-style\u002F` and apply the rules. For most tasks, `03-elementary-principles-of-composition.md` covers what matters most.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add davila7\u002Fclaude-code-templates --skill writing-clearly-and-concisely",{"tool":71,"command":72},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill writing-clearly-and-concisely",{"tool":74,"command":75},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill writing-clearly-and-concisely","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002FSKILL.md",true,[79,85,89,93,97,101,105,109,113,117,121,127],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"elements-of-style\u002F01-introductory.md","REFERENCE","参考文档",303,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F01-introductory.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"elements-of-style\u002F02-elementary-rules-of-usage.md",12161,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F02-elementary-rules-of-usage.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"elements-of-style\u002F03-elementary-principles-of-composition.md",33622,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F03-elementary-principles-of-composition.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"elements-of-style\u002F04-a-few-matters-of-form.md",4918,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F04-a-few-matters-of-form.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"elements-of-style\u002F05-words-and-expressions-commonly-misused.md",22310,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F05-words-and-expressions-commonly-misused.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"README.md",5853,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002FREADME.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi_examples.md",10348,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Funiprot-database\u002Freferences\u002Fapi_examples.md",{"path":110,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fapi_fields.md",7729,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Funiprot-database\u002Freferences\u002Fapi_fields.md",{"path":114,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fid_mapping_databases.md",6682,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Funiprot-database\u002Freferences\u002Fid_mapping_databases.md",{"path":118,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fquery_syntax.md",6833,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Funiprot-database\u002Freferences\u002Fquery_syntax.md",{"path":122,"resourceType":123,"resourceTypeDesc":124,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Funiprot_client.py","SCRIPT","脚本",9982,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Funiprot-database\u002Fscripts\u002Funiprot_client.py",{"path":128,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":129,"sourceHtmlUrl":130},"signs-of-ai-writing.md",94774,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fwriting-clearly-and-concisely\u002Fsigns-of-ai-writing.md",[132,159,186,217,251,275],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":50},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,146,35,147,148,41,34,149,150,151,152,153,154,155,156,157,158],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":50},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[165],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[167,168,169,170,171,172,173,174,175,176,177,34,178,179,180,181,182,183,184,185],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":199,"publishedAt":50},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[192,195,196],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":197,"categoryName":198,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[200,201,202,203,204,205,206,35,207,208,209,210,211,212,213,41,214,215,34,216],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":221,"licenseFileUrl":222,"sourceHtmlUrl":223,"categories":224,"keywords":228,"publishedAt":50},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[225],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[229,230,231,232,233,234,235,236,237,238,239,47,240,241,242,243,244,245,246,247,248,249,35,250],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":221,"licenseFileUrl":255,"sourceHtmlUrl":256,"categories":257,"keywords":262,"publishedAt":50},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[258,261],{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},[263,264,265,266,267,230,268,239,47,269,270,271,272,35,273,150,274],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":276,"name":277,"nameZh":6,"description":278,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":221,"licenseFileUrl":279,"sourceHtmlUrl":280,"categories":281,"keywords":285,"publishedAt":50},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[282,283,284],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[286,287,288,289,290,291,292,31,232,293,241,178,294,295,296,297,298,212,299,34,300,301,302,303,304,156,305],"discernment nudge","nudge","interpretation","help","run","reasoning","data","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]