[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699XBQXCXJQKFDP06VN13FP":3,"skill-same:01M699XBQXCXJQKFDP06VN13FP":60},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M699XBQXCXJQKFDP06VN13FP","manage-bans",null,"Create and manage banned AST patterns that prevent code constructs in edits. USE FOR: \"ban a code pattern\", \"add a tree-sitter lint rule\", \"prevent specific syntax in edits\", \"validate a BANNED_AST.md rule\". DO NOT USE FOR: \"explain how existing code works\", \"answer general programming questions\".","microsoft\u002Fvscode-team-kit","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699X9KV4SS0Q63FKWDHSQ6Z",67,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fban-ast\u002Fskills\u002Fmanage-bans\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25],"manage bans","validate","2026-11-10 10:12:30",false,"---\nname: manage-bans\ndescription: 'Create and manage banned AST patterns that prevent code constructs in edits. USE FOR: \"ban a code pattern\", \"add a tree-sitter lint rule\", \"prevent specific syntax in edits\", \"validate a BANNED_AST.md rule\". DO NOT USE FOR: \"explain how existing code works\", \"answer general programming questions\".'\n---\n\n# Managing Banned AST Patterns\n\nBan rules are discovered from two sources, both checked by the preToolUse hook:\n\n1. **`$HOME\u002F.BANNED_AST.md`** — global rules that apply to all edits, regardless of project.\n2. **`BANNED_AST.md` files in any parent directory of the edited file** — can contain multiple rules, scoped to that subtree.\n\n## Source 1: Global Ban File (`$HOME\u002F.BANNED_AST.md`)\n\nPlace a `BANNED_AST.md` in your home directory to define rules that apply globally to every edit. It uses the same multi-rule format as directory-scoped files:\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk and should be replaced with safer alternatives.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n```\n\n### Creating a Global Ban\n\n1. Open or create `~\u002F.BANNED_AST.md`.\n2. Add a rule block with `---` frontmatter containing `name` and `message`, followed by `---` and the Tree Sitter query.\n3. Multiple rules can be stacked in the same file, each separated by a new frontmatter block.\n4. Validate the rule — see [Validating Rules](#validating-rules) below.\n\n## Source 2: `BANNED_AST.md` Files (Directory-Scoped)\n\nPlace a `BANNED_AST.md` file in any directory to ban patterns for all files at or below that directory. The hook walks up from each edited file's directory to the filesystem root, collecting rules from every `BANNED_AST.md` it finds.\n\nA single `BANNED_AST.md` can contain **multiple rules**, each separated by its own frontmatter block:\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n\n---\nname: no-console-log\nmessage: \"Avoid console.log() in production code.\"\n---\n\n(call_expression\n  function: (member_expression\n    object: (identifier) @obj\n    property: (property_identifier) @prop)\n  (#eq? @obj \"console\")\n  (#eq? @prop \"log\"))\n```\n\nEach rule section starts with `---` frontmatter containing `name` and `message`, followed by `---`, then the Tree Sitter query body. The next `---` begins the next rule.\n\n### When to Use Which\n\n- **`~\u002F.BANNED_AST.md`** — personal global bans that apply everywhere regardless of file location.\n- **`BANNED_AST.md`** — scoped bans for subtrees (e.g. ban `any` in `src\u002F` but allow it in `tests\u002F`).\n\nWhen both sources define a rule with the same `name`, the `BANNED_AST.md` closer to the edited file takes precedence.\n\n## Rule Format\n\n### Frontmatter Fields\n\n- **name** (required): A unique identifier for this ban (lowercase, hyphens ok). This is used in justification comments (`\u003Cname> justification: ...`).\n- **message** (required): The rejection message shown when this pattern is detected. Should explain WHY the pattern is banned and suggest alternatives.\n\n### Body\n\nThe body contains a [Tree Sitter query](https:\u002F\u002Ftree-sitter.github.io\u002Ftree-sitter\u002Fusing-parsers\u002Fqueries) that matches the banned AST nodes. These use S-expression syntax with optional predicates like `#eq?` and `#match?`.\n\n## Examples\n\n### Global ban file (`~\u002F.BANNED_AST.md`)\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk. Use Function constructor or a sandboxed interpreter instead.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n```\n\n### Multi-rule `BANNED_AST.md`\n\nPlace this in a project directory to ban multiple patterns for all files below it:\n\n```markdown\n---\nname: no-console-log\nmessage: \"Avoid console.log() in production code. Use a structured logging framework instead.\"\n---\n\n(call_expression\n  function: (member_expression\n    object: (identifier) @obj\n    property: (property_identifier) @prop)\n  (#eq? @obj \"console\")\n  (#eq? @prop \"log\"))\n\n---\nname: no-any-type\nmessage: \"Do not use the 'any' type. Use 'unknown' or a concrete type instead.\"\n---\n\n(predefined_type) @type\n(#eq? @type \"any\")\n```\n\n## Validating Rules\n\nAfter writing a rule, always validate it using the `validate-rule.mts` script before finishing. This catches query syntax errors and confirms the rule matches the intended patterns — and only those patterns.\n\n```bash\nnode ban-ast\u002Fscripts\u002Fvalidate-rule.mts \\\n  --lang ts \\\n  --query '\u003Cyour-tree-sitter-query>' \\\n  --should-match '\u003Ccode that should be flagged>' \\\n  --should-not-match '\u003Ccode that should be allowed>'\n```\n\n- `--lang` — file extension for the language (default: `ts`). Supported: `ts`, `js`, `tsx`, `py`, `rs`, `go`, `c`, `cpp`, `cs`, `java`, `rb`, and more.\n- `--query` — the Tree Sitter S-expression query from the rule body.\n- `--should-match` — a code snippet that **must** trigger the rule. Repeat for multiple cases.\n- `--should-not-match` — a code snippet that **must not** trigger the rule. Repeat for multiple cases.\n\nIf no `--should-match` \u002F `--should-not-match` flags are given, the script only checks that the query is syntactically valid.\n\nThe script exits with code `1` if any test fails, so you can see immediately when a rule needs to be revised.\n\n### Example\n\n```bash\nnode ban-ast\u002Fscripts\u002Fvalidate-rule.mts \\\n  --lang ts \\\n  --query '(call_expression function: (identifier) @fn (#eq? @fn \"eval\"))' \\\n  --should-match 'eval(\"code\")' \\\n  --should-not-match 'foo(\"code\")'\n```\n\nExpected output:\n\n```\nPASS [should-match]:     \"eval(\\\"code\\\")\"\nPASS [should-not-match]: \"foo(\\\"code\\\")\"\n\n2 test(s): 2 passed, 0 failed.\n```\n\n## Justification Override\n\nIf a banned pattern is strictly necessary, include a justification comment in the code to bypass the ban for that specific instance:\n\n```typescript\n\u002F\u002F \u003Cno-eval> justification: required for dynamic plugin loading\nconst result = eval(expression);\n```\n\nThe hook checks for `\u003Crule-name> justification: \u003Cnon-empty reason>` anywhere in the new code. If found, that rule is not enforced for that edit. The reason must be non-empty to ensure overrides are intentional and documented.\n","# Managing Banned AST Patterns\n\nBan rules are discovered from two sources, both checked by the preToolUse hook:\n\n1. **`$HOME\u002F.BANNED_AST.md`** — global rules that apply to all edits, regardless of project.\n2. **`BANNED_AST.md` files in any parent directory of the edited file** — can contain multiple rules, scoped to that subtree.\n\n## Source 1: Global Ban File (`$HOME\u002F.BANNED_AST.md`)\n\nPlace a `BANNED_AST.md` in your home directory to define rules that apply globally to every edit. It uses the same multi-rule format as directory-scoped files:\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk and should be replaced with safer alternatives.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n```\n\n### Creating a Global Ban\n\n1. Open or create `~\u002F.BANNED_AST.md`.\n2. Add a rule block with `---` frontmatter containing `name` and `message`, followed by `---` and the Tree Sitter query.\n3. Multiple rules can be stacked in the same file, each separated by a new frontmatter block.\n4. Validate the rule — see [Validating Rules](#validating-rules) below.\n\n## Source 2: `BANNED_AST.md` Files (Directory-Scoped)\n\nPlace a `BANNED_AST.md` file in any directory to ban patterns for all files at or below that directory. The hook walks up from each edited file's directory to the filesystem root, collecting rules from every `BANNED_AST.md` it finds.\n\nA single `BANNED_AST.md` can contain **multiple rules**, each separated by its own frontmatter block:\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n\n---\nname: no-console-log\nmessage: \"Avoid console.log() in production code.\"\n---\n\n(call_expression\n  function: (member_expression\n    object: (identifier) @obj\n    property: (property_identifier) @prop)\n  (#eq? @obj \"console\")\n  (#eq? @prop \"log\"))\n```\n\nEach rule section starts with `---` frontmatter containing `name` and `message`, followed by `---`, then the Tree Sitter query body. The next `---` begins the next rule.\n\n### When to Use Which\n\n- **`~\u002F.BANNED_AST.md`** — personal global bans that apply everywhere regardless of file location.\n- **`BANNED_AST.md`** — scoped bans for subtrees (e.g. ban `any` in `src\u002F` but allow it in `tests\u002F`).\n\nWhen both sources define a rule with the same `name`, the `BANNED_AST.md` closer to the edited file takes precedence.\n\n## Rule Format\n\n### Frontmatter Fields\n\n- **name** (required): A unique identifier for this ban (lowercase, hyphens ok). This is used in justification comments (`\u003Cname> justification: ...`).\n- **message** (required): The rejection message shown when this pattern is detected. Should explain WHY the pattern is banned and suggest alternatives.\n\n### Body\n\nThe body contains a [Tree Sitter query](https:\u002F\u002Ftree-sitter.github.io\u002Ftree-sitter\u002Fusing-parsers\u002Fqueries) that matches the banned AST nodes. These use S-expression syntax with optional predicates like `#eq?` and `#match?`.\n\n## Examples\n\n### Global ban file (`~\u002F.BANNED_AST.md`)\n\n```markdown\n---\nname: no-eval\nmessage: \"Do not use eval(). It poses a security risk. Use Function constructor or a sandboxed interpreter instead.\"\n---\n\n(call_expression\n  function: (identifier) @fn\n  (#eq? @fn \"eval\"))\n```\n\n### Multi-rule `BANNED_AST.md`\n\nPlace this in a project directory to ban multiple patterns for all files below it:\n\n```markdown\n---\nname: no-console-log\nmessage: \"Avoid console.log() in production code. Use a structured logging framework instead.\"\n---\n\n(call_expression\n  function: (member_expression\n    object: (identifier) @obj\n    property: (property_identifier) @prop)\n  (#eq? @obj \"console\")\n  (#eq? @prop \"log\"))\n\n---\nname: no-any-type\nmessage: \"Do not use the 'any' type. Use 'unknown' or a concrete type instead.\"\n---\n\n(predefined_type) @type\n(#eq? @type \"any\")\n```\n\n## Validating Rules\n\nAfter writing a rule, always validate it using the `validate-rule.mts` script before finishing. This catches query syntax errors and confirms the rule matches the intended patterns — and only those patterns.\n\n```bash\nnode ban-ast\u002Fscripts\u002Fvalidate-rule.mts \\\n  --lang ts \\\n  --query '\u003Cyour-tree-sitter-query>' \\\n  --should-match '\u003Ccode that should be flagged>' \\\n  --should-not-match '\u003Ccode that should be allowed>'\n```\n\n- `--lang` — file extension for the language (default: `ts`). Supported: `ts`, `js`, `tsx`, `py`, `rs`, `go`, `c`, `cpp`, `cs`, `java`, `rb`, and more.\n- `--query` — the Tree Sitter S-expression query from the rule body.\n- `--should-match` — a code snippet that **must** trigger the rule. Repeat for multiple cases.\n- `--should-not-match` — a code snippet that **must not** trigger the rule. Repeat for multiple cases.\n\nIf no `--should-match` \u002F `--should-not-match` flags are given, the script only checks that the query is syntactically valid.\n\nThe script exits with code `1` if any test fails, so you can see immediately when a rule needs to be revised.\n\n### Example\n\n```bash\nnode ban-ast\u002Fscripts\u002Fvalidate-rule.mts \\\n  --lang ts \\\n  --query '(call_expression function: (identifier) @fn (#eq? @fn \"eval\"))' \\\n  --should-match 'eval(\"code\")' \\\n  --should-not-match 'foo(\"code\")'\n```\n\nExpected output:\n\n```\nPASS [should-match]:     \"eval(\\\"code\\\")\"\nPASS [should-not-match]: \"foo(\\\"code\\\")\"\n\n2 test(s): 2 passed, 0 failed.\n```\n\n## Justification Override\n\nIf a banned pattern is strictly necessary, include a justification comment in the code to bypass the ban for that specific instance:\n\n```typescript\n\u002F\u002F \u003Cno-eval> justification: required for dynamic plugin loading\nconst result = eval(expression);\n```\n\nThe hook checks for `\u003Crule-name> justification: \u003Cnon-empty reason>` anywhere in the new code. If found, that rule is not enforced for that edit. The reason must be non-empty to ensure overrides are intentional and documented.\n",{"name":5,"description":7},"main","5bb403cf26437f24d00f1847f9164576713a93ab","ban-ast\u002Fskills\u002Fmanage-bans",12,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 10:38:12",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add microsoft\u002Fvscode-team-kit --skill manage-bans",{"tool":46,"command":47},"bunx","bunx skills add microsoft\u002Fvscode-team-kit --skill manage-bans",{"tool":49,"command":50},"pnpm","pnpm dlx skills add microsoft\u002Fvscode-team-kit --skill manage-bans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fban-ast\u002Fskills\u002Fmanage-bans\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"evals\u002Feval.yaml","REFERENCE","参考文档",7049,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fban-ast\u002Fskills\u002Fmanage-bans\u002Fevals\u002Feval.yaml",[61,79,101,113,129,140],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":75,"publishedAt":26},"01M699YSSBWV52XX5646GGWH02","generate-test-video","Make a short narrated \"how to test\" or \"how to verify\" video for a VS Code test plan item (TPI), a fixed bug, or a few fixed bugs of one area: recorded in real VS Code Insiders in a throwaway profile, every step checked in the app, with captions, a zoom, flags that pause where something is wrong, a verdict slide and a recap. macOS. USE FOR: \"make a how-to-test video for TPI 342400\", \"a video to verify issue 341013\", \"how-to-verify video for bugs 339711 339712 339714\". DO NOT USE FOR: explaining a PR to someone who won't test it (use pr-studio:generate-video), plain screen recordings, editing an existing video.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Ftest-videos\u002Fskills\u002Fgenerate-test-video\u002FSKILL.md",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000016","图像与多媒体",[76,77,78],"test","generate test video","macos",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":26},"01M699YRFQ79KY3QVQ1DWJ4CX4","session-timeline","Open a live timeline canvas for the current Copilot session. Use when asked to inspect session events, system prompts, reasoning, tool executions, or subagent activity in a session timeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fsession-timeline\u002Fskills\u002Fsession-timeline\u002FSKILL.md",[],[86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"timeline","session timeline","session","prompts","live","use","canvas","events","tool","system","activity","subagent","open","reasoning","copilot",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":110,"publishedAt":26},"01M699YQ8Y2X7DB2H7FNX8FDVP","review-plan","Review an implementation plan produced by the Plan agent. It is CRITICAL to review plans before handing off to implementation — plans often have gaps, incorrect assumptions, or suboptimal sequencing that are cheaper to catch now than after coding. Use when the user asks to 'review the plan', 'check my plan', 'is this plan ready', or after the Plan agent produces a plan.md.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Freview-plan\u002Fskills\u002Freview-plan\u002FSKILL.md",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[111,112],"review plan","review",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":26},"01M699YNCNK188DHTHQ11J8WQ5","review-areas","In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development. USE FOR: \"in-depth review of a pull request\", \"code quality check or bug hunt\", \"review correctness, tests, security, performance and product areas\", \"review after any non-trivial development phase\". DO NOT USE FOR: \"plan a new implementation\", \"explain how existing code works\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Freview-areas\u002Fskills\u002Freview-areas\u002FSKILL.md",[119,122],{"categoryNo":120,"categoryName":121,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":108,"categoryName":109,"taxonomyType":70,"taxonomyTypeDesc":71},[112,124,125,126,127,128],"review areas","code quality","performance","security","code review",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":26},"01M699YK1BS97EEHD4B2817JJ4","generate-video","Make the shortest narrated video that fully explains a GitHub pull request (at most 90 seconds, captions, diagrams chosen for the PR, and real footage of the app, before and after side by side, when the change is visible) in one white Microsoft look. USE FOR: \"\u002Fgenerate-video 12345\", \"make a video of this PR\", \"explain PR \u003Curl> in a video\", \"a video for my manager about this PR\". DO NOT USE FOR: a screen recording on its own (no PR to explain), editing existing videos, slide decks (use generate-presentation).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fpr-studio\u002Fskills\u002Fgenerate-video\u002FSKILL.md",[135],{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[137,138,9,139],"generate video","change","github",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":26},"01M699YHC6Q7AEZCPGRJ7Y7AZC","generate-presentation","Make the shortest slide deck (a 16:9 PDF with speaker notes, at most 12 slides) that fully explains a GitHub pull request, in one white Microsoft look: one idea per slide, drawn as diagrams, with screenshots of the real app when the change is visible, every fact from the PR. USE FOR: \"\u002Fgenerate-presentation 12345\", \"make slides about this PR\", \"a deck for my manager on PR \u003Curl>\", \"present this pull request\". DO NOT USE FOR: editing PowerPoint files, videos (use generate-video), decks with no pull request behind them.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-team-kit\u002Fblob\u002Fmain\u002Fpr-studio\u002Fskills\u002Fgenerate-presentation\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":150,"categoryName":151,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000003","演示文稿",[153,154,138,9,139,155],"generate presentation","PDF","screenshots"]