[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MH80GZEKSGYVT1M81DPS7E":3,"skill-same:01M6MH80GZEKSGYVT1M81DPS7E":70},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6MH80GZEKSGYVT1M81DPS7E","strategic-alignment",null,"Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.","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-strategic-alignment-skill-242ee0a4\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"strategic","strategic alignment","alignment","optimize","company","at","checker","directions","cascades","team execution","mapping","orphan","connect","goal","expense","team","analysis","playbook","protocols","communication","2026-11-10 10:12:30",false,"---\nname: \"strategic-alignment\"\ndescription: \"Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: strategic-alignment\n  updated: 2026-03-05\n  python-tools: alignment_checker.py\n  frameworks: alignment-playbook\n---\n\n# Strategic Alignment Engine\n\nStrategy fails at the cascade, not the boardroom. This skill detects misalignment before it becomes dysfunction and builds systems that keep strategy connected from CEO to individual contributor.\n\n## Keywords\nstrategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, alignment checker, strategy articulation, cross-functional, goal cascade, misalignment, alignment score\n\n## Quick Start\n\n```bash\npython scripts\u002Falignment_checker.py    # Check OKR alignment: orphans, conflicts, coverage gaps\n```\n\n## Core Framework\n\nThe alignment problem: **The further a goal gets from the strategy that created it, the less likely it reflects the original intent.** This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.\n\n### Step 1: Strategy Articulation Test\n\nBefore checking cascade, check the source. Ask five people from five different teams:\n**\"What is the company's most important strategic priority right now?\"**\n\n**Scoring:**\n- All five give the same answer: ✅ Articulation is clear\n- 3–4 give similar answers: ? Loose alignment — clarify and communicate\n- \u003C 3 agree: ? Strategy isn't clear enough to cascade. Fix this before fixing cascade.\n\n**Format test:** The strategy should be statable in one sentence. If leadership needs a paragraph, teams won't internalize it.\n- ❌ \"We focus on product-led growth while maintaining enterprise relationships and expanding our international presence and investing in platform capabilities\"\n- ✅ \"Win the mid-market healthcare segment in DACH before Series B\"\n\n### Step 2: Cascade Mapping\n\nMap the flow from company strategy → each level of the organization.\n\n```\nCompany level:  OKR-1, OKR-2, OKR-3\n    ↓\nDept level:     Sales OKRs, Eng OKRs, Product OKRs, CS OKRs\n    ↓\nTeam level:     Team A OKRs, Team B OKRs...\n    ↓\nIndividual:     Personal goals \u002F rocks\n```\n\n**For each goal at every level, ask:**\n- Which company-level goal does this support?\n- If this goal is 100% achieved, how much does it move the company goal?\n- Is the connection direct or theoretical?\n\n### Step 3: Alignment Detection\n\nThree failure patterns:\n\n**Orphan goals:** Team or individual goals that don't connect to any company goal.\n- Symptom: \"We've been working on this for a quarter and nobody above us seems to care\"\n- Root cause: Goals set bottom-up or from last quarter's priorities without reconciling to current company OKRs\n- Fix: Connect or cut. Every goal needs a parent.\n\n**Conflicting goals:** Two teams' goals, when both succeed, create a worse outcome.\n- Classic example: Sales commits to volume contracts (revenue), CS is measured on satisfaction scores. Sales closes bad-fit customers; CS scores tank.\n- Fix: Cross-functional OKR review before quarter begins. Shared metrics where teams interact.\n\n**Coverage gaps:** Company has 3 OKRs. 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3.\n- Symptom: Company OKR-3 consistently misses; nobody owns it\n- Fix: Explicit ownership assignment. If no team owns a company OKR, it won't happen.\n\nSee `scripts\u002Falignment_checker.py` for automated detection against your JSON-formatted OKRs.\n\n### Step 4: Silo Identification\n\nSilos exist when teams optimize for local metrics at the expense of company metrics.\n\n**Silo signals:**\n- A department consistently hits their goals while the company misses\n- Teams don't know what other teams are working on\n- \"That's not our problem\" is a common phrase\n- Escalations only flow up; coordination never flows sideways\n- Data isn't shared between teams that depend on each other\n\n**Silo root causes:**\n1. **Incentive misalignment:** Teams rewarded for local metrics don't optimize for company metrics\n2. **No shared goals:** When teams share a goal, they coordinate. When they don't, they drift.\n3. **No shared language:** Engineering doesn't understand sales metrics; sales doesn't understand technical debt\n4. **Geography or time zones:** Silos accelerate when teams don't interact organically\n\n**Silo measurement:**\n- How often do teams request something from each other vs. proceed independently?\n- How much time does it take to resolve a cross-functional issue?\n- Can a team member describe the current priorities of an adjacent team?\n\n### Step 5: Communication Gap Analysis\n\nWhat the CEO says ≠ what teams hear. The gap grows with company size.\n\n**The message decay model:**\n- CEO communicates strategy at all-hands → managers filter through their lens → teams receive modified version → individuals interpret further\n\n**Gap sources:**\n- **Ambiguity:** Strategy stated at too high a level (\"grow the business\") lets each team fill in their own interpretation\n- **Frequency:** One all-hands per quarter isn't enough repetition to change behavior\n- **Medium mismatch:** Long written strategy doc for teams that respond to visual communication\n- **Trust deficit:** Teams don't believe the strategy is real (\"we've heard this before\")\n\n**Gap detection:**\n- Run the Step 1 articulation test across all levels\n- Compare what leadership thinks they communicated vs. what teams say they heard\n- Survey: \"What changed about how you work since the last strategy update?\"\n\n### Step 6: Realignment Protocol\n\nHow to fix misalignment without calling it a \"realignment\" (which creates fear).\n\n**Step 6a: Don't start with what's wrong**\nStarting with \"here's our misalignment\" creates defensiveness. Start with \"here's where we're heading and I want to make sure we're connected.\"\n\n**Step 6b: Re-cascade in a workshop, not a memo**\nAlignment workshops are more effective than documents. Get company-level OKR owners and department leads in a room. Map connections. Find gaps together.\n\n**Step 6c: Fix incentives before fixing goals**\nIf department heads are rewarded for local metrics that conflict with company goals, no amount of goal-setting fixes the problem. The incentive structure must change first.\n\n**Step 6d: Install a quarterly alignment check**\nAfter fixing, prevent recurrence. See `references\u002Falignment-playbook.md` for quarterly cadence.\n\n---\n\n## Alignment Score\n\nA quick health check. Score each area 0–10:\n\n| Area | Question | Score |\n|------|----------|-------|\n| Strategy clarity | Can 5 people from different teams state the strategy consistently? | \u002F10 |\n| Cascade completeness | Do all team goals connect to company goals? | \u002F10 |\n| Conflict detection | Have cross-team OKR conflicts been reviewed and resolved? | \u002F10 |\n| Coverage | Does each company OKR have explicit team ownership? | \u002F10 |\n| Communication | Do teams' behaviors reflect the strategy (not just their stated understanding)? | \u002F10 |\n\n**Total: __ \u002F 50**\n\n| Score | Status |\n|-------|--------|\n| 45–50 | Excellent. Maintain the system. |\n| 35–44 | Good. Address specific weak areas. |\n| 20–34 | Misalignment is costing you. Immediate attention required. |\n| \u003C 20 | Strategic drift. Treat as crisis. |\n\n---\n\n## Key Questions for Alignment\n\n- \"Ask your newest team member: what is the most important thing the company is trying to achieve right now?\"\n- \"Which company OKR does your team's top priority support? Can you trace the connection?\"\n- \"When Team A and Team B both hit their goals, does the company always win? Are there scenarios where they don't?\"\n- \"What changed in how your team works since the last strategy update?\"\n- \"Name a decision made last week that was influenced by the company strategy.\"\n\n## Red Flags\n\n- Teams consistently hit goals while company misses targets\n- Cross-functional projects take 3x longer than expected (coordination failure)\n- Strategy updated quarterly but team priorities don't change\n- \"That's a leadership problem, not our problem\" attitude at the team level\n- New initiatives announced without connecting them to existing OKRs\n- Department heads optimize for headcount or budget rather than company outcomes\n\n## Integration with Other C-Suite Roles\n\n| When... | Work with... | To... |\n|---------|-------------|-------|\n| New strategy is set | CEO + COO | Cascade into quarterly rocks before announcing |\n| OKR cycle starts | COO | Run cross-team conflict check before finalizing |\n| Team consistently misses goals | CHRO | Diagnose: capability gap or alignment gap? |\n| Silo identified | COO | Design shared metrics or cross-functional OKRs |\n| Post-M&A | CEO + Culture Architect | Detect strategy conflicts between merged entities |\n\n## Detailed References\n- `scripts\u002Falignment_checker.py` — Automated OKR alignment analysis (orphans, conflicts, coverage)\n- `references\u002Falignment-playbook.md` — Cascade techniques, quarterly alignment check, common patterns\n","# Strategic Alignment Engine\n\nStrategy fails at the cascade, not the boardroom. This skill detects misalignment before it becomes dysfunction and builds systems that keep strategy connected from CEO to individual contributor.\n\n## Keywords\nstrategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, alignment checker, strategy articulation, cross-functional, goal cascade, misalignment, alignment score\n\n## Quick Start\n\n```bash\npython scripts\u002Falignment_checker.py    # Check OKR alignment: orphans, conflicts, coverage gaps\n```\n\n## Core Framework\n\nThe alignment problem: **The further a goal gets from the strategy that created it, the less likely it reflects the original intent.** This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.\n\n### Step 1: Strategy Articulation Test\n\nBefore checking cascade, check the source. Ask five people from five different teams:\n**\"What is the company's most important strategic priority right now?\"**\n\n**Scoring:**\n- All five give the same answer: ✅ Articulation is clear\n- 3–4 give similar answers: ? Loose alignment — clarify and communicate\n- \u003C 3 agree: ? Strategy isn't clear enough to cascade. Fix this before fixing cascade.\n\n**Format test:** The strategy should be statable in one sentence. If leadership needs a paragraph, teams won't internalize it.\n- ❌ \"We focus on product-led growth while maintaining enterprise relationships and expanding our international presence and investing in platform capabilities\"\n- ✅ \"Win the mid-market healthcare segment in DACH before Series B\"\n\n### Step 2: Cascade Mapping\n\nMap the flow from company strategy → each level of the organization.\n\n```\nCompany level:  OKR-1, OKR-2, OKR-3\n    ↓\nDept level:     Sales OKRs, Eng OKRs, Product OKRs, CS OKRs\n    ↓\nTeam level:     Team A OKRs, Team B OKRs...\n    ↓\nIndividual:     Personal goals \u002F rocks\n```\n\n**For each goal at every level, ask:**\n- Which company-level goal does this support?\n- If this goal is 100% achieved, how much does it move the company goal?\n- Is the connection direct or theoretical?\n\n### Step 3: Alignment Detection\n\nThree failure patterns:\n\n**Orphan goals:** Team or individual goals that don't connect to any company goal.\n- Symptom: \"We've been working on this for a quarter and nobody above us seems to care\"\n- Root cause: Goals set bottom-up or from last quarter's priorities without reconciling to current company OKRs\n- Fix: Connect or cut. Every goal needs a parent.\n\n**Conflicting goals:** Two teams' goals, when both succeed, create a worse outcome.\n- Classic example: Sales commits to volume contracts (revenue), CS is measured on satisfaction scores. Sales closes bad-fit customers; CS scores tank.\n- Fix: Cross-functional OKR review before quarter begins. Shared metrics where teams interact.\n\n**Coverage gaps:** Company has 3 OKRs. 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3.\n- Symptom: Company OKR-3 consistently misses; nobody owns it\n- Fix: Explicit ownership assignment. If no team owns a company OKR, it won't happen.\n\nSee `scripts\u002Falignment_checker.py` for automated detection against your JSON-formatted OKRs.\n\n### Step 4: Silo Identification\n\nSilos exist when teams optimize for local metrics at the expense of company metrics.\n\n**Silo signals:**\n- A department consistently hits their goals while the company misses\n- Teams don't know what other teams are working on\n- \"That's not our problem\" is a common phrase\n- Escalations only flow up; coordination never flows sideways\n- Data isn't shared between teams that depend on each other\n\n**Silo root causes:**\n1. **Incentive misalignment:** Teams rewarded for local metrics don't optimize for company metrics\n2. **No shared goals:** When teams share a goal, they coordinate. When they don't, they drift.\n3. **No shared language:** Engineering doesn't understand sales metrics; sales doesn't understand technical debt\n4. **Geography or time zones:** Silos accelerate when teams don't interact organically\n\n**Silo measurement:**\n- How often do teams request something from each other vs. proceed independently?\n- How much time does it take to resolve a cross-functional issue?\n- Can a team member describe the current priorities of an adjacent team?\n\n### Step 5: Communication Gap Analysis\n\nWhat the CEO says ≠ what teams hear. The gap grows with company size.\n\n**The message decay model:**\n- CEO communicates strategy at all-hands → managers filter through their lens → teams receive modified version → individuals interpret further\n\n**Gap sources:**\n- **Ambiguity:** Strategy stated at too high a level (\"grow the business\") lets each team fill in their own interpretation\n- **Frequency:** One all-hands per quarter isn't enough repetition to change behavior\n- **Medium mismatch:** Long written strategy doc for teams that respond to visual communication\n- **Trust deficit:** Teams don't believe the strategy is real (\"we've heard this before\")\n\n**Gap detection:**\n- Run the Step 1 articulation test across all levels\n- Compare what leadership thinks they communicated vs. what teams say they heard\n- Survey: \"What changed about how you work since the last strategy update?\"\n\n### Step 6: Realignment Protocol\n\nHow to fix misalignment without calling it a \"realignment\" (which creates fear).\n\n**Step 6a: Don't start with what's wrong**\nStarting with \"here's our misalignment\" creates defensiveness. Start with \"here's where we're heading and I want to make sure we're connected.\"\n\n**Step 6b: Re-cascade in a workshop, not a memo**\nAlignment workshops are more effective than documents. Get company-level OKR owners and department leads in a room. Map connections. Find gaps together.\n\n**Step 6c: Fix incentives before fixing goals**\nIf department heads are rewarded for local metrics that conflict with company goals, no amount of goal-setting fixes the problem. The incentive structure must change first.\n\n**Step 6d: Install a quarterly alignment check**\nAfter fixing, prevent recurrence. See `references\u002Falignment-playbook.md` for quarterly cadence.\n\n---\n\n## Alignment Score\n\nA quick health check. Score each area 0–10:\n\n| Area | Question | Score |\n|------|----------|-------|\n| Strategy clarity | Can 5 people from different teams state the strategy consistently? | \u002F10 |\n| Cascade completeness | Do all team goals connect to company goals? | \u002F10 |\n| Conflict detection | Have cross-team OKR conflicts been reviewed and resolved? | \u002F10 |\n| Coverage | Does each company OKR have explicit team ownership? | \u002F10 |\n| Communication | Do teams' behaviors reflect the strategy (not just their stated understanding)? | \u002F10 |\n\n**Total: __ \u002F 50**\n\n| Score | Status |\n|-------|--------|\n| 45–50 | Excellent. Maintain the system. |\n| 35–44 | Good. Address specific weak areas. |\n| 20–34 | Misalignment is costing you. Immediate attention required. |\n| \u003C 20 | Strategic drift. Treat as crisis. |\n\n---\n\n## Key Questions for Alignment\n\n- \"Ask your newest team member: what is the most important thing the company is trying to achieve right now?\"\n- \"Which company OKR does your team's top priority support? Can you trace the connection?\"\n- \"When Team A and Team B both hit their goals, does the company always win? Are there scenarios where they don't?\"\n- \"What changed in how your team works since the last strategy update?\"\n- \"Name a decision made last week that was influenced by the company strategy.\"\n\n## Red Flags\n\n- Teams consistently hit goals while company misses targets\n- Cross-functional projects take 3x longer than expected (coordination failure)\n- Strategy updated quarterly but team priorities don't change\n- \"That's a leadership problem, not our problem\" attitude at the team level\n- New initiatives announced without connecting them to existing OKRs\n- Department heads optimize for headcount or budget rather than company outcomes\n\n## Integration with Other C-Suite Roles\n\n| When... | Work with... | To... |\n|---------|-------------|-------|\n| New strategy is set | CEO + COO | Cascade into quarterly rocks before announcing |\n| OKR cycle starts | COO | Run cross-team conflict check before finalizing |\n| Team consistently misses goals | CHRO | Diagnose: capability gap or alignment gap? |\n| Silo identified | COO | Design shared metrics or cross-functional OKRs |\n| Post-M&A | CEO + Culture Architect | Detect strategy conflicts between merged entities |\n\n## Detailed References\n- `scripts\u002Falignment_checker.py` — Automated OKR alignment analysis (orphans, conflicts, coverage)\n- `references\u002Falignment-playbook.md` — Cascade techniques, quarterly alignment check, common patterns\n",{"name":5,"license":14,"metadata":43,"description":7},{"author":44,"domain":5,"updated":45,"version":46,"category":47,"frameworks":48,"python-tools":49},"Alireza Rezvani",1772668800000,"1.0.0","c-level","alignment-playbook","alignment_checker.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-strategic-alignment-skill-242ee0a4","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill strategic-alignment",{"tool":62,"command":63},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill strategic-alignment",{"tool":65,"command":66},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill strategic-alignment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-strategic-alignment-skill-242ee0a4\u002FSKILL.md",true,[],[71,97,124,157,185,220],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":38},"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",[],[73,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":38},"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",[],[105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,23,123],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","copilot instructions",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":38},"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",[130,135],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":136,"categoryName":137,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000023","Skill与智能体开发",[139,140,141,142,143,144,145,146,147,148,149,150,151,90,152,153,154,155,95,156],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":38},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000011","运维与部署",[167,168,169,170,171,172,173,174,175,90,176,177,178,179,180,181,182,183,184,95],"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":202,"publishedAt":38},"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",[191,194,199],{"categoryNo":192,"categoryName":193,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":195,"categoryName":196,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":200,"categoryName":201,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000038","人力资源",[203,204,205,206,207,208,209,210,106,211,90,212,213,214,215,216,217,218,95,219],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":38},"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",[],[227,228,229,230,231,206,232,90,216,233,234,235,236,237,238,239,240,241,95,242],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]