[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MH3BSNA072THZT25FM2XP2":3,"skill-same:01M6MH3BSNA072THZT25FM2XP2":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6MH3BSNA072THZT25FM2XP2","general-counsel-advisor",null,"General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech), or when user mentions general counsel, GC, legal review, contract risk, term sheet, IP assignment, or regulatory exposure. NOT a substitute for licensed counsel — surfaces questions to bring to qualified attorneys.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-skills-general-counsel-advisor-skill-064a0ffd\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"general counsel advisor","Counsel","general","advisor","scanner","for","employment","bring","mapping","contract","ip","leadership","startups","landscape","review","surfaces","gc","msa","strategy","risk","2026-11-10 10:12:30",false,"---\nname: \"general-counsel-advisor\"\ndescription: \"General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech), or when user mentions general counsel, GC, legal review, contract risk, term sheet, IP assignment, or regulatory exposure. NOT a substitute for licensed counsel — surfaces questions to bring to qualified attorneys.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: general-counsel-leadership\n  updated: 2026-05-12\n  python-tools: contract_risk_scanner.py, term_sheet_analyzer.py\n  frameworks: contract-review, ip-strategy, term-sheet-decoding, regulatory-mapping\n---\n\n# General Counsel Advisor\n\nStrategic legal frameworks for startup General Counsels and founders without one. Contract risk, IP strategy, term sheet decoding, regulatory landscape.\n\nThis is **not legal advice**. It surfaces the right questions to bring to qualified outside counsel and catches the obvious traps before they reach a signature. Treat every output as a starting point for a conversation with a licensed attorney, not as a substitute for one.\n\n## Keywords\n\ngeneral counsel, GC, legal review, contract review, MSA, SaaS agreement, NDA, DPA, employment agreement, contractor agreement, IP assignment, invention assignment, open source license, OSS compliance, term sheet, liquidation preference, anti-dilution, option pool, vesting, acceleration, drag-along, pro-rata, board composition, regulatory, HIPAA, GDPR, CCPA, FDA, MDR, fintech, BSA\u002FAML, money transmitter, AI Act, indemnity, liability cap, force majeure, auto-renewal, choice of law, venue, non-compete, non-solicit\n\n## Quick Start\n\n```bash\n# Scan a contract for risky clauses (uses bundled sample if no path given)\npython scripts\u002Fcontract_risk_scanner.py\npython scripts\u002Fcontract_risk_scanner.py path\u002Fto\u002Fcontract.txt\n\n# Analyze a term sheet for founder-friendliness\npython scripts\u002Fterm_sheet_analyzer.py\npython scripts\u002Fterm_sheet_analyzer.py path\u002Fto\u002Fterm_sheet.json\n```\n\n## Key Questions (ask these first)\n\n- **Who owns the IP being created or shared?** (Founders forget that contractors don't auto-assign IP without a written clause.)\n- **What's the liability cap, and what's carved out?** (Standard: 12 months of fees, with carve-outs for IP infringement, data breach, willful misconduct.)\n- **Is there a DPA in place if any personal data flows?** (GDPR, CCPA, state laws — non-negotiable if EU\u002FCA data is touched.)\n- **What's the termination right, notice period, and auto-renewal trap?** (5-year auto-renew with 60-day notice is a common founder mistake.)\n- **Does this contract or product launch trigger a new regulatory regime?** (Healthcare → HIPAA. Fintech → BSA\u002FAML. Medical device → FDA\u002FMDR.)\n- **For term sheets: liquidation preference, pre-money option pool, anti-dilution flavor?** (Three places where 5% of founder economics can quietly disappear.)\n\n## Core Responsibilities\n\n### 1. Contract Review\n\nStandard contracts a startup signs in its first 5 years:\n\n- **Vendor MSA** — Master Service Agreement (cloud, tooling, services)\n- **Customer SaaS Agreement** — your standard customer paper + customer redlines\n- **NDA** — mutual + one-way, with carve-outs for residuals + independent development\n- **DPA** — Data Processing Agreement (required when personal data flows)\n- **Employment Agreement** — offer letter, IP assignment, non-compete (where enforceable), arbitration\n- **Contractor \u002F 1099 Agreement** — IP assignment is critical; misclassification risk\n- **Equity Agreements** — option grants, RSU agreements, advisor grants (FAST template, YC SAFE for advisors)\n\n**Run** `contract_risk_scanner.py` on the text. It flags the 12 most common founder-killer clauses.\n\n### 2. IP Strategy\n\n- **Invention assignment** — every employee and contractor signs one. No exceptions.\n- **Open source license compliance** — track every OSS dependency's license; AGPL and GPL trigger copyleft obligations.\n- **Trade secrets** — define what's protected and how (clean room dev, access controls, NDAs).\n- **Patents** — file provisional within 12 months of disclosure; PCT for international.\n- **Trademarks** — register the word mark first, design mark second; clear before launch.\n- **Copyright** — automatic on creation, but register for statutory damages eligibility.\n\nSee `references\u002Fip_and_regulatory.md`.\n\n### 3. Term Sheet Decoding\n\nWhen a term sheet arrives, the difference between a founder-friendly and founder-hostile sheet often hides in three clauses:\n\n- **Liquidation preference** — 1x non-participating is standard; 1x participating or 2x is hostile\n- **Pre-money vs post-money option pool** — pre-money pool dilutes founders; post-money dilutes everyone proportionally\n- **Anti-dilution** — broad-based weighted average is standard; full ratchet is hostile\n\n**Run** `term_sheet_analyzer.py` to get a 0-100 founder-friendliness score with flags.\n\n### 4. Regulatory Landscape\n\nWhen to engage outside counsel **before** committing:\n\n| Trigger | Regime | First Step |\n|---|---|---|\n| Healthcare data | HIPAA, HITECH, state breach laws | Specialist health-tech counsel |\n| Cardholder data | PCI DSS (industry standard, not law, but contractually required) | QSA + counsel |\n| Money movement | BSA\u002FAML, state money-transmitter (50-state patchwork) | Fintech specialist |\n| Medical device claims | FDA 510(k) \u002F De Novo \u002F PMA, MDR (EU), ISO 13485 | Medical-device specialist |\n| EU residents' personal data | GDPR + EU AI Act if AI is deployed | EU privacy counsel |\n| California residents | CCPA \u002F CPRA | Privacy generalist |\n| Securities (tokens, equity crowdfunding) | SEC rules (Reg D, Reg A+, Reg CF) | Securities counsel |\n| Defense \u002F aerospace customers | ITAR, EAR, DFARS, CMMC | Export-control counsel |\n| AI in EU | EU AI Act (risk-tiered) | EU privacy + product counsel |\n| AI for hiring (NYC, CO, IL) | Local bias-audit laws | Employment counsel |\n\nSee `references\u002Fip_and_regulatory.md` for sequencing.\n\n## Workflows\n\n### Workflow 1: Contract Review\n1. Save the contract as plain text\n2. Run `contract_risk_scanner.py path\u002Fto\u002Fcontract.txt`\n3. For each HIGH risk finding, draft a counter-proposal\n4. Bring the redline + counter-proposals to outside counsel\n5. Log the decision via `\u002Fcs:decide`\n\n### Workflow 2: Term Sheet Response\n1. Save the term sheet as a JSON file matching the schema in `term_sheet_analyzer.py --help`\n2. Run `python scripts\u002Fterm_sheet_analyzer.py path\u002Fto\u002Fterm_sheet.json`\n3. Review the founder-friendliness score and per-clause flags\n4. Negotiate the worst 3 clauses (don't try to win all 20)\n5. Always have a securities\u002Fventure attorney review before signing\n6. Log via `\u002Fcs:decide` with `\u002Fcs:freeze 30` to prevent regret-driven re-opening\n\n### Workflow 3: IP Hygiene Audit\n1. Confirm every employee and contractor (past 12 months) signed invention assignment\n2. Run an OSS license inventory (`pip-licenses`, `license-checker` for npm)\n3. Map AGPL\u002FGPL dependencies and confirm compliance (or remove)\n4. File provisional patents on novel inventions (12-month deadline from disclosure)\n5. Register word-mark trademarks for the product name\n\n### Workflow 4: Regulatory Trigger Assessment\n1. List planned product features for the next 12 months\n2. Map each feature to the trigger table in this document\n3. For any HIPAA \u002F FDA \u002F fintech trigger, engage a specialist counsel **before** building\n4. Document the regulatory roadmap and budget alongside the product roadmap\n5. Pair with `cs-ciso-advisor` for ISO 27001 \u002F SOC 2 sequencing\n\n## Output Standard (when invoked via `\u002Fcs:gc-review`)\n\n```\n**Bottom Line:** [sign \u002F negotiate \u002F do not sign]\n**The Risks:** [3 highest-severity issues]\n**Counter-Proposals:** [specific language]\n**Outside Counsel Action Items:** [what to bring to the attorney]\n**Your Decision:** [the call only the founder can make]\n```\n\n## Adjacent Skills\n\n- `c-level-advisor\u002Fskills\u002Fciso-advisor\u002F` — Compliance overlap (SOC 2, ISO 27001, HIPAA technical safeguards)\n- `c-level-advisor\u002Fskills\u002Fcfo-advisor\u002F` — Term sheet → dilution math\n- `c-level-advisor\u002Fskills\u002Fma-playbook\u002F` — Acquisition agreements, integration playbooks\n- `ra-qm-team\u002F` — ISO 13485, MDR, FDA 510(k), GDPR execution\n- `c-level-agents\u002Fskills\u002Fgc-review\u002FSKILL.md` — `\u002Fcs:gc-review` slash command\n\n## References\n\n- [contracts_playbook.md](references\u002Fcontracts_playbook.md) — Standard contracts, clause checklist, common founder traps\n- [ip_and_regulatory.md](references\u002Fip_and_regulatory.md) — IP protection + regulatory landscape mapping\n- [term_sheet_decoder.md](references\u002Fterm_sheet_decoder.md) — Term sheet glossary + founder-friendly defaults + pushback strategies\n\n---\n\n**Version:** 1.0.0\n**Status:** Production Ready\n**Disclaimer:** Not legal advice. Always engage qualified counsel for binding decisions.\n","# General Counsel Advisor\n\nStrategic legal frameworks for startup General Counsels and founders without one. Contract risk, IP strategy, term sheet decoding, regulatory landscape.\n\nThis is **not legal advice**. It surfaces the right questions to bring to qualified outside counsel and catches the obvious traps before they reach a signature. Treat every output as a starting point for a conversation with a licensed attorney, not as a substitute for one.\n\n## Keywords\n\ngeneral counsel, GC, legal review, contract review, MSA, SaaS agreement, NDA, DPA, employment agreement, contractor agreement, IP assignment, invention assignment, open source license, OSS compliance, term sheet, liquidation preference, anti-dilution, option pool, vesting, acceleration, drag-along, pro-rata, board composition, regulatory, HIPAA, GDPR, CCPA, FDA, MDR, fintech, BSA\u002FAML, money transmitter, AI Act, indemnity, liability cap, force majeure, auto-renewal, choice of law, venue, non-compete, non-solicit\n\n## Quick Start\n\n```bash\n# Scan a contract for risky clauses (uses bundled sample if no path given)\npython scripts\u002Fcontract_risk_scanner.py\npython scripts\u002Fcontract_risk_scanner.py path\u002Fto\u002Fcontract.txt\n\n# Analyze a term sheet for founder-friendliness\npython scripts\u002Fterm_sheet_analyzer.py\npython scripts\u002Fterm_sheet_analyzer.py path\u002Fto\u002Fterm_sheet.json\n```\n\n## Key Questions (ask these first)\n\n- **Who owns the IP being created or shared?** (Founders forget that contractors don't auto-assign IP without a written clause.)\n- **What's the liability cap, and what's carved out?** (Standard: 12 months of fees, with carve-outs for IP infringement, data breach, willful misconduct.)\n- **Is there a DPA in place if any personal data flows?** (GDPR, CCPA, state laws — non-negotiable if EU\u002FCA data is touched.)\n- **What's the termination right, notice period, and auto-renewal trap?** (5-year auto-renew with 60-day notice is a common founder mistake.)\n- **Does this contract or product launch trigger a new regulatory regime?** (Healthcare → HIPAA. Fintech → BSA\u002FAML. Medical device → FDA\u002FMDR.)\n- **For term sheets: liquidation preference, pre-money option pool, anti-dilution flavor?** (Three places where 5% of founder economics can quietly disappear.)\n\n## Core Responsibilities\n\n### 1. Contract Review\n\nStandard contracts a startup signs in its first 5 years:\n\n- **Vendor MSA** — Master Service Agreement (cloud, tooling, services)\n- **Customer SaaS Agreement** — your standard customer paper + customer redlines\n- **NDA** — mutual + one-way, with carve-outs for residuals + independent development\n- **DPA** — Data Processing Agreement (required when personal data flows)\n- **Employment Agreement** — offer letter, IP assignment, non-compete (where enforceable), arbitration\n- **Contractor \u002F 1099 Agreement** — IP assignment is critical; misclassification risk\n- **Equity Agreements** — option grants, RSU agreements, advisor grants (FAST template, YC SAFE for advisors)\n\n**Run** `contract_risk_scanner.py` on the text. It flags the 12 most common founder-killer clauses.\n\n### 2. IP Strategy\n\n- **Invention assignment** — every employee and contractor signs one. No exceptions.\n- **Open source license compliance** — track every OSS dependency's license; AGPL and GPL trigger copyleft obligations.\n- **Trade secrets** — define what's protected and how (clean room dev, access controls, NDAs).\n- **Patents** — file provisional within 12 months of disclosure; PCT for international.\n- **Trademarks** — register the word mark first, design mark second; clear before launch.\n- **Copyright** — automatic on creation, but register for statutory damages eligibility.\n\nSee `references\u002Fip_and_regulatory.md`.\n\n### 3. Term Sheet Decoding\n\nWhen a term sheet arrives, the difference between a founder-friendly and founder-hostile sheet often hides in three clauses:\n\n- **Liquidation preference** — 1x non-participating is standard; 1x participating or 2x is hostile\n- **Pre-money vs post-money option pool** — pre-money pool dilutes founders; post-money dilutes everyone proportionally\n- **Anti-dilution** — broad-based weighted average is standard; full ratchet is hostile\n\n**Run** `term_sheet_analyzer.py` to get a 0-100 founder-friendliness score with flags.\n\n### 4. Regulatory Landscape\n\nWhen to engage outside counsel **before** committing:\n\n| Trigger | Regime | First Step |\n|---|---|---|\n| Healthcare data | HIPAA, HITECH, state breach laws | Specialist health-tech counsel |\n| Cardholder data | PCI DSS (industry standard, not law, but contractually required) | QSA + counsel |\n| Money movement | BSA\u002FAML, state money-transmitter (50-state patchwork) | Fintech specialist |\n| Medical device claims | FDA 510(k) \u002F De Novo \u002F PMA, MDR (EU), ISO 13485 | Medical-device specialist |\n| EU residents' personal data | GDPR + EU AI Act if AI is deployed | EU privacy counsel |\n| California residents | CCPA \u002F CPRA | Privacy generalist |\n| Securities (tokens, equity crowdfunding) | SEC rules (Reg D, Reg A+, Reg CF) | Securities counsel |\n| Defense \u002F aerospace customers | ITAR, EAR, DFARS, CMMC | Export-control counsel |\n| AI in EU | EU AI Act (risk-tiered) | EU privacy + product counsel |\n| AI for hiring (NYC, CO, IL) | Local bias-audit laws | Employment counsel |\n\nSee `references\u002Fip_and_regulatory.md` for sequencing.\n\n## Workflows\n\n### Workflow 1: Contract Review\n1. Save the contract as plain text\n2. Run `contract_risk_scanner.py path\u002Fto\u002Fcontract.txt`\n3. For each HIGH risk finding, draft a counter-proposal\n4. Bring the redline + counter-proposals to outside counsel\n5. Log the decision via `\u002Fcs:decide`\n\n### Workflow 2: Term Sheet Response\n1. Save the term sheet as a JSON file matching the schema in `term_sheet_analyzer.py --help`\n2. Run `python scripts\u002Fterm_sheet_analyzer.py path\u002Fto\u002Fterm_sheet.json`\n3. Review the founder-friendliness score and per-clause flags\n4. Negotiate the worst 3 clauses (don't try to win all 20)\n5. Always have a securities\u002Fventure attorney review before signing\n6. Log via `\u002Fcs:decide` with `\u002Fcs:freeze 30` to prevent regret-driven re-opening\n\n### Workflow 3: IP Hygiene Audit\n1. Confirm every employee and contractor (past 12 months) signed invention assignment\n2. Run an OSS license inventory (`pip-licenses`, `license-checker` for npm)\n3. Map AGPL\u002FGPL dependencies and confirm compliance (or remove)\n4. File provisional patents on novel inventions (12-month deadline from disclosure)\n5. Register word-mark trademarks for the product name\n\n### Workflow 4: Regulatory Trigger Assessment\n1. List planned product features for the next 12 months\n2. Map each feature to the trigger table in this document\n3. For any HIPAA \u002F FDA \u002F fintech trigger, engage a specialist counsel **before** building\n4. Document the regulatory roadmap and budget alongside the product roadmap\n5. Pair with `cs-ciso-advisor` for ISO 27001 \u002F SOC 2 sequencing\n\n## Output Standard (when invoked via `\u002Fcs:gc-review`)\n\n```\n**Bottom Line:** [sign \u002F negotiate \u002F do not sign]\n**The Risks:** [3 highest-severity issues]\n**Counter-Proposals:** [specific language]\n**Outside Counsel Action Items:** [what to bring to the attorney]\n**Your Decision:** [the call only the founder can make]\n```\n\n## Adjacent Skills\n\n- `c-level-advisor\u002Fskills\u002Fciso-advisor\u002F` — Compliance overlap (SOC 2, ISO 27001, HIPAA technical safeguards)\n- `c-level-advisor\u002Fskills\u002Fcfo-advisor\u002F` — Term sheet → dilution math\n- `c-level-advisor\u002Fskills\u002Fma-playbook\u002F` — Acquisition agreements, integration playbooks\n- `ra-qm-team\u002F` — ISO 13485, MDR, FDA 510(k), GDPR execution\n- `c-level-agents\u002Fskills\u002Fgc-review\u002FSKILL.md` — `\u002Fcs:gc-review` slash command\n\n## References\n\n- [contracts_playbook.md](references\u002Fcontracts_playbook.md) — Standard contracts, clause checklist, common founder traps\n- [ip_and_regulatory.md](references\u002Fip_and_regulatory.md) — IP protection + regulatory landscape mapping\n- [term_sheet_decoder.md](references\u002Fterm_sheet_decoder.md) — Term sheet glossary + founder-friendly defaults + pushback strategies\n\n---\n\n**Version:** 1.0.0\n**Status:** Production Ready\n**Disclaimer:** Not legal advice. Always engage qualified counsel for binding decisions.\n",{"name":5,"license":14,"metadata":48,"description":7},{"author":49,"domain":50,"updated":51,"version":52,"category":53,"frameworks":54,"python-tools":55},"Alireza Rezvani","general-counsel-leadership",1778544000000,"1.0.0","c-level","contract-review, ip-strategy, term-sheet-decoding, regulatory-mapping","contract_risk_scanner.py, term_sheet_analyzer.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-skills-general-counsel-advisor-skill-064a0ffd","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill general-counsel-advisor",{"tool":68,"command":69},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill general-counsel-advisor",{"tool":71,"command":72},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill general-counsel-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-skills-general-counsel-advisor-skill-064a0ffd\u002FSKILL.md",true,[],[77,102,130,163,191,223],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":43},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[79,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,28,101],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","webmcp",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":43},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"publishedAt":43},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[136,141],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":142,"categoryName":143,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000023","Skill与智能体开发",[145,146,147,148,149,150,151,152,153,154,155,156,157,96,158,159,160,161,28,162],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":43},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000011","运维与部署",[173,174,175,176,177,178,179,180,181,96,182,183,184,185,186,187,188,189,190,28],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":206,"publishedAt":43},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[197,200,203],{"categoryNo":198,"categoryName":199,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":201,"categoryName":202,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":204,"categoryName":205,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源",[207,208,209,210,211,212,213,214,111,215,96,216,217,25,218,219,220,221,28,222],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","activate","do","task","cv","letter",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":43},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[230,231,232,233,234,210,235,96,219,236,237,238,239,240,241,242,243,244,28,245],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]