Organization Level Support for AI Capabilities using .github-private

[smaglio81]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Coding Agent

Body

Hello,

The capability to define reusable Copilot Coding Agents for use across an organization is supported by adding agent profiles under an agents directory in your organizations .github-private repository.

The github/awesome-copilot repository also defines agents within an agents directory. It also provides folders for other common AI tools like skills, plugins, instructions, hooks, etc.

Can the organization level .github-private repository have more functionality added to, in order to support these folders as standardized locations for the Copilot Coding Agents to use when working within organization repository.

For example, if the cloud-design-patterns skill was added to an organizations .github-private repository under the skills folder. Then a Coding Agent profile from the agents folder can reference that skill in it's agent.md and the skill will be available for the Coding Agent to use in every repository in the organization.

It can see this being useful for:

• Skills
• Plugins
• Hooks

I would imagine that organizations wouldn't want all skills, plugins, hooks etc to be available on every run of a Coding Agent within their individual repositories. But, if a skill, plugin, etc was explicitly defined within the frontmatter of an agent, then the relevant AI tools could be copied into the Coding Agents workspace.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐