[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699B6VSJCNZEAVM5RTZ83SE":3,"skill-same:01M699B6VSJCNZEAVM5RTZ83SE":70},{"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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M699B6VSJCNZEAVM5RTZ83SE","python-feature-lifecycle",null,"Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.","microsoft\u002Fagent-framework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6999R99RF2DY8AXYFS5HZRM",14676,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002F.github\u002Fskills\u002Fpython-feature-lifecycle\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"python","python feature lifecycle","lifecycle","feature","agent framework","framework","package","how","guidance","next","stage","how to","decorators","move","for","codebase","2026-11-10 10:12:30",false,"---\nname: python-feature-lifecycle\ndescription: >\n  Guidance for package and feature lifecycle in the Agent Framework Python\n  codebase, including stage meanings, feature-stage decorators, feature enums,\n  and how to move APIs from one stage to the next.\n---\n\n# Python Feature Lifecycle\n\n## Two lifecycle levels\n\nAgent Framework uses lifecycle at two different levels:\n\n1. **Package lifecycle** — the maturity of the package as a whole\n2. **Feature lifecycle** — the maturity of a specific API or feature inside that package\n\nThese are related, but they are **not the same thing**.\n\n- The **package stage is the default** for everything in the package.\n- **Feature-stage decorators are only for exceptions** when a feature is behind the package's default stage.\n- Do **not** decorate every class or function just because the package is experimental or release candidate.\n\nThis skill describes staged API behavior within a package. For creating or promoting a package, including sample\nplacement, meta-package membership, versioning, and lazy-loading namespace decisions, follow the\n`python-package-management` skill.\n\n### Important default\n\nIf a package is still in **beta \u002F experimental preview**, all public APIs in that package are experimental by default.\n\n- Do **not** add `@experimental(...)` everywhere in that package.\n- The package stage already communicates that default.\n\nOnce a package moves forward, you can keep individual features behind:\n\n- If a package moves to **release candidate**, a feature may remain **experimental**\n- If a package moves to **released \u002F GA**, a feature may remain **experimental** or **release candidate**\n\nThat is the main use case for feature-stage decorators.\n\n## The four stages\n\n### 1. Experimental\n\nUse for features that are still unstable and may change or be removed without notice.\n\nFeature-level code pattern:\n\n```python\nfrom ._feature_stage import ExperimentalFeature, experimental\n\n\n@experimental(feature_id=ExperimentalFeature.MY_FEATURE)\nclass MyFeature:\n    ...\n```\n\nBehavior:\n\n- Adds an experimental warning block to the docstring\n- Records feature metadata on the decorated object\n- Emits a runtime warning the first time the feature is used (once per feature by default)\n\nEnum setup:\n\n- Add an all-caps member to `ExperimentalFeature`\n- Reuse the same feature ID across all APIs that belong to the same conceptual feature\n\n### 2. Release candidate\n\nUse for features that are nearly stable but may still receive small refinements before GA.\n\nFeature-level code pattern:\n\n```python\nfrom ._feature_stage import ReleaseCandidateFeature, release_candidate\n\n\n@release_candidate(feature_id=ReleaseCandidateFeature.MY_FEATURE)\nclass MyFeature:\n    ...\n```\n\nBehavior:\n\n- Adds a release-candidate note to the docstring\n- Records feature metadata on the decorated object\n- Does **not** emit the experimental warning\n\nEnum setup:\n\n- Add an all-caps member to `ReleaseCandidateFeature`\n\n### 3. Released\n\nUse for stable GA APIs.\n\nCode pattern:\n\n- **No feature-stage decorator**\n- **No entry** in `ExperimentalFeature`\n- **No entry** in `ReleaseCandidateFeature`\n\nIf a feature is fully released, remove any stage-specific feature annotation.\n\n### 4. Deprecated\n\nUse for APIs that still exist but should not be used for new code.\n\nCode pattern:\n\n```python\nimport sys\n\nif sys.version_info >= (3, 13):\n    from warnings import deprecated  # type: ignore # pragma: no cover\nelse:\n    from typing_extensions import deprecated  # type: ignore # pragma: no cover\n\n\n@deprecated(\"MyOldFeature is deprecated. Use MyNewFeature instead.\")\nclass MyOldFeature:\n    ...\n```\n\nBehavior:\n\n- Uses the repository's version-conditional deprecation import pattern\n- Should describe what to use instead\n\nDeprecated APIs should not also carry feature-stage decorators.\n\n## Expected decorators by stage\n\n| Feature stage | Expected annotation |\n| --- | --- |\n| Experimental | `@experimental(feature_id=ExperimentalFeature.X)` |\n| Release candidate | `@release_candidate(feature_id=ReleaseCandidateFeature.X)` |\n| Released | No feature-stage decorator |\n| Deprecated | `@deprecated(\"...\")` |\n\n## Feature enums\n\nThe feature enums are the inventory of currently staged features:\n\n- `ExperimentalFeature`\n- `ReleaseCandidateFeature`\n\nGuidance:\n\n- Use one enum member per conceptual feature, not per class\n- Ideally, an ADR already defines the overall feature boundary and therefore the feature ID that staged APIs for that feature should reuse\n- Keep feature IDs all caps\n- Reuse the same member across related APIs for the same feature\n- Remove enum members when the feature no longer belongs to that stage\n- Treat these enums as **current-stage inventories**, not as a stable consumer introspection API\n\nMinimal consumer guidance:\n\n- Treat `__feature_stage__` and `__feature_id__` as optional staged metadata, not as stable contracts\n- Use `getattr(obj, \"__feature_stage__\", None)` and `getattr(obj, \"__feature_id__\", None)` rather than direct attribute access\n- Treat missing metadata as \"no explicit feature-stage annotation\"\n- For warning filters while a feature is staged, match the literal feature ID string\n- Do **not** rely on `ExperimentalFeature.X`, `ReleaseCandidateFeature.X`, or the continued presence of `__feature_id__` after a feature moves stages or is released\n\nFor consumers, the enums are also re-exported from `agent_framework`.\n\nFor internal implementation code inside `agent_framework`, continue to import the enums and decorators from `._feature_stage`.\n\n## Package stage vs feature stage\n\nUse the following rules:\n\n### Package is experimental \u002F beta\n\n- All public APIs are experimental by default\n- Do **not** add feature-stage decorators just to restate that\n- Only introduce feature-level annotations later if the package advances first\n\n### Package is release candidate\n\n- All public APIs are RC by default\n- Do **not** decorate everything\n- Add `@experimental(...)` only for features that are intentionally still behind the package\n\n### Package is released \u002F GA\n\n- All public APIs are released by default\n- Add `@experimental(...)` or `@release_candidate(...)` only for features still being held back\n\n## Moving a feature from one stage to the next\n\n### Experimental -> Release candidate\n\n1. Move the feature ID from `ExperimentalFeature` to `ReleaseCandidateFeature`\n2. Replace `@experimental(...)` with `@release_candidate(...)`\n3. Update any tests or docs that mention the old stage\n\n### Experimental -> Released\n\n1. Remove `@experimental(...)`\n2. Remove the feature from `ExperimentalFeature`\n3. Do not add a replacement feature-stage decorator\n\n### Release candidate -> Released\n\n1. Remove `@release_candidate(...)`\n2. Remove the feature from `ReleaseCandidateFeature`\n3. Leave the API undecorated\n\n### Any stage -> Deprecated\n\n1. Remove any feature-stage decorator\n2. Remove the feature from the stage enum\n3. Add `@deprecated(\"...\")`\n4. Update docs\u002Ftests to reflect the replacement path\n\n## Promotion guidance\n\nFeatures do **not** have to pass through every stage.\n\n- It is usually a good idea to move features in order when that reflects reality\n- But it is completely acceptable to go **experimental -> released**\n- Do **not** force a feature through release candidate if there is no real RC period\n\nLikewise, when a package advances, do not automatically move every feature with it.\n\n- Promote features based on actual readiness\n- Keep lagging features explicitly marked only when they are behind the package default\n\n## Practical rules of thumb\n\n- **Package default first, feature exceptions second**\n- **Do not decorate everything in preview packages**\n- **Do not double-annotate members of an already-staged class**\n- **Use enums only for currently staged features**\n- **Do not treat stage enums as a compatibility contract**\n- **Treat `__feature_stage__` and `__feature_id__` as optional metadata; use `getattr`**\n- **Remove stage annotations once a feature is released or deprecated**\n","# Python Feature Lifecycle\n\n## Two lifecycle levels\n\nAgent Framework uses lifecycle at two different levels:\n\n1. **Package lifecycle** — the maturity of the package as a whole\n2. **Feature lifecycle** — the maturity of a specific API or feature inside that package\n\nThese are related, but they are **not the same thing**.\n\n- The **package stage is the default** for everything in the package.\n- **Feature-stage decorators are only for exceptions** when a feature is behind the package's default stage.\n- Do **not** decorate every class or function just because the package is experimental or release candidate.\n\nThis skill describes staged API behavior within a package. For creating or promoting a package, including sample\nplacement, meta-package membership, versioning, and lazy-loading namespace decisions, follow the\n`python-package-management` skill.\n\n### Important default\n\nIf a package is still in **beta \u002F experimental preview**, all public APIs in that package are experimental by default.\n\n- Do **not** add `@experimental(...)` everywhere in that package.\n- The package stage already communicates that default.\n\nOnce a package moves forward, you can keep individual features behind:\n\n- If a package moves to **release candidate**, a feature may remain **experimental**\n- If a package moves to **released \u002F GA**, a feature may remain **experimental** or **release candidate**\n\nThat is the main use case for feature-stage decorators.\n\n## The four stages\n\n### 1. Experimental\n\nUse for features that are still unstable and may change or be removed without notice.\n\nFeature-level code pattern:\n\n```python\nfrom ._feature_stage import ExperimentalFeature, experimental\n\n\n@experimental(feature_id=ExperimentalFeature.MY_FEATURE)\nclass MyFeature:\n    ...\n```\n\nBehavior:\n\n- Adds an experimental warning block to the docstring\n- Records feature metadata on the decorated object\n- Emits a runtime warning the first time the feature is used (once per feature by default)\n\nEnum setup:\n\n- Add an all-caps member to `ExperimentalFeature`\n- Reuse the same feature ID across all APIs that belong to the same conceptual feature\n\n### 2. Release candidate\n\nUse for features that are nearly stable but may still receive small refinements before GA.\n\nFeature-level code pattern:\n\n```python\nfrom ._feature_stage import ReleaseCandidateFeature, release_candidate\n\n\n@release_candidate(feature_id=ReleaseCandidateFeature.MY_FEATURE)\nclass MyFeature:\n    ...\n```\n\nBehavior:\n\n- Adds a release-candidate note to the docstring\n- Records feature metadata on the decorated object\n- Does **not** emit the experimental warning\n\nEnum setup:\n\n- Add an all-caps member to `ReleaseCandidateFeature`\n\n### 3. Released\n\nUse for stable GA APIs.\n\nCode pattern:\n\n- **No feature-stage decorator**\n- **No entry** in `ExperimentalFeature`\n- **No entry** in `ReleaseCandidateFeature`\n\nIf a feature is fully released, remove any stage-specific feature annotation.\n\n### 4. Deprecated\n\nUse for APIs that still exist but should not be used for new code.\n\nCode pattern:\n\n```python\nimport sys\n\nif sys.version_info >= (3, 13):\n    from warnings import deprecated  # type: ignore # pragma: no cover\nelse:\n    from typing_extensions import deprecated  # type: ignore # pragma: no cover\n\n\n@deprecated(\"MyOldFeature is deprecated. Use MyNewFeature instead.\")\nclass MyOldFeature:\n    ...\n```\n\nBehavior:\n\n- Uses the repository's version-conditional deprecation import pattern\n- Should describe what to use instead\n\nDeprecated APIs should not also carry feature-stage decorators.\n\n## Expected decorators by stage\n\n| Feature stage | Expected annotation |\n| --- | --- |\n| Experimental | `@experimental(feature_id=ExperimentalFeature.X)` |\n| Release candidate | `@release_candidate(feature_id=ReleaseCandidateFeature.X)` |\n| Released | No feature-stage decorator |\n| Deprecated | `@deprecated(\"...\")` |\n\n## Feature enums\n\nThe feature enums are the inventory of currently staged features:\n\n- `ExperimentalFeature`\n- `ReleaseCandidateFeature`\n\nGuidance:\n\n- Use one enum member per conceptual feature, not per class\n- Ideally, an ADR already defines the overall feature boundary and therefore the feature ID that staged APIs for that feature should reuse\n- Keep feature IDs all caps\n- Reuse the same member across related APIs for the same feature\n- Remove enum members when the feature no longer belongs to that stage\n- Treat these enums as **current-stage inventories**, not as a stable consumer introspection API\n\nMinimal consumer guidance:\n\n- Treat `__feature_stage__` and `__feature_id__` as optional staged metadata, not as stable contracts\n- Use `getattr(obj, \"__feature_stage__\", None)` and `getattr(obj, \"__feature_id__\", None)` rather than direct attribute access\n- Treat missing metadata as \"no explicit feature-stage annotation\"\n- For warning filters while a feature is staged, match the literal feature ID string\n- Do **not** rely on `ExperimentalFeature.X`, `ReleaseCandidateFeature.X`, or the continued presence of `__feature_id__` after a feature moves stages or is released\n\nFor consumers, the enums are also re-exported from `agent_framework`.\n\nFor internal implementation code inside `agent_framework`, continue to import the enums and decorators from `._feature_stage`.\n\n## Package stage vs feature stage\n\nUse the following rules:\n\n### Package is experimental \u002F beta\n\n- All public APIs are experimental by default\n- Do **not** add feature-stage decorators just to restate that\n- Only introduce feature-level annotations later if the package advances first\n\n### Package is release candidate\n\n- All public APIs are RC by default\n- Do **not** decorate everything\n- Add `@experimental(...)` only for features that are intentionally still behind the package\n\n### Package is released \u002F GA\n\n- All public APIs are released by default\n- Add `@experimental(...)` or `@release_candidate(...)` only for features still being held back\n\n## Moving a feature from one stage to the next\n\n### Experimental -> Release candidate\n\n1. Move the feature ID from `ExperimentalFeature` to `ReleaseCandidateFeature`\n2. Replace `@experimental(...)` with `@release_candidate(...)`\n3. Update any tests or docs that mention the old stage\n\n### Experimental -> Released\n\n1. Remove `@experimental(...)`\n2. Remove the feature from `ExperimentalFeature`\n3. Do not add a replacement feature-stage decorator\n\n### Release candidate -> Released\n\n1. Remove `@release_candidate(...)`\n2. Remove the feature from `ReleaseCandidateFeature`\n3. Leave the API undecorated\n\n### Any stage -> Deprecated\n\n1. Remove any feature-stage decorator\n2. Remove the feature from the stage enum\n3. Add `@deprecated(\"...\")`\n4. Update docs\u002Ftests to reflect the replacement path\n\n## Promotion guidance\n\nFeatures do **not** have to pass through every stage.\n\n- It is usually a good idea to move features in order when that reflects reality\n- But it is completely acceptable to go **experimental -> released**\n- Do **not** force a feature through release candidate if there is no real RC period\n\nLikewise, when a package advances, do not automatically move every feature with it.\n\n- Promote features based on actual readiness\n- Keep lagging features explicitly marked only when they are behind the package default\n\n## Practical rules of thumb\n\n- **Package default first, feature exceptions second**\n- **Do not decorate everything in preview packages**\n- **Do not double-annotate members of an already-staged class**\n- **Use enums only for currently staged features**\n- **Do not treat stage enums as a compatibility contract**\n- **Treat `__feature_stage__` and `__feature_id__` as optional metadata; use `getattr`**\n- **Remove stage annotations once a feature is released or deprecated**\n",{"name":5,"description":7},"main","b7884ad88eb85c27b2a7bf40c0e15948e7ccc28d","python\u002F.github\u002Fskills\u002Fpython-feature-lifecycle",2624,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework","https:\u002F\u002Faka.ms\u002Fagent-framework","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 14:06:55",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add microsoft\u002Fagent-framework --skill python-feature-lifecycle",{"tool":56,"command":57},"bunx","bunx skills add microsoft\u002Fagent-framework --skill python-feature-lifecycle",{"tool":59,"command":60},"pnpm","pnpm dlx skills add microsoft\u002Fagent-framework --skill python-feature-lifecycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002F.github\u002Fskills\u002Fpython-feature-lifecycle\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"plan-document-reviewer-prompt.md","REFERENCE","参考文档",1714,"https:\u002F\u002Fgithub.com\u002Fwallfacers\u002Fdata-talk\u002Fblob\u002Fmaster\u002Fserver\u002Fdata-talk-adapter\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fwriting-plans\u002Fplan-document-reviewer-prompt.md",[71,96,125,135,158,175],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":35},"01M70H1GNJPW85ENXA0BCPC6PF","draft-release-notes","Create or rewrite Agent Framework release notes from a generated GitHub release log. Use when preparing Python or .NET release notes, filtering mixed-language changelogs, deduplicating changes, preserving inline contributor credits, or documenting breaking-change migrations from pull requests. Requires the user to provide the generated GitHub log, language, and release version before work begins.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdraft-release-notes\u002FSKILL.md",[],[78,79,80,81,82,19,23,83,84,85,86,87,88,89,90,91,92,93,94,95],"notes","release notes","release","draft","draft release notes","pull requests","create","pull","generated","filtering","use","version","log","release version","rewrite","mixed-language","contributor","when",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":35},"01M699C55AYGT1ZVZDHWFZNBDB","agent-framework-builder-python","Use this skill when building, modifying, reviewing, evaluating, integrating, or hosting Python applications with Microsoft Agent Framework. Use it for Agent Framework agents, harness agents, workflows, orchestrations, declarative definitions, tools, sessions, middleware, evaluation, observability, integrations, or hosting, even when the user has not yet chosen the correct framework pattern.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fskills\u002Fagent-framework-builder-python\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[19,23,108,24,109,9,110,111,112,113,114,115,116,117,118,88,119,120,121,122,123,33,124,95],"agent framework builder python","builder","workflows","sessions","microsoft agent framework","harness","observability","Evaluation","applications","correct","integrations","hosting","pattern","middleware","with","orchestrations","declarative",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":35},"01M699C2PH4WPRCMV90NHANCY9","agent-framework-builder-dotnet","Use this skill when building, modifying, reviewing, evaluating, integrating, or hosting .NET (C#) applications with Microsoft Agent Framework. Use it for Agent Framework agents, harness agents, workflows, orchestrations, declarative definitions, tools, sessions, middleware, evaluation, observability, integrations, or hosting, even when the user has not yet chosen the correct framework pattern.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fskills\u002Fagent-framework-builder-dotnet\u002FSKILL.md",[131],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[23,133,134,24,109,9,110,111,112,113,114,116,117,118,88,121,122,123,33,124,95],"dotnet","agent framework builder dotnet",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":35},"01M699C0QKV5XEBE61PB8NV544","foundry-hosted-agent-validation","Step-by-step process for validating a Python Foundry hosted agent sample (under python\u002Fsamples\u002F04-hosting\u002Ffoundry-hosted-agents\u002F) end to end — running it locally (native runtime and `azd ai agent run`) and after deploying it to an Azure AI Foundry project with `azd`. Use this when asked to validate a hosted agent sample.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fscripts\u002Fsample_validation\u002Fskills\u002Ffoundry-hosted-agent-validation\u002FSKILL.md",[141],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[143,144,145,19,146,147,148,149,24,150,151,88,152,153,154,155,156,33,95,157],"foundry","foundry hosted agent validation","validation","ai agent","azure","run","azure ai foundry","tool","model","project","sample","runtime","end","native","running",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":35},"01M699BYCYJD8RXC5MYY61WBPR","foundry-config-setup","Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder\u002Fhardcoded project_endpoint (for example \"https:\u002F\u002Fyour-project.services.ai.azure.com\") or a hardcoded model instead of reading them from the environment.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fscripts\u002Fsample_validation\u002Fskills\u002Ffoundry-config-setup\u002FSKILL.md",[],[143,165,166,167,168,147,169,170,171,150,151,172,88,173,152,153,174,122,33,95],"foundry config setup","config","setup","placeholder","tool use","https","services","environment","example","missing",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":35},"01M699BWSTE6SGCCBY3JFP10GQ","support-style","Contoso Outdoors customer-support tone and formatting guidelines.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fsamples\u002F04-hosting\u002Ffoundry-hosted-agents\u002Fresponses\u002Ffoundry_toolbox_mcp_skills\u002Fskills\u002Fsupport-style\u002FSKILL.md",[],[182,183,184,185,186,187,188],"support","support style","style","customer","guidelines","tone","formatting"]