Dotnet Debugging
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
Operate Devsy workspaces and providers for end users. An agent skill from devsy-org/devsy.
Install Devsy
$ npx skills add devsy-org/devsy --skill devsy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install devsy-org/devsy devsy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/devsy .claude/skills/devsy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .claude/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add devsy-org/devsy --skill devsy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install devsy-org/devsy devsy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/devsy .agents/skills/devsy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .agents/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add devsy-org/devsy --skill devsy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install devsy-org/devsy devsy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/devsy .cursor/skills/devsy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .cursor/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/devsy-org/devsy.git --path .agents/skills/devsy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add devsy-org/devsy --skill devsy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install devsy-org/devsy devsy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/devsy .gemini/skills/devsy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .gemini/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install devsy-org/devsy devsyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add devsy-org/devsy --skill devsy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/devsy .github/skills/devsy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .github/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add devsy-org/devsy --skill devsy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install devsy-org/devsy devsy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devsy-org/devsy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/devsy .opencode/skills/devsy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "devsy" agent skill from https://github.com/devsy-org/devsy/tree/main/.agents/skills/devsy into .opencode/skills/devsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devsy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
devsy- GitHub stars
- 109
- Token cost
- ~1.7k tokens
- SKILL.md length
- 788 words
- Files
- 7 (incl. references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Operate Devsy workspaces and providers for end users. An agent skill from devsy-org/devsy.
- Run commands in Devsy workspaces
- SKILL.md covers Choose the interface, Discover and select a workspace, Create and resume and Execute commands, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Configure providers
What it does
Devsy is an agent skill from devsy-org/devsy. Operate Devsy workspaces and providers for end users. Use to discover, create, resume, stop, delete, troubleshoot, or run commands in Devsy workspaces, and configure providers. Not for developing Devsy itself. Prefer Devsy MCP tools and use the CLI for additional operations or when MCP is unavailable.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/cli.md`, `references/mcp-tools.md` and `references/providers.md`). Compatibility notes: Requires Devsy installed on the controlling host and access to Devsy MCP via devsy mcp serve or shell access to the devsy CLI. Workspace execution also…
It sits in DevOps & Cloud, covering MCP servers and Containers. It works with Model Context Protocol, Docker, Kubernetes and Visual Studio Code. The repository describes itself as: Deploy secure local and cloud environments for developers and agents. The licence is MPL-2.0.
When your agent uses it
- Run commands in Devsy workspaces
- Configure providers
Example prompts
- “/devsy”
Requirements
- Docker
- Compatibility (from SKILL.md): Requires Devsy installed on the controlling host and access to Devsy MCP via devsy mcp serve or shell access to the devsy CLI. Workspace execution also requires a supported container runtime and a running workspace.
What it can do on your machine
Read from SKILL.md and the folder at commit 81bd40e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
devsy.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Devsy installed on the controlling host and access to Devsy MCP via devsy mcp serve or shell access to the devsy CLI. Workspace execution also requires a supported container runtime and a running workspace.
From compatibility in the SKILL.md frontmatter.
Context cost
Devsy loads about 1.7k tokens when it runs, and up to ~7.8k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 788 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from devsy-org/devsy at commit 81bd40e, republished under its MPL-2.0 licence (© devsy-org). 788 words, ~1,659 tokens.
Download SKILL.mdSave it as
.claude/skills/devsy/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- devsy
- description
- Operate Devsy workspaces and providers for end users. Use to discover, create, resume, stop, delete, troubleshoot, or run commands in Devsy workspaces, and configure providers. Not for developing Devsy itself. Prefer Devsy MCP tools and use the CLI for additional operations or when MCP is unavailable.
- compatibility
- Requires Devsy installed on the controlling host and access to Devsy MCP via devsy mcp serve or shell access to the devsy CLI. Workspace execution also requires a supported container runtime and a running workspace.
- license
- MPL-2.0
- metadata.author
- devsy-org
- metadata.product
- devsy
Devsy
Operate Devsy workspaces and providers on behalf of an end user. This skill is
not the contributor guide for changing Devsy itself; for source-development
tasks follow the repository's AGENTS.md and normal development instructions.
Choose the interface
Use the available Devsy MCP tool when it supports the requested operation. Client tool names may have a server prefix; discover the actual tools rather than assuming they are connected. Use the Devsy CLI for capabilities MCP does not expose, or as fallback when MCP is unavailable and shell access exists. If neither interface is available, report the missing prerequisite and link to Devsy MCP setup. Installing this skill does not install Devsy or configure MCP.
Keep the same Devsy context, provider, and owner scope when switching interfaces. Do not silently replace Devsy operations with direct Docker, Kubernetes, or cloud mutations. Devsy owns workspace state; low-level provider diagnosis needs appropriate user authority and a reason the Devsy diagnostics are insufficient.
Discover and select a workspace
- When identity is uncertain, call
workspace_listand use a returned name. Match an explicit user name first, then source/project when unambiguous. - Reuse an existing suitable workspace when consistent with the request. An explicit request for another isolated workspace should get a distinct name.
- Inspect saved configuration with
workspace_status. Its current result is configuration, not live running state. When running state matters, usedevsy workspace status <name> --result-format jsonorworkspace describethrough the CLI. Existence does not imply the container is running. - Resolve multiple matching candidates before mutating one.
Create and resume
Before creating, list workspaces, determine the source, and consider reuse.
workspace_create accepts a Git URL, absolute host-local path, container image,
or canonical source returned by workspace_list. A local path belongs to the
host running Devsy, not necessarily the agent's remote filesystem.
If provider selection matters, call provider_list and use the configured name.
Otherwise allow the context's default provider. Add a provider only when setup
is part of the user's request; do not change the global default just to select
one provider for one workspace. Creation starts the workspace. Use its returned
configuration and identity for subsequent work. Use workspace_start to resume
an existing workspace, after discovery where needed.
Create timeout recovery
A client timeout does not prove server-side creation stopped. Do not blindly
retry creation, switch to CLI creation, or pick a second name. Check
workspace_status for the expected name, or workspace_list if the name is
uncertain. A newly visible configuration does not by itself prove setup finished;
check live state and operation diagnostics when needed. Use bounded checks
appropriate to the active task. A single not-found result can race creation;
retry only after evidence establishes that the original operation failed or
ended without creating the workspace. Report an unresolved outcome instead of
creating duplicate infrastructure.
Show full SKILL.md (328 more words)Show less
Execute commands
Ensure the workspace is started. workspace_exec.command is an argv array:
{"name":"my-workspace","command":["npm","test"]}Use a shell only for shell features such as pipes, redirection, expansion, or chaining, and only when that shell exists in the workspace:
{"name":"my-workspace","command":["sh","-c","npm test && npm run lint"]}Separate direct argv calls are also suitable for sequential commands. Determine
test/build commands from the project or user request; do not guess a package
manager. workdir is a container path and env maps strings to strings.
Check tool errors and the optional error payload as well as exit_code,
stdout, and stderr. timed_out means an execution timeout, not a normal
process exit; truncated means captured output is incomplete; clamped means
the requested timeout was shortened. Do not automatically rerun a command with
side effects after timeout or incomplete output. Defaults are 5 minutes per
exec, a 30-minute maximum, 100 KiB per output stream, and 8 concurrent
create/start/exec operations per server; server flags can change these limits.
Stop, delete, and configure providers
Stopping compute uses workspace_stop; deletion removes workspace resources.
Do not interpret restart, refresh, fix, or vague cleanup as deletion authority.
For deletion or reset, establish unambiguous intent and target. Explicit deletion
can proceed within that authority without repeated confirmation. Do not default
to force=true: forced cleanup can leave provider resources behind and, for
imported workspaces, can also enable remote deletion otherwise skipped.
Provider deletion affects shared configuration and may be refused while
workspaces use it. Do not delete a provider to repair one workspace. Treat
provider_use as a default change for subsequent creates, not a per-workspace
selection. Commands executed inside a workspace can themselves be destructive;
assess their effects, not just the tool name.
References
Read only the reference relevant to the task:
- MCP tool contract — inputs, results, limits, and errors.
- Workspace workflows — discovery, creation, resume, execution, stop, delete, recreate/reset.
- CLI fallback and extended capabilities — structured output, diagnostics, and CLI-only operations.
- Provider workflows — provider selection and configuration.
- Safety and authority — destructive actions, credentials, and repository content.
- Troubleshooting — timeouts, partial output, and unavailable interfaces.
© devsy-org, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in .agents/skills/devsy of devsy-org/devsy.
- SKILL.md
- references/cli.md
- references/mcp-tools.md
- references/providers.md
- references/safety.md
- references/troubleshooting.md
- references/workspace-workflows.md
Open the folder on GitHubat commit 81bd40e
Compare with similar skills
Devsy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Devsy this skilldevsy-org/devsy | 109 | — | ~1.7k | Automated safety check: Pass | MPL-2.0 | |
| Dotnet Debuggingnovotnyllc/dotnet-artisan | 233 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Oneclickvirtoneclickvirt/oneclickvirt | 372 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Unraiddinglebear-ai/unraid | 135 | — | ~5.4k | Automated safety check: Notes | MIT | |
| Pluggedin Stack OpsVeriTeknik/pluggedin-app | 103 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Skillz Integrationgithub/gh-aw | 5.3k | — | ~905 | Automated safety check: Pass | MIT |
Similar skills
Oneclickvirt
oneclickvirt/oneclickvirt
OneClickVirt operations skill for managing containers, virtual machines, provider nodes, health checks, and metrics through MCP.
Unraid
dinglebear-ai/unraid
This skill should be used when the user mentions Unraid, asks to check server health, monitor array or disk status, list or restart Docker containers, start or stop VMs, read system logs, check…
Pluggedin Stack Ops
VeriTeknik/pluggedin-app
A skill your agent uses when deploying, restarting, verifying or rolling back the containerised plugged.in production stack, when the site returns 404 or 5xx after a deploy or git operation, or when…
- Official
Skillz Integration
github/gh-aw
Run and integrate Skillz MCP server with Docker for skill execution.
- Official
.NET Crash Dump Collection
dotnet/skills
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
Related
Categories
Questions about Devsy
What does Devsy do?
Operate Devsy workspaces and providers for end users. An agent skill from devsy-org/devsy. Devsy is an agent skill from devsy-org/devsy. Operate Devsy workspaces and providers for end users.
When should I use Devsy?
Devsy fits situations like: run commands in Devsy workspaces; configure providers.
How do I install Devsy in Claude Code?
Run `npx skills add devsy-org/devsy --skill devsy -a claude-code`. Or copy the skill folder (.agents/skills/devsy in devsy-org/devsy) into .claude/skills/devsy in your project. Claude Code loads it when a task matches its description.
How do I install Devsy in Codex?
Run `npx skills add devsy-org/devsy --skill devsy -a codex`. Or copy the skill folder (.agents/skills/devsy in devsy-org/devsy) into .agents/skills/devsy in your project. Codex loads it when a task matches its description.
Can I use Devsy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add devsy-org/devsy --skill devsy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devsy, .gemini/skills/devsy, .github/skills/devsy and .opencode/skills/devsy in your project.
What does Devsy need to run?
SKILL.md names no scripts, command-line tools or credentials: Devsy is instructions for the agent only. Our summary lists: Docker. Compatibility (from SKILL.md): Requires Devsy installed on the controlling host and access to Devsy MCP via devsy mcp serve or shell access to the devsy CLI. Workspace execution also requires a supported container runtime and a running workspace..
Does Devsy access the network?
SKILL.md names 1 domain. As links in the text: devsy.sh. This is read from the text; nothing was executed.
Is Devsy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Devsy use?
Devsy is published under the MPL-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Devsy use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.
What are the alternatives to Devsy?
Skills that share tags, products or a category with Devsy: Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars), Oneclickvirt (oneclickvirt/oneclickvirt, 372 stars), Unraid (dinglebear-ai/unraid, 135 stars) and Pluggedin Stack Ops (VeriTeknik/pluggedin-app, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Devsy?
devsy-org (a GitHub organization) maintains it in devsy-org/devsy, which has 109 GitHub stars. The repository was last updated on October 7, 2026.
Source: devsy-org/devsy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.