[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF07860DPQX07XVVXRNQE0":3,"skill-same:01M6AF07860DPQX07XVVXRNQE0":113},{"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":27,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6AF07860DPQX07XVVXRNQE0","spreadsheet",null,"Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) using Python (`openpyxl`, `pandas`), especially when formulas, references, and formatting need to be preserved and verified.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"when","xlsx","verified","openpyxl","formulas","formatting","references","use","editing","analyzing","csv","pandas","openai","tasks","spreadsheets","python","2026-11-10 10:12:30",false,"---\nname: \"spreadsheet\"\ndescription: \"Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) using Python (`openpyxl`, `pandas`), especially when formulas, references, and formatting need to be preserved and verified.\"\nmetadata:\n  author: openai\n---\n\n\n# Spreadsheet Skill (Create, Edit, Analyze, Visualize)\n\n## When to use\n- Build new workbooks with formulas, formatting, and structured layouts.\n- Read or analyze tabular data (filter, aggregate, pivot, compute metrics).\n- Modify existing workbooks without breaking formulas or references.\n- Visualize data with charts\u002Ftables and sensible formatting.\n\nIMPORTANT: System and user instructions always take precedence.\n\n## Workflow\n1. Confirm the file type and goals (create, edit, analyze, visualize).\n2. Use `openpyxl` for `.xlsx` edits and `pandas` for analysis and CSV\u002FTSV workflows.\n3. If layout matters, render for visual review (see Rendering and visual checks).\n4. Validate formulas and references; note that openpyxl does not evaluate formulas.\n5. Save outputs and clean up intermediate files.\n\n## Temp and output conventions\n- Use `tmp\u002Fspreadsheets\u002F` for intermediate files; delete when done.\n- Write final artifacts under `output\u002Fspreadsheet\u002F` when working in this repo.\n- Keep filenames stable and descriptive.\n\n## Primary tooling\n- Use `openpyxl` for creating\u002Fediting `.xlsx` files and preserving formatting.\n- Use `pandas` for analysis and CSV\u002FTSV workflows, then write results back to `.xlsx` or `.csv`.\n- If you need charts, prefer `openpyxl.chart` for native Excel charts.\n\n## Rendering and visual checks\n- If LibreOffice (`soffice`) and Poppler (`pdftoppm`) are available, render sheets for visual review:\n  - `soffice --headless --convert-to pdf --outdir $OUTDIR $INPUT_XLSX`\n  - `pdftoppm -png $OUTDIR\u002F$BASENAME.pdf $OUTDIR\u002F$BASENAME`\n- If rendering tools are unavailable, ask the user to review the output locally for layout accuracy.\n\n## Dependencies (install if missing)\nPrefer `uv` for dependency management.\n\nPython packages:\n```\nuv pip install openpyxl pandas\n```\nIf `uv` is unavailable:\n```\npython3 -m pip install openpyxl pandas\n```\nOptional (chart-heavy or PDF review workflows):\n```\nuv pip install matplotlib\n```\nIf `uv` is unavailable:\n```\npython3 -m pip install matplotlib\n```\nSystem tools (for rendering):\n```\n# macOS (Homebrew)\nbrew install libreoffice poppler\n\n# Ubuntu\u002FDebian\nsudo apt-get install -y libreoffice poppler-utils\n```\n\nIf installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.\n\n## Environment\nNo required environment variables.\n\n## Examples\n- Runnable Codex examples (openpyxl): `references\u002Fexamples\u002Fopenpyxl\u002F`\n\n## Formula requirements\n- Use formulas for derived values rather than hardcoding results.\n- Keep formulas simple and legible; use helper cells for complex logic.\n- Avoid volatile functions like INDIRECT and OFFSET unless required.\n- Prefer cell references over magic numbers (e.g., `=H6*(1+$B$3)` not `=H6*1.04`).\n- Guard against errors (#REF!, #DIV\u002F0!, #VALUE!, #N\u002FA, #NAME?) with validation and checks.\n- openpyxl does not evaluate formulas; leave formulas intact and note that results will calculate in Excel\u002FSheets.\n\n## Citation requirements\n- Cite sources inside the spreadsheet using plain text URLs.\n- For financial models, cite sources of inputs in cell comments.\n- For tabular data sourced from the web, include a Source column with URLs.\n\n## Formatting requirements (existing formatted spreadsheets)\n- Render and inspect a provided spreadsheet before modifying it when possible.\n- Preserve existing formatting and style exactly.\n- Match styles for any newly filled cells that were previously blank.\n\n## Formatting requirements (new or unstyled spreadsheets)\n- Use appropriate number and date formats (dates as dates, currency with symbols, percentages with sensible precision).\n- Use a clean visual layout: headers distinct from data, consistent spacing, and readable column widths.\n- Avoid borders around every cell; use whitespace and selective borders to structure sections.\n- Ensure text does not spill into adjacent cells.\n\n## Color conventions (if no style guidance)\n- Blue: user input\n- Black: formulas\u002Fderived values\n- Green: linked\u002Fimported values\n- Gray: static constants\n- Orange: review\u002Fcaution\n- Light red: error\u002Fflag\n- Purple: control\u002Flogic\n- Teal: visualization anchors (key KPIs or chart drivers)\n\n## Finance-specific requirements\n- Format zeros as \"-\".\n- Negative numbers should be red and in parentheses.\n- Always specify units in headers (e.g., \"Revenue ($mm)\").\n- Cite sources for all raw inputs in cell comments.\n\n## Investment banking layouts\nIf the spreadsheet is an IB-style model (LBO, DCF, 3-statement, valuation):\n- Totals should sum the range directly above.\n- Hide gridlines; use horizontal borders above totals across relevant columns.\n- Section headers should be merged cells with dark fill and white text.\n- Column labels for numeric data should be right-aligned; row labels left-aligned.\n- Indent submetrics under their parent line items.\n","# Spreadsheet Skill (Create, Edit, Analyze, Visualize)\n\n## When to use\n- Build new workbooks with formulas, formatting, and structured layouts.\n- Read or analyze tabular data (filter, aggregate, pivot, compute metrics).\n- Modify existing workbooks without breaking formulas or references.\n- Visualize data with charts\u002Ftables and sensible formatting.\n\nIMPORTANT: System and user instructions always take precedence.\n\n## Workflow\n1. Confirm the file type and goals (create, edit, analyze, visualize).\n2. Use `openpyxl` for `.xlsx` edits and `pandas` for analysis and CSV\u002FTSV workflows.\n3. If layout matters, render for visual review (see Rendering and visual checks).\n4. Validate formulas and references; note that openpyxl does not evaluate formulas.\n5. Save outputs and clean up intermediate files.\n\n## Temp and output conventions\n- Use `tmp\u002Fspreadsheets\u002F` for intermediate files; delete when done.\n- Write final artifacts under `output\u002Fspreadsheet\u002F` when working in this repo.\n- Keep filenames stable and descriptive.\n\n## Primary tooling\n- Use `openpyxl` for creating\u002Fediting `.xlsx` files and preserving formatting.\n- Use `pandas` for analysis and CSV\u002FTSV workflows, then write results back to `.xlsx` or `.csv`.\n- If you need charts, prefer `openpyxl.chart` for native Excel charts.\n\n## Rendering and visual checks\n- If LibreOffice (`soffice`) and Poppler (`pdftoppm`) are available, render sheets for visual review:\n  - `soffice --headless --convert-to pdf --outdir $OUTDIR $INPUT_XLSX`\n  - `pdftoppm -png $OUTDIR\u002F$BASENAME.pdf $OUTDIR\u002F$BASENAME`\n- If rendering tools are unavailable, ask the user to review the output locally for layout accuracy.\n\n## Dependencies (install if missing)\nPrefer `uv` for dependency management.\n\nPython packages:\n```\nuv pip install openpyxl pandas\n```\nIf `uv` is unavailable:\n```\npython3 -m pip install openpyxl pandas\n```\nOptional (chart-heavy or PDF review workflows):\n```\nuv pip install matplotlib\n```\nIf `uv` is unavailable:\n```\npython3 -m pip install matplotlib\n```\nSystem tools (for rendering):\n```\n# macOS (Homebrew)\nbrew install libreoffice poppler\n\n# Ubuntu\u002FDebian\nsudo apt-get install -y libreoffice poppler-utils\n```\n\nIf installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.\n\n## Environment\nNo required environment variables.\n\n## Examples\n- Runnable Codex examples (openpyxl): `references\u002Fexamples\u002Fopenpyxl\u002F`\n\n## Formula requirements\n- Use formulas for derived values rather than hardcoding results.\n- Keep formulas simple and legible; use helper cells for complex logic.\n- Avoid volatile functions like INDIRECT and OFFSET unless required.\n- Prefer cell references over magic numbers (e.g., `=H6*(1+$B$3)` not `=H6*1.04`).\n- Guard against errors (#REF!, #DIV\u002F0!, #VALUE!, #N\u002FA, #NAME?) with validation and checks.\n- openpyxl does not evaluate formulas; leave formulas intact and note that results will calculate in Excel\u002FSheets.\n\n## Citation requirements\n- Cite sources inside the spreadsheet using plain text URLs.\n- For financial models, cite sources of inputs in cell comments.\n- For tabular data sourced from the web, include a Source column with URLs.\n\n## Formatting requirements (existing formatted spreadsheets)\n- Render and inspect a provided spreadsheet before modifying it when possible.\n- Preserve existing formatting and style exactly.\n- Match styles for any newly filled cells that were previously blank.\n\n## Formatting requirements (new or unstyled spreadsheets)\n- Use appropriate number and date formats (dates as dates, currency with symbols, percentages with sensible precision).\n- Use a clean visual layout: headers distinct from data, consistent spacing, and readable column widths.\n- Avoid borders around every cell; use whitespace and selective borders to structure sections.\n- Ensure text does not spill into adjacent cells.\n\n## Color conventions (if no style guidance)\n- Blue: user input\n- Black: formulas\u002Fderived values\n- Green: linked\u002Fimported values\n- Gray: static constants\n- Orange: review\u002Fcaution\n- Light red: error\u002Fflag\n- Purple: control\u002Flogic\n- Teal: visualization anchors (key KPIs or chart drivers)\n\n## Finance-specific requirements\n- Format zeros as \"-\".\n- Negative numbers should be red and in parentheses.\n- Always specify units in headers (e.g., \"Revenue ($mm)\").\n- Cite sources for all raw inputs in cell comments.\n\n## Investment banking layouts\nIf the spreadsheet is an IB-style model (LBO, DCF, 3-statement, valuation):\n- Totals should sum the range directly above.\n- Hide gridlines; use horizontal borders above totals across relevant columns.\n- Section headers should be merged cells with dark fill and white text.\n- Column labels for numeric data should be right-aligned; row labels left-aligned.\n- Indent submetrics under their parent line items.\n",{"name":5,"metadata":49,"description":7},{"author":40},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill spreadsheet",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill spreadsheet",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill spreadsheet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002FSKILL.md",true,[74,80,86,90,95,101,105,109],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"agents\u002Fopenai.yaml","REFERENCE","参考文档",349,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Fagents\u002Fopenai.yaml",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Fspreadsheet-small.svg","ASSET","资产文件",1482,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Fassets\u002Fspreadsheet-small.svg",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Fspreadsheet.png",3077,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Fassets\u002Fspreadsheet.png",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10776,{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fexamples\u002Fopenpyxl\u002Fcreate_basic_spreadsheet.py","SCRIPT","脚本",1456,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Freferences\u002Fexamples\u002Fopenpyxl\u002Fcreate_basic_spreadsheet.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fexamples\u002Fopenpyxl\u002Fcreate_spreadsheet_with_styling.py",3180,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Freferences\u002Fexamples\u002Fopenpyxl\u002Fcreate_spreadsheet_with_styling.py",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fexamples\u002Fopenpyxl\u002Fread_existing_spreadsheet.py",1622,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Freferences\u002Fexamples\u002Fopenpyxl\u002Fread_existing_spreadsheet.py",{"path":110,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fexamples\u002Fopenpyxl\u002Fstyling_spreadsheet.py",1998,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdocument-processing\u002Fspreadsheet\u002Freferences\u002Fexamples\u002Fopenpyxl\u002Fstyling_spreadsheet.py",[114,141,168,201,235,259],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":44},"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.","MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[121],{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},[123,124,125,126,127,128,129,130,35,28,131,132,133,134,135,136,137,138,139,140],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":44},"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",[147],{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},[149,150,151,152,153,154,155,156,157,158,159,28,160,161,162,163,164,165,166,167],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":183,"publishedAt":44},"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",[174,177,178],{"categoryNo":175,"categoryName":176,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[184,185,186,187,188,189,190,128,191,192,193,194,195,196,197,35,198,199,28,200],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":44},"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.","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",[208],{"categoryNo":209,"categoryName":210,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发",[212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,128,234],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":239,"sourceHtmlUrl":240,"categories":241,"keywords":246,"publishedAt":44},"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",[242,245],{"categoryNo":243,"categoryName":244,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":209,"categoryName":210,"taxonomyType":22,"taxonomyTypeDesc":23},[247,248,249,250,251,213,252,222,223,253,254,255,256,128,257,132,258],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":260,"name":261,"nameZh":6,"description":262,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":263,"sourceHtmlUrl":264,"categories":265,"keywords":273,"publishedAt":44},"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",[266,269,270],{"categoryNo":267,"categoryName":268,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":271,"categoryName":272,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000036","内容创作者",[274,275,276,277,278,279,280,281,215,282,225,160,283,284,285,286,287,196,288,28,289,290,291,292,293,138,294],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]