ai-tools-setup
Skill from wonderwhy-er/DesktopCommanderMCP
Install
npx skills add wonderwhy-er/DesktopCommanderMCP --skill ai-tools-setup
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install desktop-commander@desktop-commander
This skill is part of the plugin “desktop-commander”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the ai-tools-setup skill do?
Description from the SKILL.md in the source repository.
Questions about ai-tools-setup
What does the ai-tools-setup skill do?
Set up, connect, validate, and repair Claude Desktop and MCP servers using Desktop Commander — inspecting and fixing mcp.json / claude_desktop_config.json, getting MCP servers to connect, and diagnosing local AI tooling. Use when a user wants to install, configure, connect, validate, or fix Claude Desktop, an MCP server, an MCP config file, or a local AI agent/gateway. Trigger on the symptoms that actually bring people in: "Claude can't see my tools", "my MCP server isn't showing up", "tools aren't loading in Claude", "add an MCP server", "my MCP isn't connecting", "fix my Claude Desktop config", "the agent won't respond", "wire up Ollama / LM Studio", "restart Claude Desktop". Also covers local agent gateways like OpenClaw and Hermes.
How do I install ai-tools-setup?
In a terminal: npx skills add wonderwhy-er/DesktopCommanderMCP --skill ai-tools-setup. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use ai-tools-setup?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is ai-tools-setup safe to use?
Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.
More skills from wonderwhy-er/DesktopCommanderMCP
Run a comprehensive, read-only health check on the user's computer and return a scored chat summary with prioritized, plain-English recommendations and safe cleanup suggestions.
Use for Desktop Commander MCP capabilities — persistent shells and REPLs, long-running processes, filesystem beyond the workspace, structured files (.xlsx, .docx, .pdf, images) and large local data files such as CSVs, ripgrep …
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes …
Organize Obsidian vaults with MOCs, wikilinks, frontmatter/properties, dashboards, orphan-note checks, and cleanup workflows.
Use Desktop Commander for terminal and command-line work, especially anything that needs a shell whose state persists across turns: Python/Node REPLs, database shells, dev servers and other long-running processes, SSH into remote …
Related skills in Agents & Workflows
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in …
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Teach the user a new skill or concept, within this workspace.
No description in the SKILL.md.
No description in the SKILL.md.
Ask which skill or flow fits your situation. A router over the skills in this repo.
No description in the SKILL.md.
Router for all Remotion skills