[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF83DZ8EGWPFAYW5B4T1YH":3,"skill-same:01M6MF83DZ8EGWPFAYW5B4T1YH":75},{"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":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6MF83DZ8EGWPFAYW5B4T1YH","board-meeting",null,"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.","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-board-meeting-skill-d0f40589\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"meeting","board meeting","board","question","suite","for","calls","strategic","loading","multi","founder","use","review","boardroom","decisions","decision","critic","analysis","protocol","memory","2026-11-10 10:12:30",false,"---\nname: \"board-meeting\"\ndescription: \"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: board-protocol\n  updated: 2026-03-05\n  frameworks: 6-phase-board, two-layer-memory, independent-contributions\n---\n\n# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:boardroom, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:boardroom [topic]` — e.g. `\u002Fcs:boardroom Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `~\u002F.claude\u002Fcompany-context.md`\n2. Load Layer 2 approved decisions from `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 14 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO (+ VPE for eng hiring) |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n| Contracts \u002F term sheets \u002F legal exposure | GC, CEO, CFO |\n| Data strategy \u002F training-data rights | CDO, CAIO, GC, CISO |\n| AI strategy \u002F model selection \u002F AI risk | CAIO, CTO, CDO, CFO |\n| Retention \u002F churn \u002F customer success | CCO, CRO, CPO |\n| Eng delivery \u002F DORA \u002F team structure | VPE, CTO, CHRO, CFO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO → GC → CDO → CAIO → CCO → VPE (activated roles only)\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `..\u002Fagent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:boardroom resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-\u003Cslug>.md`\n- **Layer 2:** Write approved decision record → `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-\u003Cslug>.md` and append to the index `~\u002F.claude\u002Fdecisions\u002Fapproved\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n\nUses the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n```\n~\u002F.claude\u002Fdecisions\u002F\n├── raw\u002FYYYY-MM-DD-\u003Cslug>.md        # Layer 1 — full transcripts (never auto-loaded)\n├── raw\u002Farchive\u002FYYYY\u002F               # Raw transcripts after 90 days\n├── approved\u002FYYYY-MM-DD-\u003Cslug>.md   # Layer 2 — founder-approved records (Phase 1 loads these)\n└── approved\u002Fdecisions.md           # Layer 2 index — append-only\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\nMigration: a legacy `memory\u002Fboard-meetings\u002F` folder may exist from earlier versions; read it for history but write new transcripts and decisions to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n","# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:boardroom, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:boardroom [topic]` — e.g. `\u002Fcs:boardroom Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `~\u002F.claude\u002Fcompany-context.md`\n2. Load Layer 2 approved decisions from `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 14 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO (+ VPE for eng hiring) |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n| Contracts \u002F term sheets \u002F legal exposure | GC, CEO, CFO |\n| Data strategy \u002F training-data rights | CDO, CAIO, GC, CISO |\n| AI strategy \u002F model selection \u002F AI risk | CAIO, CTO, CDO, CFO |\n| Retention \u002F churn \u002F customer success | CCO, CRO, CPO |\n| Eng delivery \u002F DORA \u002F team structure | VPE, CTO, CHRO, CFO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO → GC → CDO → CAIO → CCO → VPE (activated roles only)\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `..\u002Fagent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:boardroom resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-\u003Cslug>.md`\n- **Layer 2:** Write approved decision record → `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-\u003Cslug>.md` and append to the index `~\u002F.claude\u002Fdecisions\u002Fapproved\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n\nUses the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n```\n~\u002F.claude\u002Fdecisions\u002F\n├── raw\u002FYYYY-MM-DD-\u003Cslug>.md        # Layer 1 — full transcripts (never auto-loaded)\n├── raw\u002Farchive\u002FYYYY\u002F               # Raw transcripts after 90 days\n├── approved\u002FYYYY-MM-DD-\u003Cslug>.md   # Layer 2 — founder-approved records (Phase 1 loads these)\n└── approved\u002Fdecisions.md           # Layer 2 index — append-only\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\nMigration: a legacy `memory\u002Fboard-meetings\u002F` folder may exist from earlier versions; read it for history but write new transcripts and decisions to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n",{"name":5,"license":14,"metadata":48,"description":7},{"author":49,"domain":50,"updated":51,"version":52,"category":53,"frameworks":54},"Alireza Rezvani","board-protocol",1772668800000,"1.0.0","c-level","6-phase-board, two-layer-memory, independent-contributions","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-board-meeting-skill-d0f40589","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill board-meeting",{"tool":67,"command":68},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill board-meeting",{"tool":70,"command":71},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill board-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-board-meeting-skill-d0f40589\u002FSKILL.md",true,[],[76,100,128,161,189,222],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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",[],[78,83,84,85,86,87,88,89,90,91,92,93,94,34,95,96,97,98,28,99],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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",[],[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":142,"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",[134,139],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":140,"categoryName":141,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000023","Skill与智能体开发",[143,144,145,146,147,148,149,150,151,152,153,154,155,34,156,157,158,159,28,160],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"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",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000011","运维与部署",[171,172,173,174,175,176,177,178,179,34,180,181,182,183,184,185,186,187,188,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":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":204,"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",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源",[205,206,207,208,209,210,211,212,109,213,34,214,215,216,217,218,219,220,28,221],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"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",[],[229,230,231,232,233,208,234,34,218,235,236,237,238,239,240,241,242,243,28,244],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]