This skills bundle has been generated using 'A-Skills'.
- Name: 'A-Skills'.
- Purpose: Enforcing agent skills in a windowed sandbox.
- Format: Docker Container / Agent Skills framework.
- License:
- This project's license: GNU General Public License v3.0
- Bundled skills:
- 'style': answer length, text formatting, comments, references,
CHANGELOG.mdandCODEOWNERSconventions. - 'ops': naming notation, Terraform and Python conventions.
- 'obsidian': Obsidian Markdown conventions.
- 'style': answer length, text formatting, comments, references,
- Two container images: GitHub Copilot and Claude Code, each with Visual Studio Code, the desktop app and the CLI.
- Hardened container: runs with
--cap-drop=ALLandno-new-privileges, with only the selected folders mounted.--userns=keep-idmaps the container's 'agent' user to the host user, so root inside the container is not root on the host.- Only the chosen folders are mounted, and
/run/user/1000is an in-memorytmpfsthat disappears with the container. --security-opt label=disableturns off SELinux labelling, because the default labels block the Wayland socket and/dev/dri, which the window needs. The isolation above still applies.
- Native Wayland window passthrough, without X11.
- Optional microphone passthrough via the host's PipeWire/PulseAudio socket, for voice input, per Dockerfiles/README.md.
- Pre-configured Visual Studio Code settings, documented in SETTINGS.md.
- None (Any OS, no isolation)
- Gnome Boxes/VM (Linux, full isolation)
- Podman/Container (Linux, full isolation)
Note: The images are Linux containers only, on both Linux and Windows hosts. GUI passthrough is not possible in native Windows containers by design (Windows-Containers #306).
- clone the repository duh
- (optionally) rename the folder to
.githubor.claudeor.agents, depending on the harness, per documentation by GitHub.- e.g. Claude Code only loads skills natively from the
.claude/skillsdirectory. They still work just fine through theAGENTS.mdinstructions.
- e.g. Claude Code only loads skills natively from the
- (optionally) adjust Visual Studio Code settings per the
settings.jsonsnippet (pre-loaded automatically for the container-sandboxed agent).- these settings are overwritten by the user-specific
settings.jsonfile synchronised from the logged-in user!
- these settings are overwritten by the user-specific
- (optionally) install Gnome Boxes (e.g. Flathub)
- (optionally) install Podman Desktop (e.g. Flathub)
- check whether the Podman socket is running
systemctl --user enable podman.socketsystemctl --user start podman.socketsystemctl status --user podman.socket- if the socket is dead, see Troubleshooting.
- build the image using Podman with
Dockerfiles/as the context directory.# Replace 'Copilot' with 'Claude' for the Claude Code image podman build -f Dockerfiles/Copilot/askillsAgent.dockerfile \ -t docker.io/library/askillsagent Dockerfiles/ - run the image using the
podman runcommand from Dockerfiles/README.md. - share files with the agent by placing them in the host's
$HOME/askillsagentdirectory, which is mounted as/workspaces/main-workspaceinside the container.
- check whether the Podman socket is running
AGENTS.md tells the agent which skill to apply and when, while CLAUDE.md imports it for Claude Code. Each SKILL.md holds the general rules and points to its extension files, which the agent reads only when the task requires them.
To add a custom skill, create a new folder under .github/skills/ with a SKILL.md file (with name and description in its frontmatter), then reference it in AGENTS.md.
The skills can be used in one of the following modes:
- 'no isolation'
- In this mode the skills in this repository can be used as-is and the agents roam free across the entire host operating system, performing the magic of
rmor the like on random files π
- In this mode the skills in this repository can be used as-is and the agents roam free across the entire host operating system, performing the magic of
- Gnome Boxes
- In this mode the skills in this repository can be used inside a VM. Gnome Boxes offers the majority of Linux distributions in a drop-down list. The operator can select which files on the host are shared with the guest OS. This is not a very performant setup, as there are significant lag and I/O issues when operating inside the guest OS's VSC and CLIs. Mostly a 'click-ops' type of setup.
- The setup of the VM is on the Operator. This repository does not cover it.
- This option supports simple host-mirrored configuration of the IDE and support software, along with compatibility with immutable distributions and Flatpaks.
- Podman (container)
- In this mode the skills in this repository can be used inside a container. Podman may build one of the included
.dockerfileimages:- GitHub Copilot: Visual Studio Code with the GitHub Copilot extension, the GitHub Copilot App and the GitHub Copilot CLI.
- Claude Code: Visual Studio Code with the Claude Code extension, the Claude Desktop App and the Claude Code CLI.
- This is most likely the ideal solution, as folders can be mounted directly to the container, while leveraging the native Wayland display server. The concept offers supreme convenience at low risk.
- This mode supports multiple entrypoints:
- GitHub Copilot:
copilot-vsc,copilot-app,copilot-cli,browser,terminal. - Claude Code:
claude-vsc,claude-app,claude-cli,browser,terminal.
- GitHub Copilot:
- In this mode the skills in this repository can be used inside a container. Podman may build one of the included
.
βββ .github
β βββ skills
β β βββ obsidian # Obsidian Markdown conventions
β β βββ ops # Naming notation, Terraform, Python
β β βββ style # General styling rules
β βββ CHANGELOG_TEMPLATE # Template for CHANGELOG.md
β βββ CODEOWNERS_TEMPLATE # Template for CODEOWNERS
β βββ PULL_REQUEST_TEMPLATE # Templates for pull requests
β βββ pull_request_template.md # Default pull request template
βββ Dockerfiles
β βββ Claude # Claude Code image and entrypoint
β βββ Copilot # GitHub Copilot image and entrypoint
β βββ PROMPTS.md # Prompts for maintaining the settings files
β βββ SETTINGS.md # Visual Studio Code settings reference
β βββ vsc-claude.json # Pre-loaded Claude Code settings
β βββ vsc-settings.json # Pre-loaded Visual Studio Code settings
βββ AGENTS.md # Skill workflow for all agents
βββ CLAUDE.md # Imports AGENTS.md for Claude Code
βββ TO-DO.md # Planned work, as user stories
Visual Studio Code instance before logging in, right after provisioning.
A Visual Studio Code instance after logging in, with user's settings.json.
socket unresponsive
- the command starts Podman Desktop (Flatpak) in CLI mode with an
lscommand to read the socket; thespawncommand creates a test Podman process. -
flatpak run --command=sh io.podman_desktop.PodmanDesktop -c \ 'ls -l $XDG_RUNTIME_DIR/podman/; flatpak-spawn --host podman --version' - test if there are any stale connections using
podman system connection list - if nothing seems wrong, then congrats. Perhaps, like me, you managed to spawn so many processes on the OS that the system has random issues. I occasionally experience this in GitKraken's "file watching failed to start for this repository" error, but also in Gnome system monitor's "Unable to find default local file monitor type".
- close some VSC instances or browser windows, or restart the host. Essentially increase
fs.inotify.max_user_watchesandfs.inotify.max_user_instances, per my article.