Skill Manager for VS Code
Skill Manager provides two Activity Bar views for moving skill directories between the opened project and an external local repository. It targets VS Code 1.138 or newer on Windows 10 or later.
The extension works with local files only. It does not inspect, stage, pull, push, commit, or otherwise automate Git. The local repository is managed externally by the user. Remote skill operations are deferred and are not implemented.
User workflow
- Open a project folder in VS Code.
- Open the Skill Manager container in the Activity Bar.
- Use Project Skills to view directories under
.github/skills in the current workspace.
- Use Local Repository to view the external repository at
%USERPROFILE%\.skillManager\skills.
- Select one or more skills, then use the view actions to copy them in either direction, delete them, or refresh the view.
- When a destination already contains a skill, confirm whether it should be overwritten.
Both views refresh when files change externally. Missing skill directories are shown as empty until they are created. The local repository is not bundled with this extension; the intentionally deleted skills-database is not recreated.
Settings
Configure these settings in VS Code settings or the workspace .vscode/settings.json:
| Setting |
Default |
Purpose |
skillManager.projectSkillsPath |
.github/skills |
Project skill directory. Relative paths resolve from the first workspace folder. |
skillManager.localRepositoryPath |
${userHome}\\.skillManager\\skills |
External local skill repository. ${userHome} resolves to the current user's home directory. |
Both paths are required and cannot be blank.
Commands
- Skill Manager: Refresh refreshes both views.
- Skill Manager: Delete Selected Skills removes the selected skill directories from the active view.
- Skill Manager: Copy Selected Skills to Local copies selected project skills to the local repository.
- Skill Manager: Copy Selected Skills to Project copies selected local skills to the project.
Development
Install dependencies, compile the extension, and run the tests:
npm install
npm run compile
npm test
The extension entry point is src/extension.ts. Compiled extension code is written to out/; test output is written to .test-out/.
Packaging a VSIX
The package uses @vscode/vsce as a development dependency. After npm install, create a VSIX with:
npm run package
This compiles the extension and runs vsce package. .vscodeignore excludes TypeScript source, compiled tests, plan files, configuration, source maps, and other development files while retaining out/, package.json, package-lock.json when present, and this README.
Install the generated .vsix in VS Code with Extensions: Install from VSIX.... Acceptance testing should verify the project/local copy workflow, overwrite confirmation, deletion, and refresh after external edits on Windows 10 or later.
Scope boundaries
- The project repository and the external local repository are the only skill sources.
- Git operations remain outside the extension and are controlled by the user.
- Remote skill support is a future TODO; there are no remote commands or services in this extension.
