This skills bundle has been generated using 'A-Skills'.
A-Skills is an agent system, which doubles as an interface to the 'a-mcorp' repositories. It was designed to provide a sandboxed container allowing the user to either elevate their own skills or study LLMs in live production scenarios. The assistant enhances the user's own knowledge and skills, rather than replacing them.
I do strongly emphasise the last part
Its skills define how an assistant writes, names, comments and contributes, and its container images give that assistant a ready, sandboxed workspace. Together, they describe how my repositories are designed and how to contribute to them.
If you ever wish to contribute to my 'emporium', simply load 'A-Skills', open a repository, and the assistant follows the (almost) same conventions as the projects' Maintainer.
- Name: 'A-Skills'.
- Purpose: An agent system and contribution interface for the 'a-mcorp' repositories - skills, container images and their configuration.
- Format: Agent Skills framework / Docker Container.
- License:
- This project's license: GNU Affero General Public License v3.0, with additional terms (attribution, name) in NOTICE; Copyright © 2026 Mateusz Adamczyk (M.A.)
| Features | ||
|---|---|---|
|
||
| Podman, before logging in | Copilot, with the user's settings.json |
Claude Code, with the user's settings.json |
| Dependencies | Usage |
|---|---|
|
To add a custom skill, create a new folder under The skills can be used in one of the following modes:
|
- 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
.
├── .github
│ ├── skills
│ │ ├── hardware # Dimensions, bills of materials, 3D printing, photos
│ │ ├── obsidian # Obsidian Markdown conventions
│ │ ├── ops # Naming notation, Terraform, Python
│ │ └── style # General styling and contributing 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, its hardware 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
├── docs # Documentation assets (screenshots)
├── AGENTS.md # Skill workflow for all agents
├── CLAUDE.md # Imports AGENTS.md for Claude Code
├── LICENSE # AGPL-3.0
├── NOTICE # Copyright and the additional terms (attribution, name)
└── TO-DO.md # Planned work, as user stories
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.