[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H5C3CFW42FS6BKSSTNWVWX":3,"skill-same:01M6H5C3CFW42FS6BKSSTNWVWX":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":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6H5C3CFW42FS6BKSSTNWVWX","strategic-clarity",null,"Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define \"what we own\" vs \"what we don't\". Triggers include \"strategic clarity\", \"team identity\", \"new role\", \"inherited ambiguity\", \"what does my team own\", or \"define our boundaries\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fproductivity\u002Fpm-ai-partner\u002Fskills\u002Fstrategic-clarity\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"strategic clarity","clarity","strategic","define","for","role","my","ambiguity","you","clear","triggers","gmail","align","use","read","grep","team","audit","identity","workflow","2026-11-10 10:12:30",false,"---\nname: strategic-clarity\ndescription: Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define \"what we own\" vs \"what we don't\". Triggers include \"strategic clarity\", \"team identity\", \"new role\", \"inherited ambiguity\", \"what does my team own\", or \"define our boundaries\".\nversion: 1.0.0\nauthor: Ahmed Khaled Mohamed \u003Cahmd.khaled.a.mohamed@gmail.com>\nlicense: MIT\nallowed-tools: Read, Glob, Grep\nargument-hint: [phase: absorb\u002Faudit\u002Farticulate\u002Falign]\n---\n\n# Strategic Clarity Workflow\n\n## Overview\n\nA 4-phase workflow for establishing team identity and strategic positioning.\n\n```\n+---------+    +---------+    +-----------+    +---------+\n| ABSORB  | -> |  AUDIT  | -> | ARTICULATE| -> |  ALIGN  |\n|         |    |         |    |           |    |         |\n| Context |    | Reality |    | Identity  |    | Buy-in  |\n+---------+    +---------+    +-----------+    +---------+\n```\n\n**When to use:** Starting a new role, inherited ambiguity, team lacks clear identity\n**Output:** Team charter, value proposition, capability audit\n\n### Advanced Patterns\n\n1. **The inherited narrative trap** — When you inherit a team, everyone will tell you what the team does. Their descriptions will conflict. Don't average them — map the contradictions. Where people disagree about team scope is exactly where boundaries are unclear and where future conflicts will emerge. The contradictions are the diagnosis\n2. **Capability vs. responsibility** — Teams often confuse what they *can* do with what they *should* do. A messaging team that *can* build email doesn't mean email is their responsibility. During the audit phase, separate capabilities (what the code does) from responsibilities (what stakeholders expect). Mismatches between these create the biggest organizational friction\n3. **The \"without us\" test** — To find your team's real value, ask: \"If our team disappeared tomorrow, what would break first?\" The thing that breaks first is your core value. The thing that breaks second is your growth opportunity. The thing nobody notices is your candidate for deprecation. This test cuts through aspirational mission statements to find ground truth\n4. **Adjacent team mapping** — Don't just define what you own. Explicitly define the boundary with each adjacent team: \"We own the push delivery pipeline. Platform team owns the notification scheduling. We hand off at [specific interface].\" Vague boundaries between teams cause more organizational damage than vague team charters. Name the seams\n5. **The 30-60-90 checkpoint** — Strategic clarity isn't a one-time exercise. At 30 days, you should have hypotheses. At 60 days, you should have a charter draft. At 90 days, you should have stakeholder alignment. If you're still \"absorbing\" at day 60, you're avoiding the hard work of articulating a position. Set a deadline for yourself\n\n## How This Skill Works\n\nI'll guide you through each phase with:\n1. **Questions** to gather context\n2. **Activities** to complete\n3. **AI-assisted prompts** for each deliverable\n4. **Checklists** to track progress\n\nTell me which phase you're in (or starting fresh), and I'll help you through it.\n\n---\n\n## Phase 1: ABSORB (Week 1)\n\n### Goal\nUnderstand what exists before forming opinions.\n\n### Activities\n- Read all existing documentation\n- Meet with team members\n- Study handover notes\n- Review historical decisions\n\n### AI Assistance\n\n**Prompt: Synthesize Context**\nShare your notes and I'll help you:\n1. Identify key themes\n2. Surface tensions or contradictions\n3. List what's still unclear\n\n**Prompt: Question Generation**\nBased on your context, I'll suggest:\n- Questions you should be asking\n- Who to talk to for answers\n- What documents to read next\n\n### Phase 1 Checklist\n- [ ] Reading notes captured\n- [ ] Key questions documented\n- [ ] Initial mental model forming\n\n---\n\n## Phase 2: AUDIT (Week 2)\n\n### Goal\nUnderstand what actually exists vs. what's claimed.\n\n### Activities\n- Systematic codebase review\n- Map capabilities to code\n- Identify gaps\n- Compare reality to documentation\n\n### AI Assistance\n\n**Prompt: Capability Mapping**\nShare your team's claimed responsibilities and I'll help build an audit template:\n- Capability name\n- Status (exists\u002Fpartial\u002Fmissing)\n- Evidence (code files\u002Fpatterns)\n- Gap description\n- Impact assessment\n\n**Prompt: Codebase Exploration**\nPoint me at code or systems and I'll help you understand:\n- What product capability it represents\n- The business logic encoded\n- Use cases supported\n- What's notably missing\n\n### Phase 2 Checklist\n- [ ] Capability audit document created\n- [ ] Gap inventory prioritized\n- [ ] Reality vs. perception documented\n\n### Output: Capability Audit Template\n\n```markdown\n# Capability Audit: [Team Name]\n\n| Capability | Status | Evidence | Gap | Impact |\n|------------|--------|----------|-----|--------|\n| [Capability 1] | Exists | [code\u002Fsystem] | — | — |\n| [Capability 2] | Partial | [code\u002Fsystem] | [missing piece] | [user impact] |\n| [Capability 3] | Missing | — | [full description] | [business impact] |\n```\n\n---\n\n## Phase 3: ARTICULATE (Week 3)\n\n### Goal\nDefine and document team identity clearly.\n\n### Activities\n- Draft mission statement\n- Define responsibility boundaries\n- Create value proposition\n- Build communication frameworks\n\n### AI Assistance\n\n**Prompt: Mission Drafting**\nShare what you actually own vs. don't own, and I'll help draft:\n- Clear mission statement\n- Distinction from adjacent teams\n- Concrete, not vague language\n\n**Prompt: Charter Structure**\nI'll help structure a one-page team charter:\n- What we're accountable for\n- What we explicitly don't own\n- How we create value\n- Key metrics we move\n\n**Prompt: Value Narrative**\nI'll help create communication frameworks:\n- One-sentence pitch\n- \"Without us, [consequence]\" statements\n- Boundary explanations for adjacent teams\n- Leadership-friendly framing\n\n### Phase 3 Checklist\n- [ ] Team charter drafted\n- [ ] Value proposition documented\n- [ ] Boundary contract defined\n\n### Output: Team Charter Template\n\n```markdown\n# [Team Name] Charter\n\n## Mission\n[One sentence: what we do and why it matters]\n\n## We Own\n- [Responsibility 1]\n- [Responsibility 2]\n- [Responsibility 3]\n\n## We Don't Own\n- [Adjacent area 1] — owned by [other team]\n- [Adjacent area 2] — owned by [other team]\n\n## Value Proposition\nWithout us: [what breaks or doesn't exist]\nWith us: [what users\u002Fbusiness gets]\n\n## Key Metrics\n- [Primary metric we move]\n- [Secondary metric]\n\n## Boundaries\n| Area | Us | Them |\n|------|----|----- |\n| [Shared area] | [Our part] | [Their part] |\n```\n\n---\n\n## Phase 4: ALIGN (Week 4)\n\n### Goal\nValidate and socialize the work.\n\n### Activities\n- Present to manager\n- Discuss with peer PMs\n- Gather feedback\n- Iterate based on input\n\n### AI Assistance\n\n**Prompt: Stakeholder Role-Play**\nTell me who you're presenting to and their likely concerns — I'll role-play as them to help you prepare for pushback.\n\n**Prompt: Presentation Polish**\nShare your draft charter and I'll help:\n- Sharpen the language\n- Anticipate objections\n- Add evidence for claims\n- Make it memorable\n\n### Phase 4 Checklist\n- [ ] Manager alignment achieved\n- [ ] Peer PM feedback incorporated\n- [ ] Final documents published\n- [ ] Communication plan for broader sharing\n\n---\n\n## Document Checklist\n\n| Document | Location | Status |\n|----------|----------|--------|\n| Reading notes | `context\u002F` | [ ] |\n| Capability audit | `analysis\u002Fcapability-audit.md` | [ ] |\n| Team charter | `strategy\u002Fteam-charter.md` | [ ] |\n| Value proposition | `strategy\u002Fvalue-proposition.md` | [ ] |\n| Stakeholder map | `analysis\u002Fstakeholder-map.md` | [ ] |\n\n---\n\n## Success Criteria\n\nBy the end of this workflow, you should be able to:\n\n- [ ] Articulate team value in one sentence\n- [ ] Explain boundary with adjacent teams clearly\n- [ ] Have manager endorsement of your framing\n- [ ] Have peer PMs understand what you own\n- [ ] Feed gap inventory into roadmap planning\n\n---\n\n## Getting Started\n\nTell me:\n1. **What's your situation?** (New role? Inherited team? Identity crisis?)\n2. **What phase are you in?** (Or starting fresh?)\n3. **What do you have so far?** (Notes? Docs? Nothing?)\n\nI'll guide you through the appropriate phase.\n","# Strategic Clarity Workflow\n\n## Overview\n\nA 4-phase workflow for establishing team identity and strategic positioning.\n\n```\n+---------+    +---------+    +-----------+    +---------+\n| ABSORB  | -> |  AUDIT  | -> | ARTICULATE| -> |  ALIGN  |\n|         |    |         |    |           |    |         |\n| Context |    | Reality |    | Identity  |    | Buy-in  |\n+---------+    +---------+    +-----------+    +---------+\n```\n\n**When to use:** Starting a new role, inherited ambiguity, team lacks clear identity\n**Output:** Team charter, value proposition, capability audit\n\n### Advanced Patterns\n\n1. **The inherited narrative trap** — When you inherit a team, everyone will tell you what the team does. Their descriptions will conflict. Don't average them — map the contradictions. Where people disagree about team scope is exactly where boundaries are unclear and where future conflicts will emerge. The contradictions are the diagnosis\n2. **Capability vs. responsibility** — Teams often confuse what they *can* do with what they *should* do. A messaging team that *can* build email doesn't mean email is their responsibility. During the audit phase, separate capabilities (what the code does) from responsibilities (what stakeholders expect). Mismatches between these create the biggest organizational friction\n3. **The \"without us\" test** — To find your team's real value, ask: \"If our team disappeared tomorrow, what would break first?\" The thing that breaks first is your core value. The thing that breaks second is your growth opportunity. The thing nobody notices is your candidate for deprecation. This test cuts through aspirational mission statements to find ground truth\n4. **Adjacent team mapping** — Don't just define what you own. Explicitly define the boundary with each adjacent team: \"We own the push delivery pipeline. Platform team owns the notification scheduling. We hand off at [specific interface].\" Vague boundaries between teams cause more organizational damage than vague team charters. Name the seams\n5. **The 30-60-90 checkpoint** — Strategic clarity isn't a one-time exercise. At 30 days, you should have hypotheses. At 60 days, you should have a charter draft. At 90 days, you should have stakeholder alignment. If you're still \"absorbing\" at day 60, you're avoiding the hard work of articulating a position. Set a deadline for yourself\n\n## How This Skill Works\n\nI'll guide you through each phase with:\n1. **Questions** to gather context\n2. **Activities** to complete\n3. **AI-assisted prompts** for each deliverable\n4. **Checklists** to track progress\n\nTell me which phase you're in (or starting fresh), and I'll help you through it.\n\n---\n\n## Phase 1: ABSORB (Week 1)\n\n### Goal\nUnderstand what exists before forming opinions.\n\n### Activities\n- Read all existing documentation\n- Meet with team members\n- Study handover notes\n- Review historical decisions\n\n### AI Assistance\n\n**Prompt: Synthesize Context**\nShare your notes and I'll help you:\n1. Identify key themes\n2. Surface tensions or contradictions\n3. List what's still unclear\n\n**Prompt: Question Generation**\nBased on your context, I'll suggest:\n- Questions you should be asking\n- Who to talk to for answers\n- What documents to read next\n\n### Phase 1 Checklist\n- [ ] Reading notes captured\n- [ ] Key questions documented\n- [ ] Initial mental model forming\n\n---\n\n## Phase 2: AUDIT (Week 2)\n\n### Goal\nUnderstand what actually exists vs. what's claimed.\n\n### Activities\n- Systematic codebase review\n- Map capabilities to code\n- Identify gaps\n- Compare reality to documentation\n\n### AI Assistance\n\n**Prompt: Capability Mapping**\nShare your team's claimed responsibilities and I'll help build an audit template:\n- Capability name\n- Status (exists\u002Fpartial\u002Fmissing)\n- Evidence (code files\u002Fpatterns)\n- Gap description\n- Impact assessment\n\n**Prompt: Codebase Exploration**\nPoint me at code or systems and I'll help you understand:\n- What product capability it represents\n- The business logic encoded\n- Use cases supported\n- What's notably missing\n\n### Phase 2 Checklist\n- [ ] Capability audit document created\n- [ ] Gap inventory prioritized\n- [ ] Reality vs. perception documented\n\n### Output: Capability Audit Template\n\n```markdown\n# Capability Audit: [Team Name]\n\n| Capability | Status | Evidence | Gap | Impact |\n|------------|--------|----------|-----|--------|\n| [Capability 1] | Exists | [code\u002Fsystem] | — | — |\n| [Capability 2] | Partial | [code\u002Fsystem] | [missing piece] | [user impact] |\n| [Capability 3] | Missing | — | [full description] | [business impact] |\n```\n\n---\n\n## Phase 3: ARTICULATE (Week 3)\n\n### Goal\nDefine and document team identity clearly.\n\n### Activities\n- Draft mission statement\n- Define responsibility boundaries\n- Create value proposition\n- Build communication frameworks\n\n### AI Assistance\n\n**Prompt: Mission Drafting**\nShare what you actually own vs. don't own, and I'll help draft:\n- Clear mission statement\n- Distinction from adjacent teams\n- Concrete, not vague language\n\n**Prompt: Charter Structure**\nI'll help structure a one-page team charter:\n- What we're accountable for\n- What we explicitly don't own\n- How we create value\n- Key metrics we move\n\n**Prompt: Value Narrative**\nI'll help create communication frameworks:\n- One-sentence pitch\n- \"Without us, [consequence]\" statements\n- Boundary explanations for adjacent teams\n- Leadership-friendly framing\n\n### Phase 3 Checklist\n- [ ] Team charter drafted\n- [ ] Value proposition documented\n- [ ] Boundary contract defined\n\n### Output: Team Charter Template\n\n```markdown\n# [Team Name] Charter\n\n## Mission\n[One sentence: what we do and why it matters]\n\n## We Own\n- [Responsibility 1]\n- [Responsibility 2]\n- [Responsibility 3]\n\n## We Don't Own\n- [Adjacent area 1] — owned by [other team]\n- [Adjacent area 2] — owned by [other team]\n\n## Value Proposition\nWithout us: [what breaks or doesn't exist]\nWith us: [what users\u002Fbusiness gets]\n\n## Key Metrics\n- [Primary metric we move]\n- [Secondary metric]\n\n## Boundaries\n| Area | Us | Them |\n|------|----|----- |\n| [Shared area] | [Our part] | [Their part] |\n```\n\n---\n\n## Phase 4: ALIGN (Week 4)\n\n### Goal\nValidate and socialize the work.\n\n### Activities\n- Present to manager\n- Discuss with peer PMs\n- Gather feedback\n- Iterate based on input\n\n### AI Assistance\n\n**Prompt: Stakeholder Role-Play**\nTell me who you're presenting to and their likely concerns — I'll role-play as them to help you prepare for pushback.\n\n**Prompt: Presentation Polish**\nShare your draft charter and I'll help:\n- Sharpen the language\n- Anticipate objections\n- Add evidence for claims\n- Make it memorable\n\n### Phase 4 Checklist\n- [ ] Manager alignment achieved\n- [ ] Peer PM feedback incorporated\n- [ ] Final documents published\n- [ ] Communication plan for broader sharing\n\n---\n\n## Document Checklist\n\n| Document | Location | Status |\n|----------|----------|--------|\n| Reading notes | `context\u002F` | [ ] |\n| Capability audit | `analysis\u002Fcapability-audit.md` | [ ] |\n| Team charter | `strategy\u002Fteam-charter.md` | [ ] |\n| Value proposition | `strategy\u002Fvalue-proposition.md` | [ ] |\n| Stakeholder map | `analysis\u002Fstakeholder-map.md` | [ ] |\n\n---\n\n## Success Criteria\n\nBy the end of this workflow, you should be able to:\n\n- [ ] Articulate team value in one sentence\n- [ ] Explain boundary with adjacent teams clearly\n- [ ] Have manager endorsement of your framing\n- [ ] Have peer PMs understand what you own\n- [ ] Feed gap inventory into roadmap planning\n\n---\n\n## Getting Started\n\nTell me:\n1. **What's your situation?** (New role? Inherited team? Identity crisis?)\n2. **What phase are you in?** (Or starting fresh?)\n3. **What do you have so far?** (Notes? Docs? Nothing?)\n\nI'll guide you through the appropriate phase.\n",{"name":5,"author":48,"license":14,"version":49,"description":7,"allowed-tools":50,"argument-hint":51},"Ahmed Khaled Mohamed \u003Cahmd.khaled.a.mohamed@gmail.com>","1.0.0","Read, Glob, Grep",[52],{"phase":53},"absorb\u002Faudit\u002Farticulate\u002Falign","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fproductivity\u002Fpm-ai-partner\u002Fskills\u002Fstrategic-clarity",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add micsapp\u002Fmicstec-skills --skill strategic-clarity",{"tool":67,"command":68},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill strategic-clarity",{"tool":70,"command":71},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill strategic-clarity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fproductivity\u002Fpm-ai-partner\u002Fskills\u002Fstrategic-clarity\u002FSKILL.md",true,[],[76,109,137,157,177,202],{"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":90,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[82,85],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[91,92,93,94,95,96,97,98,99,100,39,101,102,103,104,105,106,107,108,27],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":121,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[115,116,119,120],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[122,123,124,125,92,126,127,128,129,130,131,132,100,39,106,133,134,107,135,136],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[143],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},[145,146,147,148,92,95,100,39,149,36,150,151,152,153,154,107,155,156,136,27],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"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":165,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[163,164],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[166,148,167,100,151,168,92,122,169,170,171,172,39,173,107,174,175,176,108,27],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[184,185,186,124,187,188,189,190,100,191,192,193,194,195,196,197,198,199,200,201],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[204,209,210,211,212,213,214,36,215,216],"npm","js","calculate","node","math","user","compute","errors"]