[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF3RFKN1F4G031AXHNQ7P2":3,"skill-same:01M6AF3RFKN1F4G031AXHNQ7P2":99},{"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":34,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6AF3RFKN1F4G031AXHNQ7P2","star-history-chart",null,"Add a self-hosted \"Stargazers over time\" chart to any GitHub repo's README. GitHub now restricts the stargazers endpoint to a repo's own admins\u002Fcollaborators, so third-party live services (star-history free tier, starchart.cc) return \"Requires authentication\" for everyone. This generates a static, theme-aware SVG in-repo and auto-refreshes it weekly with a GitHub Action using the repo's own GITHUB_TOKEN. Use when the star chart in a README is broken, shows \"Requires authentication\", or you want a star history that never breaks.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"star history chart","history","STAR","chart","time","when","static","weekly","action","you","now","free","live","token","github","self","cc","never","auto","broken","endpoint","services","authentication","2026-11-10 10:12:30",false,"---\nname: star-history-chart\ndescription: Add a self-hosted \"Stargazers over time\" chart to any GitHub repo's README. GitHub now restricts the stargazers endpoint to a repo's own admins\u002Fcollaborators, so third-party live services (star-history free tier, starchart.cc) return \"Requires authentication\" for everyone. This generates a static, theme-aware SVG in-repo and auto-refreshes it weekly with a GitHub Action using the repo's own GITHUB_TOKEN. Use when the star chart in a README is broken, shows \"Requires authentication\", or you want a star history that never breaks.\n---\n\n# Star History Chart (self-hosted, never breaks)\n\nAdd a \"Stargazers over time\" chart that renders from a static SVG committed to\nthe repo and refreshes itself weekly — no external chart service, no broken\nimages.\n\n## Why this exists\n\nGitHub now restricts the `\u002Fstargazers` endpoint to a repository's own admins and\ncollaborators. Unauthenticated requests return `{\"message\":\"Requires\nauthentication\"}`, which breaks every third-party live-chart service\n(star-history.com free tier, starchart.cc, etc.) for **all** repos. The only\nreliable fix is to generate the chart yourself with an authenticated token and\ncommit a static image. Inside GitHub Actions, the repo's own `GITHUB_TOKEN` can\nread its own stargazers, so the whole thing runs with zero secrets to configure.\n\n## What this skill sets up\n\n1. `scripts\u002Fgenerate_star_history.py` — fetches stargazers (authenticated),\n   renders a clean, light\u002Fdark-adaptive SVG.\n2. `.github\u002Fworkflows\u002Fstar-history.yml` — weekly cron + manual trigger that\n   regenerates and commits `docs\u002Fstar-history.svg`.\n3. A README section pointing at the local SVG.\n\n## Workflow\n\n### Step 1: Copy the script and workflow into the repo\n\n```bash\nmkdir -p scripts .github\u002Fworkflows docs\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py scripts\u002Fgenerate_star_history.py\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml .github\u002Fworkflows\u002Fstar-history.yml\n```\n\n> The script needs the `requests` package: `pip install requests`.\n> It resolves the repo from `STAR_HISTORY_REPO`, then `GITHUB_REPOSITORY`\n> (set automatically in Actions), then the `origin` git remote — so no edits\n> are required for it to work in a different repo.\n\n### Step 2: Generate the SVG once, locally\n\nUse a token that can read the repo's stargazers (as owner\u002Fcollaborator). The\nGitHub CLI provides one:\n\n```bash\nGITHUB_TOKEN=$(gh auth token) python scripts\u002Fgenerate_star_history.py\n```\n\nThis writes `docs\u002Fstar-history.svg`. For a repo with many thousands of stars the\nfirst run paginates the whole stargazer list and can take a couple of minutes.\n\nVerify it rendered (optional, macOS): `qlmanage -t -s 800 -o . docs\u002Fstar-history.svg`\n\n### Step 3: Add it to the README\n\nAdd or replace the star chart section. Point the image at the **local** SVG.\nSet the link target to wherever you want clicks to go (the repo, a docs page, or\nyour own site):\n\n```markdown\n## Stargazers over time\n[![Stargazers over time](docs\u002Fstar-history.svg)](https:\u002F\u002Fgithub.com\u002FOWNER\u002FREPO\u002Fstargazers)\n```\n\nIf replacing a broken `star-history.com` \u002F `starchart.cc` embed, swap only the\nimage URL to `docs\u002Fstar-history.svg` and keep or update the link target.\n\n### Step 4: Commit\n\n```bash\ngit add scripts\u002Fgenerate_star_history.py .github\u002Fworkflows\u002Fstar-history.yml docs\u002Fstar-history.svg README.md\ngit commit -m \"feat(readme): self-hosted stargazers chart with weekly auto-refresh\"\ngit push\n```\n\n### Step 5: (Optional) Trigger the auto-refresh now\n\nThe workflow runs every Monday at 04:00 UTC. To refresh immediately without\nwaiting: **GitHub → Actions → \"Update Star History\" → Run workflow**.\n\n## Customization\n\n- **Output path** — set `STAR_HISTORY_OUTPUT` (default `docs\u002Fstar-history.svg`).\n- **Different repo** — set `STAR_HISTORY_REPO=owner\u002Fname`.\n- **Colors \u002F size** — edit the `.line`, `.area`, `.dot` CSS and `WIDTH`\u002F`HEIGHT`\n  constants near the top of `generate_star_history.py`. The chart is\n  theme-aware via a `prefers-color-scheme: dark` block, so it looks right in\n  both GitHub light and dark modes.\n- **Refresh cadence** — edit the `cron` expression in the workflow.\n\n## Notes\n\n- No secrets to add: the workflow uses the automatic `GITHUB_TOKEN`.\n- Private repos work too, as long as the token can read the repo.\n- The script uses only `requests` plus the Python standard library.\n","# Star History Chart (self-hosted, never breaks)\n\nAdd a \"Stargazers over time\" chart that renders from a static SVG committed to\nthe repo and refreshes itself weekly — no external chart service, no broken\nimages.\n\n## Why this exists\n\nGitHub now restricts the `\u002Fstargazers` endpoint to a repository's own admins and\ncollaborators. Unauthenticated requests return `{\"message\":\"Requires\nauthentication\"}`, which breaks every third-party live-chart service\n(star-history.com free tier, starchart.cc, etc.) for **all** repos. The only\nreliable fix is to generate the chart yourself with an authenticated token and\ncommit a static image. Inside GitHub Actions, the repo's own `GITHUB_TOKEN` can\nread its own stargazers, so the whole thing runs with zero secrets to configure.\n\n## What this skill sets up\n\n1. `scripts\u002Fgenerate_star_history.py` — fetches stargazers (authenticated),\n   renders a clean, light\u002Fdark-adaptive SVG.\n2. `.github\u002Fworkflows\u002Fstar-history.yml` — weekly cron + manual trigger that\n   regenerates and commits `docs\u002Fstar-history.svg`.\n3. A README section pointing at the local SVG.\n\n## Workflow\n\n### Step 1: Copy the script and workflow into the repo\n\n```bash\nmkdir -p scripts .github\u002Fworkflows docs\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py scripts\u002Fgenerate_star_history.py\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml .github\u002Fworkflows\u002Fstar-history.yml\n```\n\n> The script needs the `requests` package: `pip install requests`.\n> It resolves the repo from `STAR_HISTORY_REPO`, then `GITHUB_REPOSITORY`\n> (set automatically in Actions), then the `origin` git remote — so no edits\n> are required for it to work in a different repo.\n\n### Step 2: Generate the SVG once, locally\n\nUse a token that can read the repo's stargazers (as owner\u002Fcollaborator). The\nGitHub CLI provides one:\n\n```bash\nGITHUB_TOKEN=$(gh auth token) python scripts\u002Fgenerate_star_history.py\n```\n\nThis writes `docs\u002Fstar-history.svg`. For a repo with many thousands of stars the\nfirst run paginates the whole stargazer list and can take a couple of minutes.\n\nVerify it rendered (optional, macOS): `qlmanage -t -s 800 -o . docs\u002Fstar-history.svg`\n\n### Step 3: Add it to the README\n\nAdd or replace the star chart section. Point the image at the **local** SVG.\nSet the link target to wherever you want clicks to go (the repo, a docs page, or\nyour own site):\n\n```markdown\n## Stargazers over time\n[![Stargazers over time](docs\u002Fstar-history.svg)](https:\u002F\u002Fgithub.com\u002FOWNER\u002FREPO\u002Fstargazers)\n```\n\nIf replacing a broken `star-history.com` \u002F `starchart.cc` embed, swap only the\nimage URL to `docs\u002Fstar-history.svg` and keep or update the link target.\n\n### Step 4: Commit\n\n```bash\ngit add scripts\u002Fgenerate_star_history.py .github\u002Fworkflows\u002Fstar-history.yml docs\u002Fstar-history.svg README.md\ngit commit -m \"feat(readme): self-hosted stargazers chart with weekly auto-refresh\"\ngit push\n```\n\n### Step 5: (Optional) Trigger the auto-refresh now\n\nThe workflow runs every Monday at 04:00 UTC. To refresh immediately without\nwaiting: **GitHub → Actions → \"Update Star History\" → Run workflow**.\n\n## Customization\n\n- **Output path** — set `STAR_HISTORY_OUTPUT` (default `docs\u002Fstar-history.svg`).\n- **Different repo** — set `STAR_HISTORY_REPO=owner\u002Fname`.\n- **Colors \u002F size** — edit the `.line`, `.area`, `.dot` CSS and `WIDTH`\u002F`HEIGHT`\n  constants near the top of `generate_star_history.py`. The chart is\n  theme-aware via a `prefers-color-scheme: dark` block, so it looks right in\n  both GitHub light and dark modes.\n- **Refresh cadence** — edit the `cron` expression in the workflow.\n\n## Notes\n\n- No secrets to add: the workflow uses the automatic `GITHUB_TOKEN`.\n- Private repos work too, as long as the token can read the repo.\n- The script uses only `requests` plus the Python standard library.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart",3926,"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-12 14:45:56",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add davila7\u002Fclaude-code-templates --skill star-history-chart",{"tool":79,"command":80},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill star-history-chart",{"tool":82,"command":83},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill star-history-chart","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002FSKILL.md",true,[87,93],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Fstar-history.yml","ASSET","资产文件",1696,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fgenerate_star_history.py","SCRIPT","脚本",7838,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py",[100,126,153,182,217,241],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":58},"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",[106],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,113,114,45,115,40,116,117,118,119,120,121,122,123,124,125],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":58},"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",[132],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[134,135,136,137,138,139,140,141,142,143,144,40,145,146,147,148,149,150,151,152],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":164,"publishedAt":58},"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",[159,162,163],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[165,166,167,168,169,170,171,113,172,173,174,175,176,177,178,115,179,180,40,181],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":186,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":193,"publishedAt":58},"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",[190],{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,113,216],"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":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":186,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":58},"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",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},[229,230,231,232,233,195,234,204,205,235,236,237,238,113,239,117,240],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":242,"name":243,"nameZh":6,"description":244,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":186,"licenseFileUrl":245,"sourceHtmlUrl":246,"categories":247,"keywords":255,"publishedAt":58},"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",[248,251,252],{"categoryNo":249,"categoryName":250,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":253,"categoryName":254,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[256,257,258,259,260,261,262,263,197,264,207,145,265,266,267,268,269,177,270,40,44,271,272,273,274,123,275],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","analysis","claims","argument","assemble","recommendations"]