Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Agent Skills are portable instruction bundles: each skill is a directory with a SKILL.md file at its root, plus any supporting resources. To use one, place that directory in the project or global skills folder recognized by your coding assistant, install it through a supported plugin or CLI, then start a task that matches the skill. Codex, Claude Code, Cursor, GitHub Copilot, and Gemini CLI use different discovery folders, so copying a skill into the wrong client directory is the most common installation error.
The reliable workflow is: choose project or global scope, install the complete skill directory (not the parent skills folder), restart the client if it was already open, and test it with a task the skill is designed to handle. Skills themselves are static files; Microsoft says no authentication is required to use them, although a skill that links to online documentation still needs network access.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What is an Agent Skill, and what does it change in a coding assistant?
An Agent Skill is a self-contained set of instructions and resources that an AI coding assistant can load when a request matches its purpose. The root of the bundle contains SKILL.md; additional files can provide examples, scripts, templates, or reference material. The format is designed to be portable rather than tied to one editor.
Compatible assistants generally discover skills automatically. You do not normally invoke a skill by typing its filename. Instead, describe the job in ordinary language. If the request matches the skill’s stated scope, the assistant may load the instructions and follow their workflow. Discovery is client-dependent, so a successful file copy does not by itself prove that a skill was loaded.
#1 Best Overall
- 🎙️ Hands-Free Voice Typing for Windows & Mac – Powered by iOS & Android dictation technology, AI VoiceWriter allows fast, accurate speech-to-text directly on your desktop. Simply speak, and your words appear in real time. Compatible with Windows 10 & above, macOS 13 & above.
- ✍️ AI Writing Assistant for Effortless Editing – Boost productivity with AI proofreading, rephrasing, and formatting. Perfect for emails, reports, creative writing, and professional content.
- 💻 Works Seamlessly in Any Desktop App – Type with your voice in Microsoft Word, Google Docs, PowerPoint, Teams, emails, and more. Just place your cursor in any text field and start speaking!
- 📱 Mobile App for Enhanced Voice Input – The AI VoiceWriter mobile app enhances voice recognition by using your phone’s microphone as an input device for clearer, more accurate dictation—while typing on your desktop. Supports iOS 15 & above, Android 9.0 & above.
- 🌎 Multilingual Voice Typing & AI Assistance – Supports 33 languages for dictation, plus AI-powered features in Chinese, English, Japanese, Korean, French, German, Spanish, Italian and, Swedish.
Skills are static files, not accounts or hosted services. The Microsoft Learn guide notes that no authentication is required to use the skill files themselves. A skill may still direct the assistant to consult online documentation, call a service, or run a local command; those actions can require network access, credentials, or separate tools.
Read the skill before installing it. Treat SKILL.md and any scripts as executable guidance: check what files it reads, what commands it suggests, and whether it asks the assistant to send data outside your project.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Which installation method should you use?
Use a project installation when the instructions belong to one repository and should travel with that codebase. Use a global installation for personal defaults that should be available in many projects. A plugin or CLI is easier to update; a manual copy gives you the clearest review and version control.
| Method | Best for | Scope and control |
|---|---|---|
| Manual directory copy | Audited, pinned files or private forks | Project or global; you review every file and update it yourself |
| Plugin marketplace | Codex or Claude Code users who want managed discovery | Installed through the client; updates follow marketplace/plugin behavior |
| NVIDIA skills CLI | Interactive or scripted installs targeted at a specific agent | Can select a skill, agent, and later run update/list/check commands |
| GitHub CLI | Installing from a GitHub repository or local directory | Uses host-specific project or user locations supported by the selected agent |
Check that the chosen client supports the skill format and the installation route. Microsoft’s compatibility guidance covers the directory approach and lists the main client locations; the Microsoft Learn Agent Skills guide is the reference for those paths.
How do I install a skill manually in the correct directory?
Manual installation works across clients when you preserve the skill’s directory structure. Copy each individual skill folder from a repository’s skills/ directory into the destination, not the parent skills directory itself.
1. Obtain and inspect the skill
- Get the repository or local directory that contains the skill collection.
- Open the selected skill folder and confirm that
SKILL.mdis directly inside it. Supporting files should remain in their relative locations. - Read the instructions and inspect scripts before making them available to an assistant. Pin or record the version if you need repeatable builds.
2. Choose project or global scope
Project scope keeps the skill with one codebase and allows a team to review it. Global scope makes it available across projects for your user account. If both scopes contain similarly named skills, prefer the project copy when the client documents that behavior, and remove ambiguity by keeping only the version you intend to use.
3. Copy the individual skill folder
Place the complete folder, including SKILL.md and its resources, in the client-specific directory below. Do not flatten the files or copy only SKILL.md; either change can prevent discovery or break relative references.
| Assistant | Project directory | Global directory |
|---|---|---|
| GitHub Copilot | {project}/.github/skills/ |
~/.copilot/skills/ |
| Claude Code | {project}/.claude/skills/ |
~/.claude/skills/ |
| Codex CLI | {project}/.codex/skills/ |
~/.codex/skills/ |
| Cursor | {project}/.cursor/skills/ |
|
| Gemini CLI | {project}/.gemini/skills/ |
The braces in the table represent your actual project directory; they are not literal characters to create. The Microsoft guide lists these locations and notes that discovery rules can change, so check the client’s current documentation if a path is ignored.
4. Restart or reload the client
Many coding agents scan skills when a session or editor starts. Close and reopen the terminal, editor, or assistant after copying a new skill. If the client provides a reload command, use it; otherwise a full restart is the dependable fallback.
How do I install Agent Skills through the Codex plugin marketplace?
Codex can install the Microsoft Agent Skills package through its plugin marketplace. This route avoids manually placing folders and gives Codex a managed plugin entry.
Free tools Windows power users keep installed
One-click scans. No signup required.
- In a Codex session, run
codex plugin marketplace add MicrosoftDocs/agent-skills. - Open the plugin browser with
/plugins. - Find the
microsoft-agent-skillsmarketplace and installazure-agent-skills. - Restart Codex if the skills do not appear immediately.
The commands and package names are documented in the Agent-Skills README. A marketplace install can be convenient for a team already using Codex plugins, but review the plugin’s contents and update behavior before enabling it in a sensitive repository.
How do I install Agent Skills in Claude Code with a plugin?
Claude Code has a corresponding marketplace flow. The plugin commands are separate from Codex’s commands, so do not substitute codex for the Claude Code command names.
- Run
/plugin marketplace add MicrosoftDocs/agent-skillsinside Claude Code. - Install the package with
/plugin install azure-agent-skills@microsoft-agent-skills. - Run
/reload-plugins, or restart Claude Code if the new skills are still missing.
The same README documents this sequence. Plugin commands can change with client releases; if a command is rejected, use the manual directory route and the client’s current plugin help.
How do I use NVIDIA’s skills CLI to install and maintain a skill?
The NVIDIA repository documents an interactive installer that can target a particular assistant. Use the latest CLI form when you want the current release.
Recommended Free Tools
Interactive installation
From a terminal, run:
npx skills add nvidia/skillsThe installer prompts you to choose from the available skills and destinations. This is useful when you are exploring a collection and want the CLI to handle the host-specific location.
Non-interactive installation
To select one skill and accept the prompts automatically, add --skill <name> --yes. To target a client, add an agent option such as --agent codex, --agent claude-code, or --agent cursor. A typical pattern is:
npx skills@latest add nvidia/skills --skill <name> --agent codex --yesReplace the angle-bracketed value with the exact skill name shown by the installer; it is a command argument, not a folder you should create. The repository supports other agent values as well, so use the one matching your client.
Maintenance commands
After installation, the CLI provides these maintenance operations:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →npx skills updateupdates installed skills.npx skills listshows the skills the CLI knows about.npx skills checkchecks the installation state.
The NVIDIA Agent Skills repository recommends using a current CLI. If a scripted build must be reproducible, record the selected skill and version rather than updating blindly.
Can GitHub CLI install a skill for my coding assistant?
Yes. GitHub CLI provides gh skill install for a GitHub repository or a local directory. The general syntax is:
gh skill install <repository> [<skill[@version]>]Use the repository argument for the source and optionally identify a skill or version. GitHub’s manual says the command installs into a host-specific project or user directory and supports Codex, Claude Code, Cursor, Gemini CLI, and many other agents.
Because the destination depends on the selected host and scope, verify the resulting directory after the command completes. The authoritative syntax and supported-agent list are in the GitHub CLI manual.
How do I run a skill after installation?
Start a normal coding-assistant request that clearly matches the skill’s domain. For example, if a skill describes a repository-documentation workflow, ask the assistant to perform that workflow in the project rather than asking it to “run skill-name.” Compatible assistants are expected to discover relevant skills and load them when the request matches.
- Open the project at the scope where you installed the skill.
- Describe the desired task, constraints, inputs, and expected output in ordinary language.
- Refer to the skill’s documented workflow when precision matters, such as required files, commands, or review steps.
- Inspect the assistant’s response and changes. Confirm that it followed the skill’s instructions instead of assuming that a matching filename proves activation.
Do not claim that a skill ran merely because it is present on disk. Microsoft’s guidance treats automatic discovery as client behavior; the practical test is a domain-specific request and observable adherence to the skill’s workflow. Some clients may expose loaded-context details, while others only show the resulting actions.
How can I verify that the assistant discovered the skill?
Verification has two parts: file placement and behavioral evidence.
Check the files
- Confirm the expected project or global directory exists for the client.
- Confirm the copied item is an individual skill folder.
- Confirm
SKILL.mdis at that folder’s root, not one level deeper. - Confirm supporting files and relative paths are intact.
- If you used a CLI, run its list or check command where available.
Check the client session
- Restart the editor or terminal after installation.
- Open the same project whose directory contains the project-scoped skill.
- Ask for a task that is specific to the skill and requires one of its documented steps.
- Compare the response with the skill’s instructions and inspect any generated files or commands.
Google’s coding-agent documentation also pairs skills checks with client setup and recommends restarting when a client loads skills only at startup. Its guidance is available at Google’s coding-agent documentation.
Why is my skill not being detected?
Most failures are caused by a path, structure, scope, or session problem. Work through these branches in order.
The folder is in the wrong place
Compare the directory with the table above. A Codex skill in ~/.claude/skills/ will not automatically become a Claude Code skill merely because both clients use the same SKILL.md format. Move or copy the individual skill folder into the target assistant’s project or global directory.
The parent directory was copied
If the path looks like .codex/skills/skills/my-skill/SKILL.md, you copied the collection’s parent folder. The expected shape is .codex/skills/my-skill/SKILL.md. Remove the extra nesting and preserve the skill folder as one unit.
The file is not at the root
A structure such as my-skill/docs/SKILL.md may not satisfy a client that expects the manifest at the skill directory root. Move the complete, correctly structured folder from the source repository rather than rebuilding it by hand.
The client started before installation
Close and reopen the editor, terminal, or assistant. For Claude Code, use /reload-plugins after plugin installation; for Codex, restart if the marketplace package does not appear.
Global and project scopes conflict
Install in the project root when a global skill is ignored or when the project needs a known version. Remove duplicate copies with the same purpose so you can tell which instructions the client is using.
The skill depends on online material
Static skill files do not require authentication, but instructions that reference online documentation require network access. Check connectivity and any corporate proxy policy before treating a network failure as a discovery failure.
The client or route is unsupported
Check whether your assistant supports Agent Skills and the chosen installation method. If a plugin command or CLI agent value is rejected, use the documented directory path for that client or consult its current help. Compatibility and discovery behavior can change between client releases.
How should teams manage versions and security?
Keep project-scoped skills under the same review process as code. Record the repository revision or package version, review changes to SKILL.md, and inspect scripts before allowing an assistant to execute them. A CLI’s update command is convenient, but automatic updates can silently change behavior; pin versions when reproducibility is more important than receiving new instructions immediately.
Global skills are useful for personal conventions but can create hidden dependencies: another developer may not have the same files, and a project may behave differently on a machine with a newer global copy. For shared work, prefer a project installation or document the exact global setup. Keep secrets out of skill files and follow the assistant’s permission prompts for commands, network access, and file changes.
When a skill instructs an assistant to use external documentation, verify the destination and the data being sent. Network availability is a runtime requirement for that instruction, not a requirement for reading the local SKILL.md.
What is the practical installation checklist?
- Choose project scope for repository-specific behavior; choose global scope for personal defaults.
- Confirm the skill folder contains a root-level
SKILL.md. - Copy individual folders from the source collection, not the parent
skillsfolder. - Use the exact client path:
.github/skills,.claude/skills,.codex/skills,.cursor/skills, or.gemini/skills. - For Codex or Claude Code, follow the marketplace commands and restart or reload when required.
- For CLI installation, use the agent selector and record the selected skill/version.
- Restart the client and open the project at the same scope where the skill was installed.
- Test with a task that genuinely matches the skill, then inspect the assistant’s behavior and file changes.
- If detection fails, check nesting, scope conflicts, network requirements, and client support before reinstalling.
Frequently Asked Questions
Do Agent Skills work without an internet connection?
The local skill files can be used without authentication, but an offline session cannot follow instructions that require fetching online documentation or contacting a remote service. Read the skill’s dependencies and provide network access only when those steps are necessary.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteShould I install a skill globally or inside the repository?
Use a project directory when the team needs a predictable, reviewable version tied to that codebase. Use a global directory for personal conventions that should follow you across repositories, and document the setup if others must reproduce it.
Can the same skill be used by different coding assistants?
A portable skill can be shared when each client supports the directory format and discovery rules, but the destination folders are client-specific. Install the same individual skill folder into each assistant’s recognized location and verify behavior separately.
How do I stop an outdated skill from affecting a project?
Remove or move the old project or global copy, then restart the client so its discovery cache is refreshed. If the skill came from a CLI or plugin, use that tool’s list or uninstall facility and check that no duplicate folder remains.
What should I do if the assistant follows only part of the skill?
First compare the request with the skill’s stated trigger and required inputs; a partial match may load only relevant guidance. Then provide the missing context explicitly, restart the client, and test a small task whose expected steps are unambiguous.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
