Agent Skills Extension

VS Code extension to browse, install, and manage AI agent skills, instructions, and agents from Git registries (GitHub and Azure DevOps).

Features

• Browse available skills, instructions, agents, and MCP servers from configured Git registries
• Install items directly into your workspace (.claude/skills, .claude/rules, .claude/agents)
• Install MCP servers into .vscode/mcp.json (VS Code native MCP configuration)
• Support for GitHub and Azure DevOps Repos as skill sources
• GitHub token support for private registries
• Microsoft Entra sign-in for Azure DevOps Services registries
• TTL-based caching to reduce API calls
• Workspace trust enforcement (installation requires trusted workspace)

Requirements

• Node.js 22.x for development and packaging
• VS Code >= 1.85.0

Configuration

{
  "agentSkills.repositories": [
    {
      "provider": "github",
      "owner": "my-org",
      "repo": "skills-registry",
      "branch": "main"
    },
    {
      "provider": "azure-devops",
      "organization": "my-org",
      "project": "my-project",
      "repo": "skills-registry",
      "branch": "main"
    }
  ],
  "agentSkills.installLocations": [".claude", ".github", ".cursor"],
  "agentSkills.cacheTTL": 3600
}

Authentication

• GitHub: run Agent Skills: Set GitHub Token (agentSkills.setToken) to store a Personal Access Token for private repositories.
• Azure DevOps Services: run Agent Skills: Sign In to Azure DevOps (agentSkills.signInAzureDevOps) to authenticate with your Microsoft Entra account.
• Azure DevOps Server/on-premises is not covered by the Azure DevOps Services sign-in flow.

Extension Settings

Registry Structure

A skills registry repository is expected to follow this directory layout:

skills/           → skill items
instructions/     → instruction items
agents/           → agent items
mcps/             → MCP server items (each must contain a mcp.json)
manifest.json     → optional metadata

MCP Servers

MCP server items must contain a mcp.json file with the server configuration. When installed, the extension merges the server entry into .vscode/mcp.json in the workspace root, which is the native VS Code MCP configuration file.

Example registry entry:

mcps/
  my-mcp-server/
    mcp.json

Example mcp.json:

{
  "servers": {
    "my-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "my-mcp-server"]
    }
  }
}

Development

Use the Node version declared in .nvmrc before installing dependencies or packaging the extension:

nvm use

npm install
npm run build
npm test
npm run lint

Local Testing in VS Code

To test the extension locally in VS Code, run it in an Extension Development Host:

1. Start the bundle in watch mode:

npm run watch

2. In VS Code, open the Run and Debug view and press F5 to launch a new Extension Development Host window.
3. In the new window, open a workspace you want to use for testing.
4. Configure agentSkills.repositories with at least one test registry. Example for Azure DevOps Services:

{
  "agentSkills.repositories": [
    {
      "provider": "azure-devops",
      "organization": "my-org",
      "project": "my-project",
      "repo": "skills-registry",
      "branch": "main"
    }
  ]
}

5. Open the Agent Skills view in the Activity Bar.
6. For Azure DevOps Services, run Agent Skills: Sign In to Azure DevOps.
7. Run Agent Skills: Refresh if the marketplace does not refresh automatically after sign-in.
8. Validate the main flows:

• browse marketplace items
• open item details
• install an item into the workspace
• confirm GitHub registries still work if configured alongside Azure DevOps

Expected Results

• Azure DevOps Services does not ask for a PAT
• Microsoft sign-in completes successfully
• marketplace items load after authentication
• item details and installation work normally
• GitHub behavior remains unchanged

License

MIT