AI Explorer is configured through the Portal Config Manager.
Navigate to Admin → Catalog Settings → Providers.
Then configure which GitHub hosts to scan for agent resources. The entity providers use GitHub code search to automatically discover rule files and SKILL.md files.
Hosts, organizations, and repositories
Each entry in the provider’s hosts list tells AI Explorer where to look for resources. You can add multiple entries to scan across different GitHub instances or organizations.
Every host entry requires a host — the GitHub hostname (e.g. github.com or your GitHub Enterprise hostname like ghe.example.com). The host must have a matching GitHub integration configured with credentials that have read access to repository contents.
From there, you can control the scope of what gets scanned:
Scanning an entire host
If all repositories on your GitHub instance belong to your company, you can scan the entire host without specifying an organization or repository list. This discovers resources across every repository accessible to your integration credentials:
This is useful when your GitHub Enterprise instance spans multiple organizations and you want AI Explorer to discover resources from all of them without maintaining a list.
This option is only recommended for private GitHub Enterprise instances where
all repositories on the host belong to your company. Do not use this with
github.com — without an organization or repository scope, AI Explorer will
attempt to search across all of GitHub, which will quickly hit API rate limits
and return incomplete results.
Scanning an organization
Set the organization field to limit scanning to a single GitHub org. This is the most common setup — it keeps AI Explorer focused on your organization’s repositories without needing to list them individually.
You can scan multiple organizations by adding separate host entries, even on the same GitHub instance:
You can also mix GitHub.com and GitHub Enterprise entries in the same configuration:
Scanning specific repositories
If you only want AI Explorer to discover resources from a known set of repositories, list them explicitly using the repos field. Each entry uses the owner/repo format:
Configuring AI Explorer
Once enabled, configure AI Explorer at Admin → Plugin Settings → AI Explorer. The settings form is organized into sections matching the options below.
Certification
As the number of agent resources in your organization grows, developers need a way to know which ones they can trust. Certification lets you designate the teams responsible for AI enablement — such as a platform engineering group or an AI advisory board — so their resources are clearly distinguished from community contributions. This is especially valuable when skills automate high-impact workflows like deployments, migrations, or security reviews, where using an unvetted skill could introduce risk.
Add entity refs (e.g. group:default/platform-team) to the Certified Owners list. Resources owned by any entity in this list display a certified badge and can be filtered for in the browse UI.
Hiding tabs
If some resource types aren’t relevant for your organization, you can hide their tabs from the AI Explorer page. Add tab IDs to the Hidden Tabs list. Valid values: rules, plugins, skills. 
