arm-software - Check that we were told which Vulkan extension we are supposed to check. If this was not specified, ask.
- If you are not familiar with the extension, download the version summary from
https://docs.vulkan.org/refpages/latest/refpages/source/<version>.html, whereversionis the version in the formVK_VERSION_<major>_<minor>, for exampleVK_VERSION_1_4for version 1.4. - For each new command, check if we have an existing hardcoded KHR or EXT suffixed version of this
command, and are missing a forward from a promoted command (ie without the suffix). Check the two
files
src/hardcoded_read.cpp(for replay) andsrc/harcoded_write.cpp(for capture). Also check the filescripts/vkconfig.pyfor extension variants that are similarly missing a promoted variant. - As above, for each new structure defined, check if we have an existing hardcoded KHR or EXT suffixed version of it and are missing handling of the promoted variant. Look in the same files as for commands.
- Check that our feature pruning code handles this version of the standard. This is tracked within the
tracking.jsonfile that we bake into the capture file container.
Validate Vulkan Version
Validate the implementation and support in lavatube for a given Vulkan version
Validate Vulkan Version by arm-software · 4112221
npx skillmds@latest add arm-software/validate-vulkan-version File contents
---name: validate-vulkan-versiondescription: Validate the implementation and support in lavatube for a given Vulkan version---1. Check that we were told which Vulkan extension we are supposed to check. If this was not specified, ask.2. If you are not familiar with the extension, download the version summary from `https://docs.vulkan.org/refpages/latest/refpages/source/<version>.html`, where `version` is the version in the form `VK_VERSION_<major>_<minor>`, for example `VK_VERSION_1_4` for version 1.4.3. For each new command, check if we have an existing hardcoded KHR or EXT suffixed version of this command, and are missing a forward from a promoted command (ie without the suffix). Check the two files `src/hardcoded_read.cpp` (for replay) and `src/harcoded_write.cpp` (for capture). Also check the file `scripts/vkconfig.py` for extension variants that are similarly missing a promoted variant.4. As above, for each new structure defined, check if we have an existing hardcoded KHR or EXT suffixed version of it and are missing handling of the promoted variant. Look in the same files as for commands.5. Check that our feature pruning code handles this version of the standard. This is tracked within the `tracking.json` file that we bake into the capture file container.
arm-software/lavatube/tree/main/.agents/skills/validate-vulkan-version commit 41122215eb
Frequently asked questions
Run npx skillmds@latest add arm-software/validate-vulkan-version in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Validate the implementation and support in lavatube for a given Vulkan version It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
arm-software (@arm-software) published this skill. Their other Agent Skills are listed on their SkillMD profile.