[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BJBBFKS0WR4F072RJ2HRX":3,"skill-same:01M69BJBBFKS0WR4F072RJ2HRX":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":24,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M69BJBBFKS0WR4F072RJ2HRX","triage-meeting-prep",null,"Prepare weekly triage meeting summary for WinAppSDK Needs-Triage issues. Use when preparing for triage meetings, reviewing Needs-Triage issues, generating diff reports since last triage, summarizing new or updated issues, or creating action item recommendations. Triggers on requests involving triage preparation, Needs-Triage review, meeting summary, triage diff, or weekly issue analysis.","microsoft\u002FWindowsAppSDK","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BJ4CARWJZW1TMD4S01Y3X",4733,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"triage","triage meeting prep","meeting prep","prep","meeting","new","review","when","weekly","for","action","triggers","recommendations","issue","reports","diff","analysis","issues","prepare","winappsdk","triage issues","2026-11-10 10:12:30",false,"---\nname: triage-meeting-prep\ndescription: Prepare weekly triage meeting summary for WinAppSDK Needs-Triage issues. Use when preparing for triage meetings, reviewing Needs-Triage issues, generating diff reports since last triage, summarizing new or updated issues, or creating action item recommendations. Triggers on requests involving triage preparation, Needs-Triage review, meeting summary, triage diff, or weekly issue analysis.\nlicense: Complete terms in LICENSE.txt\n---\n\n# Triage Meeting Preparation\n\nThis skill helps prepare comprehensive summaries for the twice-weekly WinAppSDK triage meetings. It focuses on issues that **actually need triage attention**:\n\n1. **Needs-Triage WITHOUT area label** — These need area assignment (primary focus)\n2. **Closed issues still labeled Needs-Triage** — These need follow-up replies\n\n> **Note**: Open issues with both `Needs-Triage` AND an `area-*` label are **excluded** — they're already triaged and waiting for area team action.\n\n## Research-Backed Analysis\n\n**Every suggestion and reply is backed by research:**\n\n| Research Type | What We Search | Why |\n|---------------|----------------|-----|\n| ? **Similar Issues** | GitHub issue search | Find duplicates, related bugs, past fixes |\n| ? **Codebase** | `grep_search`, `semantic_search` | Understand technical context, find workarounds |\n| ? **Documentation** | `fetch_webpage` on MS docs | Verify known limitations, expected behavior |\n| ? **Git History** | `git log`, `git blame` | Identify area owners, recent changes |\n\nThis ensures:\n- Suggested replies are technically accurate\n- Workarounds are validated against the codebase\n- We reference related issues customers may have missed\n- Area assignments are informed by code structure\n\n## Key Outputs: What's Changed Since Last Triage\n\nThe skill tracks **four critical categories** for each meeting:\n\n| Category | Description | Action Required |\n|----------|-------------|-----------------|\n| ? **Popular Issues** | ≥5 reactions (community interest) | May need priority attention |\n| ? **Created This Week** | Issues created since last weekly triage | Review + assign area |\n| ⏳ **Older Pending** | Older issues still without area labels | Follow up — why no action? |\n| ✅ **Closed (need reply)** | Closed issues with customer follow-up | Draft reply with `[confidence:XX]` |\n\nAll suggestions include confidence scoring in `[confidence:XX]` format for easy filtering.\n\n## When to Use This Skill\n\n**Primary triggers** — Use this skill when:\n\n1. **Preparing for triage meetings** — Generate a summary of issues needing area assignment\n2. **Reviewing what's changed** — See the diff of issues since the last triage run\n3. **Drafting customer replies** — Get research-backed suggested replies for closed issues\n4. **Tracking pending items** — Identify issues that still haven't been actioned from previous meetings\n\n**Anti-patterns** — Do NOT use this skill when:\n- Reviewing a single specific issue (use `Get-IssueDetails.ps1` for individual issues)\n- General issue searching without triage context\n- Non-WinAppSDK repositories\n\n## Prerequisites\n\n- **GitHub CLI (gh)** installed and authenticated (`gh auth login`)\n- Access to microsoft\u002FWindowsAppSDK repository\n- Previous triage state file for diff comparison: `Generated-Files\u002FtriageMeeting\u002Fprevious-state.json`\n\n> **Migration note**: If you have an existing `Generated Files\u002FtriageMeeting\u002F...` directory from earlier runs, rename `Generated Files` to `Generated-Files` before using this skill, or pass explicit input\u002Foutput paths to the scripts so you keep prior diff history.\n\n### Installing GitHub CLI\n\n```powershell\n# Windows\nwinget install GitHub.cli\n\n# Then authenticate\ngh auth login\n```\n\n## Step-by-Step Workflow\n\n### Workflow: Generate Triage Meeting Summary\n\n1. **Load previous triage state** from `Generated-Files\u002FtriageMeeting\u002Fprevious-state.json`\n2. **Fetch current Needs-Triage issues** using the scripts:\n   ```powershell\n   # Get all issues needing triage (no area label)\n   .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-TriageIssues.ps1 -NoAreaOnly -OutputFormat summary\n   \n   # Or get JSON for processing\n   $issues = .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-TriageIssues.ps1 -NoAreaOnly | ConvertFrom-Json\n   ```\n3. **Categorize issues by creation date**:\n   - ? **Created This Week** — `createdAt` ≥ last weekly triage date\n   - ⏳ **Older Pending** — `createdAt` \u003C last weekly triage date\n4. **Fetch area label definitions** for classification:\n   ```powershell\n   .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-RepositoryLabels.ps1 -Filter \"area-*\" -OutputFormat json\n   ```\n5. **For each no-area issue**, analyze using `Get-IssueDetails.ps1`:\n   - Run: `.\u002FGet-IssueDetails.ps1 -IssueNumber \u003Cnumber> -OutputFormat summary`\n   - Review the issue body, comments, and labels\n   - **Classify the area label** by reasoning about the issue content against the area label definitions (see workflow for confidence rubric)\n5. **Generate summary report** with links to each issue's `overview.md`\n6. **Save current state** for next diff comparison\n\n> **Important**: Every issue without an area label gets a review. The summary links to each review file.\n\n## Available Scripts\n\nThe skill provides several PowerShell scripts for data fetching and analysis:\n\n### Get-TriageIssues.ps1\n\nFetches all issues with the `Needs-Triage` label from the repository.\n\n```powershell\n# Get all Needs-Triage issues without area labels\n.\u002FGet-TriageIssues.ps1 -NoAreaOnly -OutputFormat summary\n\n# Get JSON output for programmatic processing\n$issues = .\u002FGet-TriageIssues.ps1 -NoAreaOnly | ConvertFrom-Json\n```\n\n**Parameters:**\n- `-Repository` — Repository in 'owner\u002Frepo' format (default: microsoft\u002FWindowsAppSDK)\n- `-State` — Filter by state: 'open', 'closed', or 'all' (default: all)\n- `-NoAreaOnly` — Only include issues without area-* labels\n- `-Limit` — Maximum issues to fetch (default: 200)\n- `-OutputFormat` — Output format: 'json', 'summary', or 'table' (default: json)\n\n### Get-IssueDetails.ps1\n\nPerforms deep analysis of a single issue including scoring and recommendations.\n\n```powershell\n# Analyze a specific issue\n.\u002FGet-IssueDetails.ps1 -IssueNumber 1234 -OutputFormat summary\n```\n\n### Get-RepositoryLabels.ps1\n\nFetches all label definitions from the repository including names, descriptions, and colors.\n\n```powershell\n# Get all labels\n.\u002FGet-RepositoryLabels.ps1 -OutputFormat summary\n\n# Get only area labels\n.\u002FGet-RepositoryLabels.ps1 -Filter \"area-*\" -OutputFormat table\n\n# Get labels from a different repository\n.\u002FGet-RepositoryLabels.ps1 -Repository \"microsoft\u002Fterminal\" -OutputFormat json\n```\n\n**Parameters:**\n- `-Repository` — Repository in 'owner\u002Frepo' format (default: microsoft\u002FWindowsAppSDK)\n- `-Filter` — Filter pattern for label names (supports wildcards like 'area-*')\n- `-Limit` — Maximum labels to fetch (default: 500)\n- `-OutputFormat` — Output format: 'json', 'summary', or 'table' (default: json)\n\n**Use cases:**\n- Understanding available area labels for issue categorization\n- Verifying label descriptions for triage decisions\n- Comparing label definitions across repositories\n- Finding labels that lack descriptions\n\n### Compare-TriageState.ps1\n\nCompares current triage state with previous state to identify changes.\n\n### Save-TriageState.ps1\n\nSaves the current triage state for future comparisons.\n\n## Output Structure\n\nAll outputs are saved to `Generated-Files\u002FtriageMeeting\u002F\u003Cdate>\u002F`:\n\n| File | Purpose |\n|------|---------|\n| `summary.md` | Main meeting document with tables linking to individual reviews |\n| `previous-state.json` | State snapshot for next diff (auto-generated) |\n\nIndividual issue reviews are saved to `Generated-Files\u002FissueReview\u002F\u003Cissue-number>\u002F`:\n\n| File | Purpose |\n|------|---------|\n| `overview.md` | Full issue analysis with scores and suggested actions (linked from summary) |\n| `implementation-plan.md` | Technical implementation details (if applicable) |\n\n> **Key Output**: The `summary.md` includes the **Suggested Actions** section extracted from each issue's `overview.md`, with `[confidence:XX]` scores.\n\n## Detailed Workflow\n\nSee [workflow-triage-prep.md](.\u002Freferences\u002Fworkflow-triage-prep.md) for the complete step-by-step process.\n\n## Issue Categories\n\n| Category | Definition | Action Needed |\n|----------|------------|---------------|\n| ? **Popular Issues** | ≥5 reactions (community interest) | May need priority attention |\n| ? **Created This Week** | `createdAt` is after last weekly triage date | Use `Get-IssueDetails.ps1` + assign area |\n| ⏳ **Older Pending** | Created before this week, still no area label | Follow up — why not actioned? |\n| ✅ **Resolved** | In previous state, NOT in current | Acknowledge (got area label or closed) |\n| ?️ **Closed (cleanup)** | Closed + still has `Needs-Triage` label | Remove `Needs-Triage` label |\n\n> **Key distinction**: \"Created This Week\" is based on when the issue was **created** (`createdAt`), not when it was first seen in triage runs. This ensures new issues are highlighted even if triage runs multiple times per week.\n\n## Summary.md Format\n\nSee [template-summary.md](.\u002Ftemplates\u002Ftemplate-summary.md) for the full template structure.\n\n## Area Classification (LLM-Based)\n\nIssues without an `area-*` label are classified by the agent using LLM reasoning — **not** keyword matching. The agent:\n\n1. Fetches area label definitions via `Get-RepositoryLabels.ps1 -Filter \"area-*\"`\n2. Reads the issue title, body, and comments from `Get-IssueDetails.ps1`\n3. Reasons about the best area match and assigns a confidence score\n\n**Confidence scale:**\n\n| Score | Level | Meaning |\n|-------|-------|---------|\n| **80–100** | High | Issue explicitly names the component; maps to exactly one area |\n| **60–79** | Medium-High | Strong signals (stack traces, API names) point to one area |\n| **40–59** | Medium | Reasonable match, but 2+ areas are plausible |\n| **20–39** | Low | Weak signal; best guess |\n| **0–19** | Very Low | No clear signal; vague or multi-area |\n\nSee [workflow-triage-prep.md](.\u002Freferences\u002Fworkflow-triage-prep.md) for the full confidence rubric and adjusters.\n\n## Action Item Types\n\n| Action | When to Suggest |\n|--------|-----------------|\n| `Assign to milestone` | High business importance, clear scope |\n| `Add area label` | Missing component\u002Farea identification |\n| `Request clarification` | Requirement clarity \u003C 50 |\n| `Close as duplicate` | Similar closed issue found with fix |\n| `Close as by-design` | Expected behavior, not a bug |\n| `Needs investigation` | Repro unclear, needs debugging |\n| `Ready for work` | Clear requirements, assignable |\n\n## Troubleshooting\n\n| Symptom | Solution |\n|---------|----------|\n| No previous state file | First run — all issues shown as \"New\" |\n| `gh` CLI not installed | Run `winget install GitHub.cli` then `gh auth login` |\n| `gh` not authenticated | Run `gh auth login` and follow the prompts |\n| Rate limited | Wait and retry, or reduce `--limit` parameter |\n| Missing issue details | Use `Get-IssueDetails.ps1 -IssueNumber \u003Cnumber>` |\n\n## Related Resources\n\n- [GitHub CLI documentation](https:\u002F\u002Fcli.github.com\u002Fmanual\u002F) — `gh` CLI reference\n- [Scripts directory](.\u002Fscripts\u002F) — PowerShell scripts for data fetching\n","# Triage Meeting Preparation\n\nThis skill helps prepare comprehensive summaries for the twice-weekly WinAppSDK triage meetings. It focuses on issues that **actually need triage attention**:\n\n1. **Needs-Triage WITHOUT area label** — These need area assignment (primary focus)\n2. **Closed issues still labeled Needs-Triage** — These need follow-up replies\n\n> **Note**: Open issues with both `Needs-Triage` AND an `area-*` label are **excluded** — they're already triaged and waiting for area team action.\n\n## Research-Backed Analysis\n\n**Every suggestion and reply is backed by research:**\n\n| Research Type | What We Search | Why |\n|---------------|----------------|-----|\n| ? **Similar Issues** | GitHub issue search | Find duplicates, related bugs, past fixes |\n| ? **Codebase** | `grep_search`, `semantic_search` | Understand technical context, find workarounds |\n| ? **Documentation** | `fetch_webpage` on MS docs | Verify known limitations, expected behavior |\n| ? **Git History** | `git log`, `git blame` | Identify area owners, recent changes |\n\nThis ensures:\n- Suggested replies are technically accurate\n- Workarounds are validated against the codebase\n- We reference related issues customers may have missed\n- Area assignments are informed by code structure\n\n## Key Outputs: What's Changed Since Last Triage\n\nThe skill tracks **four critical categories** for each meeting:\n\n| Category | Description | Action Required |\n|----------|-------------|-----------------|\n| ? **Popular Issues** | ≥5 reactions (community interest) | May need priority attention |\n| ? **Created This Week** | Issues created since last weekly triage | Review + assign area |\n| ⏳ **Older Pending** | Older issues still without area labels | Follow up — why no action? |\n| ✅ **Closed (need reply)** | Closed issues with customer follow-up | Draft reply with `[confidence:XX]` |\n\nAll suggestions include confidence scoring in `[confidence:XX]` format for easy filtering.\n\n## When to Use This Skill\n\n**Primary triggers** — Use this skill when:\n\n1. **Preparing for triage meetings** — Generate a summary of issues needing area assignment\n2. **Reviewing what's changed** — See the diff of issues since the last triage run\n3. **Drafting customer replies** — Get research-backed suggested replies for closed issues\n4. **Tracking pending items** — Identify issues that still haven't been actioned from previous meetings\n\n**Anti-patterns** — Do NOT use this skill when:\n- Reviewing a single specific issue (use `Get-IssueDetails.ps1` for individual issues)\n- General issue searching without triage context\n- Non-WinAppSDK repositories\n\n## Prerequisites\n\n- **GitHub CLI (gh)** installed and authenticated (`gh auth login`)\n- Access to microsoft\u002FWindowsAppSDK repository\n- Previous triage state file for diff comparison: `Generated-Files\u002FtriageMeeting\u002Fprevious-state.json`\n\n> **Migration note**: If you have an existing `Generated Files\u002FtriageMeeting\u002F...` directory from earlier runs, rename `Generated Files` to `Generated-Files` before using this skill, or pass explicit input\u002Foutput paths to the scripts so you keep prior diff history.\n\n### Installing GitHub CLI\n\n```powershell\n# Windows\nwinget install GitHub.cli\n\n# Then authenticate\ngh auth login\n```\n\n## Step-by-Step Workflow\n\n### Workflow: Generate Triage Meeting Summary\n\n1. **Load previous triage state** from `Generated-Files\u002FtriageMeeting\u002Fprevious-state.json`\n2. **Fetch current Needs-Triage issues** using the scripts:\n   ```powershell\n   # Get all issues needing triage (no area label)\n   .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-TriageIssues.ps1 -NoAreaOnly -OutputFormat summary\n   \n   # Or get JSON for processing\n   $issues = .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-TriageIssues.ps1 -NoAreaOnly | ConvertFrom-Json\n   ```\n3. **Categorize issues by creation date**:\n   - ? **Created This Week** — `createdAt` ≥ last weekly triage date\n   - ⏳ **Older Pending** — `createdAt` \u003C last weekly triage date\n4. **Fetch area label definitions** for classification:\n   ```powershell\n   .\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-RepositoryLabels.ps1 -Filter \"area-*\" -OutputFormat json\n   ```\n5. **For each no-area issue**, analyze using `Get-IssueDetails.ps1`:\n   - Run: `.\u002FGet-IssueDetails.ps1 -IssueNumber \u003Cnumber> -OutputFormat summary`\n   - Review the issue body, comments, and labels\n   - **Classify the area label** by reasoning about the issue content against the area label definitions (see workflow for confidence rubric)\n5. **Generate summary report** with links to each issue's `overview.md`\n6. **Save current state** for next diff comparison\n\n> **Important**: Every issue without an area label gets a review. The summary links to each review file.\n\n## Available Scripts\n\nThe skill provides several PowerShell scripts for data fetching and analysis:\n\n### Get-TriageIssues.ps1\n\nFetches all issues with the `Needs-Triage` label from the repository.\n\n```powershell\n# Get all Needs-Triage issues without area labels\n.\u002FGet-TriageIssues.ps1 -NoAreaOnly -OutputFormat summary\n\n# Get JSON output for programmatic processing\n$issues = .\u002FGet-TriageIssues.ps1 -NoAreaOnly | ConvertFrom-Json\n```\n\n**Parameters:**\n- `-Repository` — Repository in 'owner\u002Frepo' format (default: microsoft\u002FWindowsAppSDK)\n- `-State` — Filter by state: 'open', 'closed', or 'all' (default: all)\n- `-NoAreaOnly` — Only include issues without area-* labels\n- `-Limit` — Maximum issues to fetch (default: 200)\n- `-OutputFormat` — Output format: 'json', 'summary', or 'table' (default: json)\n\n### Get-IssueDetails.ps1\n\nPerforms deep analysis of a single issue including scoring and recommendations.\n\n```powershell\n# Analyze a specific issue\n.\u002FGet-IssueDetails.ps1 -IssueNumber 1234 -OutputFormat summary\n```\n\n### Get-RepositoryLabels.ps1\n\nFetches all label definitions from the repository including names, descriptions, and colors.\n\n```powershell\n# Get all labels\n.\u002FGet-RepositoryLabels.ps1 -OutputFormat summary\n\n# Get only area labels\n.\u002FGet-RepositoryLabels.ps1 -Filter \"area-*\" -OutputFormat table\n\n# Get labels from a different repository\n.\u002FGet-RepositoryLabels.ps1 -Repository \"microsoft\u002Fterminal\" -OutputFormat json\n```\n\n**Parameters:**\n- `-Repository` — Repository in 'owner\u002Frepo' format (default: microsoft\u002FWindowsAppSDK)\n- `-Filter` — Filter pattern for label names (supports wildcards like 'area-*')\n- `-Limit` — Maximum labels to fetch (default: 500)\n- `-OutputFormat` — Output format: 'json', 'summary', or 'table' (default: json)\n\n**Use cases:**\n- Understanding available area labels for issue categorization\n- Verifying label descriptions for triage decisions\n- Comparing label definitions across repositories\n- Finding labels that lack descriptions\n\n### Compare-TriageState.ps1\n\nCompares current triage state with previous state to identify changes.\n\n### Save-TriageState.ps1\n\nSaves the current triage state for future comparisons.\n\n## Output Structure\n\nAll outputs are saved to `Generated-Files\u002FtriageMeeting\u002F\u003Cdate>\u002F`:\n\n| File | Purpose |\n|------|---------|\n| `summary.md` | Main meeting document with tables linking to individual reviews |\n| `previous-state.json` | State snapshot for next diff (auto-generated) |\n\nIndividual issue reviews are saved to `Generated-Files\u002FissueReview\u002F\u003Cissue-number>\u002F`:\n\n| File | Purpose |\n|------|---------|\n| `overview.md` | Full issue analysis with scores and suggested actions (linked from summary) |\n| `implementation-plan.md` | Technical implementation details (if applicable) |\n\n> **Key Output**: The `summary.md` includes the **Suggested Actions** section extracted from each issue's `overview.md`, with `[confidence:XX]` scores.\n\n## Detailed Workflow\n\nSee [workflow-triage-prep.md](.\u002Freferences\u002Fworkflow-triage-prep.md) for the complete step-by-step process.\n\n## Issue Categories\n\n| Category | Definition | Action Needed |\n|----------|------------|---------------|\n| ? **Popular Issues** | ≥5 reactions (community interest) | May need priority attention |\n| ? **Created This Week** | `createdAt` is after last weekly triage date | Use `Get-IssueDetails.ps1` + assign area |\n| ⏳ **Older Pending** | Created before this week, still no area label | Follow up — why not actioned? |\n| ✅ **Resolved** | In previous state, NOT in current | Acknowledge (got area label or closed) |\n| ?️ **Closed (cleanup)** | Closed + still has `Needs-Triage` label | Remove `Needs-Triage` label |\n\n> **Key distinction**: \"Created This Week\" is based on when the issue was **created** (`createdAt`), not when it was first seen in triage runs. This ensures new issues are highlighted even if triage runs multiple times per week.\n\n## Summary.md Format\n\nSee [template-summary.md](.\u002Ftemplates\u002Ftemplate-summary.md) for the full template structure.\n\n## Area Classification (LLM-Based)\n\nIssues without an `area-*` label are classified by the agent using LLM reasoning — **not** keyword matching. The agent:\n\n1. Fetches area label definitions via `Get-RepositoryLabels.ps1 -Filter \"area-*\"`\n2. Reads the issue title, body, and comments from `Get-IssueDetails.ps1`\n3. Reasons about the best area match and assigns a confidence score\n\n**Confidence scale:**\n\n| Score | Level | Meaning |\n|-------|-------|---------|\n| **80–100** | High | Issue explicitly names the component; maps to exactly one area |\n| **60–79** | Medium-High | Strong signals (stack traces, API names) point to one area |\n| **40–59** | Medium | Reasonable match, but 2+ areas are plausible |\n| **20–39** | Low | Weak signal; best guess |\n| **0–19** | Very Low | No clear signal; vague or multi-area |\n\nSee [workflow-triage-prep.md](.\u002Freferences\u002Fworkflow-triage-prep.md) for the full confidence rubric and adjusters.\n\n## Action Item Types\n\n| Action | When to Suggest |\n|--------|-----------------|\n| `Assign to milestone` | High business importance, clear scope |\n| `Add area label` | Missing component\u002Farea identification |\n| `Request clarification` | Requirement clarity \u003C 50 |\n| `Close as duplicate` | Similar closed issue found with fix |\n| `Close as by-design` | Expected behavior, not a bug |\n| `Needs investigation` | Repro unclear, needs debugging |\n| `Ready for work` | Clear requirements, assignable |\n\n## Troubleshooting\n\n| Symptom | Solution |\n|---------|----------|\n| No previous state file | First run — all issues shown as \"New\" |\n| `gh` CLI not installed | Run `winget install GitHub.cli` then `gh auth login` |\n| `gh` not authenticated | Run `gh auth login` and follow the prompts |\n| Rate limited | Wait and retry, or reduce `--limit` parameter |\n| Missing issue details | Use `Get-IssueDetails.ps1 -IssueNumber \u003Cnumber>` |\n\n## Related Resources\n\n- [GitHub CLI documentation](https:\u002F\u002Fcli.github.com\u002Fmanual\u002F) — `gh` CLI reference\n- [Scripts directory](.\u002Fscripts\u002F) — PowerShell scripts for data fetching\n",{"name":5,"license":51,"description":7},"Complete terms in LICENSE.txt","main","32dbd99499d1554d5d4ed5d512311d1339833740",".github\u002Fskills\u002Ftriage-meeting-prep",482,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK","https:\u002F\u002Fdocs.microsoft.com\u002Fwindows\u002Fapps\u002Fwindows-app-sdk\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 11:17:33",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add microsoft\u002FWindowsAppSDK --skill triage-meeting-prep",{"tool":68,"command":69},"bunx","bunx skills add microsoft\u002FWindowsAppSDK --skill triage-meeting-prep",{"tool":71,"command":72},"pnpm","pnpm dlx skills add microsoft\u002FWindowsAppSDK --skill triage-meeting-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002FSKILL.md",true,[76,81,87,91,97,101,105,109,113],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",11355,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FEXAMPLES.md","REFERENCE","参考文档",2059,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Farize-link\u002Freferences\u002FEXAMPLES.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflow-triage-prep.md",20221,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Freferences\u002Fworkflow-triage-prep.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002FCompare-TriageState.ps1","SCRIPT","脚本",8867,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FCompare-TriageState.ps1",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002FGet-IssueDetails.ps1",7598,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-IssueDetails.ps1",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002FGet-RepositoryLabels.ps1",9522,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-RepositoryLabels.ps1",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002FGet-TriageIssues.ps1",7744,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FGet-TriageIssues.ps1",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002FSave-TriageState.ps1",4323,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Fscripts\u002FSave-TriageState.ps1",{"path":114,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":115,"sourceHtmlUrl":116},"templates\u002Ftemplate-summary.md",7734,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage-meeting-prep\u002Ftemplates\u002Ftemplate-summary.md",[118,149],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":131,"publishedAt":46},"01M69BJ6MXVHZV66DQ85XWZC96","issue-triage-report","Generate comprehensive GitHub Feature Area Status reports for the Windows App SDK repository. Use when asked to create triage reports, identify high-priority issues, analyze feature area health, find issues needing attention, or generate status dashboards. Triggers on requests involving issue triage, area status, priority analysis, bug tracking reports, or engineering team focus areas.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fissue-triage-report\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fissue-triage-report\u002FSKILL.md",[125,130],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[25,132,133,134,135,38,32,136,137,138,139,140,141,42,142,41,143,144,39,145,146,147,148],"report","issue triage report","issue triage","triage report","analyze","sdk","status","windows","create","generate","repository","team","bug","focus","app","bug tracking","github",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":153,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":46},"01M69BJEX3CEP8RFFZWAXSE2QD","worktree-manager","Create and manage Git worktrees for parallel development workflows. Use when multiple self-contained issues should NOT be fixed in a single branch, when human-Copilot iteration requires isolated environments with separate chat history and commits, or when parallel work items need independent build\u002Ftest results. Triggers on requests involving branch isolation, work item separation, parallel development, or avoiding messy branch switching.","MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWindowsAppSDK\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworktree-manager\u002FSKILL.md",[],[157,158,159,160,161,140,162,42,163,164,165,166,167,168,169,170,171,172,32,173,174,175],"manager","worktree manager","worktree","self","development","git","work","branch","git worktrees","worktrees","human","development workflows","iteration","switching","separation","environments","copilot","test","workflows"]