[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE9M8RZC12J3NQQMXYQ9KC":3,"skill-same:01M6AE9M8RZC12J3NQQMXYQ9KC":100},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AE9M8RZC12J3NQQMXYQ9KC","curviate",null,"Entry point for driving LinkedIn work through the Curviate CLI: which skill answers which task, how to resolve the `curviate` binary, the retrieval-mode concept and the flags only four commands accept, and the rule that an agent branches on the exit code rather than on the message text. Use whenever a task involves LinkedIn profiles, companies, search, messages, posts, comments, reactions, connections, follows, job postings, Sales Navigator or Recruiter, or whenever a `curviate` command is about to run and it is not obvious which area covers it.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"text","mode","which","posts","how to","reactions","commands","message","branches","only","command","work","cli","how","Recruiting","navigator","messages","https","search","code","run","plugin","github","2026-11-10 10:12:30",false,"---\nname: curviate\ndescription: \"Entry point for driving LinkedIn work through the Curviate CLI: which skill answers which task, how to resolve the `curviate` binary, the retrieval-mode concept and the flags only four commands accept, and the rule that an agent branches on the exit code rather than on the message text. Use whenever a task involves LinkedIn profiles, companies, search, messages, posts, comments, reactions, connections, follows, job postings, Sales Navigator or Recruiter, or whenever a `curviate` command is about to run and it is not obvious which area covers it.\"\nlicense: MIT\nmetadata:\n  version: 0.1.0\n  author: Curviate\n  tags: [LinkedIn, CLI, Agents, Sales, Recruiting, Outreach]\n  repository: https:\u002F\u002Fgithub.com\u002FCurviate\u002Fcurviate-plugin\n---\n\n# Curviate: start here\n\nCurviate is a LinkedIn API for agents. The `curviate` CLI is its command surface, and this skill is\nthe dispatcher: it says which skill to read, and carries the few rules that apply everywhere. It\ncarries no command syntax: every command, flag and worked example lives in the area skill that owns\nit.\n\nEstablished against CLI `0.33.0`.\n\n## Which skill answers this\n\n| Task | Skill |\n|---|---|\n| First run on a new machine: install, authenticate, connect an account, prove it works. | `curviate-quickstart` |\n| A member profile or a company page. Resolving a human search term into the filter id a search needs. Sessions, stored profiles and connected accounts. | `curviate-profile` |\n| Finding people, companies, posts, jobs, services or groups. Running a pasted LinkedIn search URL. | `curviate-search` |\n| Reading conversations, sending and managing messages, InMail, company-page inboxes. | `curviate-inbox` |\n| Publishing posts, commenting, reacting, the home feed, notifications. | `curviate-engage` |\n| Connection invitations, follows, relations, followers. | `curviate-network` |\n| Job postings: creating, publishing, budgets, applicants. | `curviate-jobs` |\n| Sales Navigator and Recruiter. | `curviate-premium` |\n\nWhen a task spans two areas (find someone, then message them), read both. They are self-sufficient\nand repeat what they need to; nothing is hidden behind a third skill.\n\n## Resolve the binary before anything else\n\n```bash\ncurviate --version    # needs Node 18 or newer\n```\n\nIf that fails, install it: `npm install -g @curviate\u002Fcli`. **Do not substitute a raw HTTP call for a\ncommand you could not find.** The command surface is the contract, and hand-rolled requests miss the\nprojections, the retry contract and the exit-code mapping that every one of these skills is written\nagainst.\n\nCredentials resolve **flag > environment > stored profile**. For a scripted run prefer\n`CURVIATE_API_KEY` in the environment or a stored profile: a key passed as a flag is visible to other\nprocesses through `ps` and is saved in shell history.\n\n## Branch on the exit code, never on the message text\n\nEvery command exits with a code that says what to do next, and under `--json` an error prints\n`{\"error\": {\"code\", \"message\", …}}`. **The code is the contract. The wording is not**: it is written\nfor a human reading a terminal and it changes between releases.\n\nTwo consequences worth internalising before the first failure:\n\n- **A single exit code can carry several distinct causes**, so read `error.code` before deciding on a\n  remedy. Exit `5` alone means three unrelated things whose fixes have nothing in common.\n- **Retrying is right for some codes and actively wrong for others.** A rate limit tells you how long\n  to wait; a refusal by one of your own ceilings will not clear on a retry at all. Each area skill\n  ends with the exit codes reachable from its commands and the action each implies. Read that table\n  rather than guessing from the message.\n\n## Retrieval mode, and the flag of the same name that is not it\n\nSome reads can be answered from a stored copy instead of a live call to LinkedIn, and `--mode` \u002F\n`--max-age` choose between them. Two rules matter everywhere:\n\n- **Exactly four commands accept those flags**: `profile me`, `profile \u003Cid>`, `inbox get` and\n  `inbox messages`. The mechanics (what each mode does, what a store miss returns, and why\n  `cache_only` and `--max-age` cannot be combined) are in `curviate-profile` and `curviate-inbox`.\n- **Every other command refuses them outright rather than ignoring them**: ``unknown flag `--mode` ``\n  at exit `2`, before any network call. That is the good failure. A retrieval-mode habit carried onto\n  a search fails loudly instead of quietly serving you a freshness you did not ask for. The two\n  exceptions below are not retrieval commands either: they refuse retrieval *values*.\n\n**Two commands take a `--mode` that is a different flag wearing the same name, and both spend real\nmoney**: `job publish` and `recruiter job publish`, each `--mode FREE|PROMOTED|PROMOTED_PLUS`. They\nselect how a posting is published. No retrieval value is valid there, and on both the flag is\nrequired rather than optional, so a retrieval habit is refused at exit `2` rather than silently\npromoting a posting. See `curviate-jobs` and `curviate-premium`.\n\n## Reading a response\n\n- **Pass `--json` on anything you parse.** It is already the default when stdout is not a terminal;\n  ask for it explicitly when a human might also be watching.\n- **An empty field in a default response is not proof the data does not exist.** Responses are\n  projected, and several fields are withheld until `--verbose` asks for them, including a few that\n  read exactly like \"this member published nothing\". Each area skill names its own.\n- **`--preview` before a write** renders the resolved request without sending it. On a read command\n  it is refused at exit `2`.\n","# Curviate: start here\n\nCurviate is a LinkedIn API for agents. The `curviate` CLI is its command surface, and this skill is\nthe dispatcher: it says which skill to read, and carries the few rules that apply everywhere. It\ncarries no command syntax: every command, flag and worked example lives in the area skill that owns\nit.\n\nEstablished against CLI `0.33.0`.\n\n## Which skill answers this\n\n| Task | Skill |\n|---|---|\n| First run on a new machine: install, authenticate, connect an account, prove it works. | `curviate-quickstart` |\n| A member profile or a company page. Resolving a human search term into the filter id a search needs. Sessions, stored profiles and connected accounts. | `curviate-profile` |\n| Finding people, companies, posts, jobs, services or groups. Running a pasted LinkedIn search URL. | `curviate-search` |\n| Reading conversations, sending and managing messages, InMail, company-page inboxes. | `curviate-inbox` |\n| Publishing posts, commenting, reacting, the home feed, notifications. | `curviate-engage` |\n| Connection invitations, follows, relations, followers. | `curviate-network` |\n| Job postings: creating, publishing, budgets, applicants. | `curviate-jobs` |\n| Sales Navigator and Recruiter. | `curviate-premium` |\n\nWhen a task spans two areas (find someone, then message them), read both. They are self-sufficient\nand repeat what they need to; nothing is hidden behind a third skill.\n\n## Resolve the binary before anything else\n\n```bash\ncurviate --version    # needs Node 18 or newer\n```\n\nIf that fails, install it: `npm install -g @curviate\u002Fcli`. **Do not substitute a raw HTTP call for a\ncommand you could not find.** The command surface is the contract, and hand-rolled requests miss the\nprojections, the retry contract and the exit-code mapping that every one of these skills is written\nagainst.\n\nCredentials resolve **flag > environment > stored profile**. For a scripted run prefer\n`CURVIATE_API_KEY` in the environment or a stored profile: a key passed as a flag is visible to other\nprocesses through `ps` and is saved in shell history.\n\n## Branch on the exit code, never on the message text\n\nEvery command exits with a code that says what to do next, and under `--json` an error prints\n`{\"error\": {\"code\", \"message\", …}}`. **The code is the contract. The wording is not**: it is written\nfor a human reading a terminal and it changes between releases.\n\nTwo consequences worth internalising before the first failure:\n\n- **A single exit code can carry several distinct causes**, so read `error.code` before deciding on a\n  remedy. Exit `5` alone means three unrelated things whose fixes have nothing in common.\n- **Retrying is right for some codes and actively wrong for others.** A rate limit tells you how long\n  to wait; a refusal by one of your own ceilings will not clear on a retry at all. Each area skill\n  ends with the exit codes reachable from its commands and the action each implies. Read that table\n  rather than guessing from the message.\n\n## Retrieval mode, and the flag of the same name that is not it\n\nSome reads can be answered from a stored copy instead of a live call to LinkedIn, and `--mode` \u002F\n`--max-age` choose between them. Two rules matter everywhere:\n\n- **Exactly four commands accept those flags**: `profile me`, `profile \u003Cid>`, `inbox get` and\n  `inbox messages`. The mechanics (what each mode does, what a store miss returns, and why\n  `cache_only` and `--max-age` cannot be combined) are in `curviate-profile` and `curviate-inbox`.\n- **Every other command refuses them outright rather than ignoring them**: ``unknown flag `--mode` ``\n  at exit `2`, before any network call. That is the good failure. A retrieval-mode habit carried onto\n  a search fails loudly instead of quietly serving you a freshness you did not ask for. The two\n  exceptions below are not retrieval commands either: they refuse retrieval *values*.\n\n**Two commands take a `--mode` that is a different flag wearing the same name, and both spend real\nmoney**: `job publish` and `recruiter job publish`, each `--mode FREE|PROMOTED|PROMOTED_PLUS`. They\nselect how a posting is published. No retrieval value is valid there, and on both the flag is\nrequired rather than optional, so a retrieval habit is refused at exit `2` rather than silently\npromoting a posting. See `curviate-jobs` and `curviate-premium`.\n\n## Reading a response\n\n- **Pass `--json` on anything you parse.** It is already the default when stdout is not a terminal;\n  ask for it explicitly when a human might also be watching.\n- **An empty field in a default response is not proof the data does not exist.** Responses are\n  projected, and several fields are withheld until `--verbose` asks for them, including a few that\n  read exactly like \"this member published nothing\". Each area skill names its own.\n- **`--preview` before a write** renders the resolved request without sending it. On a read command\n  it is refused at exit `2`.\n",{"name":5,"license":15,"metadata":52,"description":7},{"tags":53,"author":59,"version":60,"repository":61},[54,55,56,57,38,58],"LinkedIn","CLI","Agents","Sales","Outreach","Curviate","0.1.0","https:\u002F\u002Fgithub.com\u002FCurviate\u002Fcurviate-plugin","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate",3963,"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-15 01:32:48",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add davila7\u002Fclaude-code-templates --skill curviate",{"tool":78,"command":79},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill curviate",{"tool":81,"command":82},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill curviate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate\u002FSKILL.md",true,[86,92,96],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"AGENT-BRIEF.md","REFERENCE","参考文档",7942,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Ftriage\u002FAGENT-BRIEF.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"agents\u002Fopenai.yaml",135,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"OUT-OF-SCOPE.md",4667,"https:\u002F\u002Fgithub.com\u002Fhareki\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Ftriage\u002FOUT-OF-SCOPE.md",[101,127,152,184,219,243],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":47},"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",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,26,113,114,115,116,117,118,119,120,121,122,123,124,37,125,126],"scoring","pool","wealthville pool scoring","liquidity","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","public","look",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":47},"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",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,136,137,138,139,140,141,142,143,144,145,117,43,146,35,147,148,149,150,151],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","plan","focus","signals","audit","dependency",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":167,"publishedAt":47},"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",[158,161,162],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[168,169,170,171,172,173,174,113,175,176,177,178,179,33,180,116,181,182,117,183],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","MCP","access","database","query",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":188,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":195,"publishedAt":47},"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",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,113,218],"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":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":188,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":230,"publishedAt":47},"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",[226,229],{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},[231,232,233,234,235,197,236,206,207,237,238,239,240,113,241,119,242],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":188,"licenseFileUrl":247,"sourceHtmlUrl":248,"categories":249,"keywords":257,"publishedAt":47},"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",[250,253,254],{"categoryNo":251,"categoryName":252,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":255,"categoryName":256,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000036","内容创作者",[258,259,260,261,44,262,263,264,199,265,209,43,266,267,268,269,270,33,271,117,272,273,274,275,276,37,277],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]