[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B7KKBZE845SFNJQ5H992V":3,"skill-same:01M69B7KKBZE845SFNJQ5H992V":78},{"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":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M69B7KKBZE845SFNJQ5H992V","test-unbranded-emitter",null,"Build and test the @typespec\u002Fhttp-client-python emitter. Use this skill whenever the user wants to test their local changes to the emitter, run the generator test suite, check if their http-client-python changes are passing, or validate a fix. Triggers on phrases like \"test the emitter\", \"run tests\", \"check if my changes pass\", \"run test:generator\", \"run CI\", or any mention of testing\u002Fvalidating changes in the emitter package.","microsoft\u002Ftypespec","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B6S8HEDME7WWCNE7RGPJF",5948,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Ftest-unbranded-emitter\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"test","test unbranded emitter","ci","changes","generator","triggers","tests","local","build","test suite","use","fix","check","testing","package","run","typespec","http","run tests","validate","build and test","python","2026-11-10 10:12:30",false,"---\nname: test-unbranded-emitter\ndescription: >\n  Build and test the @typespec\u002Fhttp-client-python emitter. Use this skill whenever\n  the user wants to test their local changes to the emitter, run the generator\n  test suite, check if their http-client-python changes are passing, or validate\n  a fix. Triggers on phrases like \"test the emitter\", \"run tests\", \"check if my\n  changes pass\", \"run test:generator\", \"run CI\", or any mention of testing\u002Fvalidating\n  changes in the emitter package.\n---\n\n# Test Emitter Skill\n\nBuilds and tests `@typespec\u002Fhttp-client-python` to validate local changes.\nAutomatically regenerates if the generated code is stale.\n\n## Paths\n\nAll paths are relative to the http-client-python package root:\n`~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python`\n\n| Item                  | Path                                                    |\n| --------------------- | ------------------------------------------------------- |\n| Package root          | `~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python` |\n| Emitter source        | `emitter\u002Fsrc`                                           |\n| Generated (unbranded) | `generator\u002Ftest\u002Funbranded\u002Fgenerated`                    |\n| Generated (azure)     | `generator\u002Ftest\u002Fazure\u002Fgenerated`                        |\n| Regenerate marker     | `.last-regenerate`                                      |\n\n## Workflow\n\n### Step 1: Build the emitter\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\nnpm run build\n```\n\nCheck for TypeScript compilation errors. If the build fails, report the errors\nto the user and stop — do not proceed to testing.\n\n### Step 2: Check if regeneration is needed\n\nRegeneration is needed if ANY of these conditions are true:\n\n1. **Generated folder doesn't exist or is empty**:\n\n   ```bash\n   cd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\n   \n   if [ ! -d \"generator\u002Ftest\u002Funbranded\u002Fgenerated\" ] \\\n     || [ -z \"$(ls -A generator\u002Ftest\u002Funbranded\u002Fgenerated 2> \u002Fdev\u002Fnull)\" ]; then\n     echo \"Unbranded generated folder is empty - regeneration needed\"\n   fi\n   \n   if [ ! -d \"generator\u002Ftest\u002Fazure\u002Fgenerated\" ] \\\n     || [ -z \"$(ls -A generator\u002Ftest\u002Fazure\u002Fgenerated 2> \u002Fdev\u002Fnull)\" ]; then\n     echo \"Azure generated folder is empty - regeneration needed\"\n   fi\n   ```\n\n2. **No regenerate marker file exists**:\n\n   ```bash\n   if [ ! -f \".last-regenerate\" ]; then\n     echo \"No regenerate marker - regeneration needed\"\n   fi\n   ```\n\n3. **Emitter source files are newer than the marker**:\n   ```bash\n   if [ -n \"$(find emitter\u002Fsrc -newer .last-regenerate -type f 2> \u002Fdev\u002Fnull | head -1)\" ]; then\n     echo \"Emitter source changed since last regenerate - regeneration needed\"\n   fi\n   ```\n\n### Step 3: Regenerate if needed\n\nIf any condition from Step 2 is true:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\necho \"Regenerating test clients...\"\nnpm run regenerate\n```\n\nAfter successful regeneration, update the marker:\n\n```bash\ntouch .last-regenerate\n```\n\nIf regeneration fails, report the error and stop.\n\nIf regeneration is NOT needed, inform the user:\n\n> \"Generated code is up to date (source unchanged since last regeneration). Skipping regenerate.\"\n\n### Step 4: Run the generator test suite\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\nnpm run ci\n```\n\nThis runs:\n\n1. `test:emitter` - vitest unit tests for the emitter\n2. `ci:generator` - pytest tests against generated code\n\nThe full CI can take several minutes. Keep the user informed that it's running.\n\n### Step 5: Report results\n\n- **If tests pass**: Confirm success and summarize any notable output (warnings, skipped tests, etc.)\n- **If tests fail**: Show the failing test names and error messages clearly.\n  Offer to help debug or investigate specific failures.\n\n## Integration with diff-upstream\n\nBoth skills share the regeneration marker system:\n\n- `diff-upstream` always regenerates and updates `.last-regenerate`\n- `test-unbranded-emitter` checks this marker and skips regeneration if fresh\n\n**Efficient workflow**:\n\n```\ndiff-upstream → test-unbranded-emitter\n```\n\nThe second command will skip regeneration since `diff-upstream` just did it.\n\n**Standalone workflow**:\n\n```\ntest-unbranded-emitter\n```\n\nWill regenerate only if source changed since last run.\n\n## Notes\n\n### Regeneration takes time\n\n`npm run regenerate` can take 2-3 minutes. The staleness check avoids this delay\nwhen the user is iterating on test fixes (not emitter changes).\n\n### Test types\n\n| Command                  | What it runs              | Duration     |\n| ------------------------ | ------------------------- | ------------ |\n| `npm run test:emitter`   | vitest unit tests only    | ~5 seconds   |\n| `npm run test:generator` | pytest only (no vitest)   | ~2 minutes   |\n| `npm run ci`             | vitest + pytest (full CI) | ~2-3 minutes |\n\nThis skill runs `npm run ci` (full CI). If the user wants just unit tests or\njust pytest, they can ask specifically.\n\n### Known flaky test\n\nThe test server teardown sometimes fails with `ProcessLookupError` - this is a\npre-existing infrastructure issue, not a test failure. All actual tests may pass\neven if you see this error at the end.\n\n### Force regeneration\n\nIf the user suspects stale generated code despite the marker, they can force\nregeneration:\n\n```bash\nrm ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\u002F.last-regenerate\n```\n\nThen run the skill again.\n\n## Gitignore\n\nEnsure this entry is in the package's `.gitignore`:\n\n```\n.last-regenerate\n```\n","# Test Emitter Skill\n\nBuilds and tests `@typespec\u002Fhttp-client-python` to validate local changes.\nAutomatically regenerates if the generated code is stale.\n\n## Paths\n\nAll paths are relative to the http-client-python package root:\n`~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python`\n\n| Item                  | Path                                                    |\n| --------------------- | ------------------------------------------------------- |\n| Package root          | `~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python` |\n| Emitter source        | `emitter\u002Fsrc`                                           |\n| Generated (unbranded) | `generator\u002Ftest\u002Funbranded\u002Fgenerated`                    |\n| Generated (azure)     | `generator\u002Ftest\u002Fazure\u002Fgenerated`                        |\n| Regenerate marker     | `.last-regenerate`                                      |\n\n## Workflow\n\n### Step 1: Build the emitter\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\nnpm run build\n```\n\nCheck for TypeScript compilation errors. If the build fails, report the errors\nto the user and stop — do not proceed to testing.\n\n### Step 2: Check if regeneration is needed\n\nRegeneration is needed if ANY of these conditions are true:\n\n1. **Generated folder doesn't exist or is empty**:\n\n   ```bash\n   cd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\n   \n   if [ ! -d \"generator\u002Ftest\u002Funbranded\u002Fgenerated\" ] \\\n     || [ -z \"$(ls -A generator\u002Ftest\u002Funbranded\u002Fgenerated 2> \u002Fdev\u002Fnull)\" ]; then\n     echo \"Unbranded generated folder is empty - regeneration needed\"\n   fi\n   \n   if [ ! -d \"generator\u002Ftest\u002Fazure\u002Fgenerated\" ] \\\n     || [ -z \"$(ls -A generator\u002Ftest\u002Fazure\u002Fgenerated 2> \u002Fdev\u002Fnull)\" ]; then\n     echo \"Azure generated folder is empty - regeneration needed\"\n   fi\n   ```\n\n2. **No regenerate marker file exists**:\n\n   ```bash\n   if [ ! -f \".last-regenerate\" ]; then\n     echo \"No regenerate marker - regeneration needed\"\n   fi\n   ```\n\n3. **Emitter source files are newer than the marker**:\n   ```bash\n   if [ -n \"$(find emitter\u002Fsrc -newer .last-regenerate -type f 2> \u002Fdev\u002Fnull | head -1)\" ]; then\n     echo \"Emitter source changed since last regenerate - regeneration needed\"\n   fi\n   ```\n\n### Step 3: Regenerate if needed\n\nIf any condition from Step 2 is true:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\necho \"Regenerating test clients...\"\nnpm run regenerate\n```\n\nAfter successful regeneration, update the marker:\n\n```bash\ntouch .last-regenerate\n```\n\nIf regeneration fails, report the error and stop.\n\nIf regeneration is NOT needed, inform the user:\n\n> \"Generated code is up to date (source unchanged since last regeneration). Skipping regenerate.\"\n\n### Step 4: Run the generator test suite\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\nnpm run ci\n```\n\nThis runs:\n\n1. `test:emitter` - vitest unit tests for the emitter\n2. `ci:generator` - pytest tests against generated code\n\nThe full CI can take several minutes. Keep the user informed that it's running.\n\n### Step 5: Report results\n\n- **If tests pass**: Confirm success and summarize any notable output (warnings, skipped tests, etc.)\n- **If tests fail**: Show the failing test names and error messages clearly.\n  Offer to help debug or investigate specific failures.\n\n## Integration with diff-upstream\n\nBoth skills share the regeneration marker system:\n\n- `diff-upstream` always regenerates and updates `.last-regenerate`\n- `test-unbranded-emitter` checks this marker and skips regeneration if fresh\n\n**Efficient workflow**:\n\n```\ndiff-upstream → test-unbranded-emitter\n```\n\nThe second command will skip regeneration since `diff-upstream` just did it.\n\n**Standalone workflow**:\n\n```\ntest-unbranded-emitter\n```\n\nWill regenerate only if source changed since last run.\n\n## Notes\n\n### Regeneration takes time\n\n`npm run regenerate` can take 2-3 minutes. The staleness check avoids this delay\nwhen the user is iterating on test fixes (not emitter changes).\n\n### Test types\n\n| Command                  | What it runs              | Duration     |\n| ------------------------ | ------------------------- | ------------ |\n| `npm run test:emitter`   | vitest unit tests only    | ~5 seconds   |\n| `npm run test:generator` | pytest only (no vitest)   | ~2 minutes   |\n| `npm run ci`             | vitest + pytest (full CI) | ~2-3 minutes |\n\nThis skill runs `npm run ci` (full CI). If the user wants just unit tests or\njust pytest, they can ask specifically.\n\n### Known flaky test\n\nThe test server teardown sometimes fails with `ProcessLookupError` - this is a\npre-existing infrastructure issue, not a test failure. All actual tests may pass\neven if you see this error at the end.\n\n### Force regeneration\n\nIf the user suspects stale generated code despite the marker, they can force\nregeneration:\n\n```bash\nrm ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002Fhttp-client-python\u002F.last-regenerate\n```\n\nThen run the skill again.\n\n## Gitignore\n\nEnsure this entry is in the package's `.gitignore`:\n\n```\n.last-regenerate\n```\n",{"name":5,"description":7},"main","05b9bad7c57b9b58e8fb5390f9bab081a1a9ac31","packages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Ftest-unbranded-emitter",423,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec","https:\u002F\u002Ftypespec.io\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 06:59:49",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add microsoft\u002Ftypespec --skill test-unbranded-emitter",{"tool":70,"command":71},"bunx","bunx skills add microsoft\u002Ftypespec --skill test-unbranded-emitter",{"tool":73,"command":74},"pnpm","pnpm dlx skills add microsoft\u002Ftypespec --skill test-unbranded-emitter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Ftest-unbranded-emitter\u002FSKILL.md",true,[],[79,103,124,156,169,188],{"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":86,"publishedAt":49},"01M69B7H23BJ7ART6SA67EFJ5W","generate-from-typespec","Generate Python SDK code from a TypeSpec specification using the local emitter. Use this skill when the user wants to generate\u002Fregenerate a Python client from a TypeSpec spec, provides a GitHub URL or local path to a TypeSpec project, or says things like \"generate from this spec\", \"emit Python from this tsp\", \"regenerate the SDK\", or \"compile this TypeSpec for Python\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Fgenerate-from-typespec\u002FSKILL.md",[85],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[43,87,88,89,48,90,91,92,93,94,95,37,96,34,97,98,99,100,101,102],"generate from typespec","generate","spec","github","sdk","code","compile","python sdk","user","specification","project","client","URL","for","things","when",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":49},"01M69B7EJ0F9HGY2Y8RMX9C4E6","diff-upstream","Regenerate the local emitter and diff the generated code against the upstream baseline checked into autorest.python. Use this skill when the user wants to see how their emitter changes affect generated code compared to what's currently in production, says things like \"diff upstream\", \"compare to baseline\", \"what changed vs production\", \"show me the diff\", \"how does this affect generated code\", or wants to validate their changes produce the expected output differences.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Fdiff-upstream\u002FSKILL.md",[109],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[111,112,113,48,46,92,114,115,116,117,118,37,119,120,34,121,122,101,30,123,102],"diff upstream","diff","upstream","produce","baseline","show me","how","generated","show","me","compare","output","expected",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":144,"publishedAt":49},"01M69B7BHV2RTK64BZ8NQGFPNE","writing-python-sdk-spector-mock-api-tests","Writes TypeSpec http-client-python generator mock API tests (azure\u002Funbranded\u002Fshared) from a Spector case. Use when given a Spector case link or a PR link that modifies Spector cases under http-specs\u002Fazure-http-specs.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpython-sdk-spector-mock-api-tests\u002FSKILL.md",[130,133,136,141],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":142,"categoryName":143,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000036","内容创作者",[145,48,91,146,147,94,148,33,149,150,151,44,152,43,37,153,154,155,31,102],"writing","writing python sdk spector mock api tests","api","writing python","mock","mock api","azure","pr","shared","link","case",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":49},"01M69B79NV57JMNA7RS13MAE5P","pnpm-format","Format the codebase with pnpm and recover from common formatting failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpnpm-format\u002FSKILL.md",[],[163,164,73,165,166,167,168],"pnpm format","format","common","formatting","with","codebase",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":49},"01M69B784PEAQ45ZKNZAX9NCA9","minimal-repro","Help create a minimal reproduction for a TypeSpec compiler or emitter bug. Use when a user provides TypeSpec source (pasted code or a GitHub URL) and describes an issue. Reproduces locally and reduces to a single-file repro.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fminimal-repro\u002FSKILL.md",[],[176,177,178,90,43,179,92,180,181,182,95,37,183,184,185,99,100,186,187,102],"minimal repro","repro","minimal","create","help","compiler","file","single-file","bug","issue","source","single",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":49},"01M69B76464N72EBS07HC4NMWJ","http-client-python-bump-and-release","Create a PR to bump TypeSpec\u002FAzure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhttp-client-python-bump-and-release\u002FSKILL.md",[],[48,44,195,196,197,98,198,151,152,43,179,199,41,200,201,202,203,204],"http client python bump and release","release","bump","http client","update","Tools","version","peer","dependencies","new"]