validate-binaries
Uses objdump to inspect binary files for specific CPU instruction sets like AVX-512 and reports pass or fail status.
Install
mkdir -p .claude/skills/validate-binaries && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3242" && unzip -o skill.zip -d .claude/skills/validate-binaries && rm skill.zipInstalls to .claude/skills/validate-binaries
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Validate voxtype binaries for CPU instruction contamination. Use when checking release binaries for AVX-512 or GFNI instruction leaks that would crash on older CPUs.Key capabilities
- →Inspect binary files for zmm registers
- →Detect forbidden AVX-512 specific instructions (vpternlog, vpermt2)
- →Identify GFNI instruction usage
- →Report binary safety status based on CPU compatibility
How it works
It executes objdump to disassemble binaries and greps for specific instruction sets or register names that signify incompatible CPU requirements.
Inputs & outputs
When to use validate-binaries
- →Checking AVX2 binary safety
- →Validating Vulkan binary compatibility
- →Hunting for forbidden CPU instructions
- →Confirming AVX-512 optimization
About this skill
Validate Binaries
Verify that voxtype binaries don't contain forbidden CPU instructions that would cause crashes on older CPUs.
What This Checks
| Binary | Must NOT have | Must have |
|---|---|---|
| AVX2 | zmm registers, AVX-512 EVEX, GFNI | - |
| Vulkan | zmm registers, AVX-512 EVEX, GFNI | - |
| AVX-512 | - | zmm registers (confirms optimization) |
Forbidden Instructions
zmmregisters - 512-bit AVX-512 registersvpternlog,vpermt2,vpblendm- AVX-512 specific{1to4},{1to8},{1to16}- AVX-512 broadcast syntaxvgf2p8,gf2p8- GFNI instructions (not on Zen 3)
Usage
When asked to validate binaries:
- Determine the version from context or ask
- Find binaries in
releases/${VERSION}/ - Run objdump checks on each binary
- Report pass/fail for each
Validation Commands
# Set version
VERSION=0.4.14
# Check AVX2 binary (should be 0 for all)
echo "=== AVX2 Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -c zmm || echo "zmm: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -cE 'vpternlog|vpermt2|vpblendm' || echo "AVX-512 ops: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -cE 'vgf2p8|gf2p8' || echo "GFNI: 0"
# Check Vulkan binary (should be 0 for all)
echo "=== Vulkan Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-vulkan | grep -c zmm || echo "zmm: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-vulkan | grep -cE 'vgf2p8|gf2p8' || echo "GFNI: 0"
# Check AVX-512 binary (should be > 0)
echo "=== AVX-512 Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx512 | grep -c zmm
Interpreting Results
PASS conditions:
- AVX2: All counts are 0
- Vulkan: All counts are 0
- AVX-512: zmm count > 0
FAIL conditions:
- AVX2 or Vulkan has any zmm/GFNI instructions
- AVX-512 has 0 zmm instructions (not optimized)
If validation fails, the Docker build cache is likely stale. Recommend:
docker compose -f docker-compose.build.yml build --no-cache avx2 vulkan
When not to use it
- →When checking source code rather than compiled binaries
- →When validating non-x86_64 architectures
Prerequisites
Limitations
- →Relies on binary disassembly accuracy
- →Requires knowledge of which CPU instruction sets are forbidden for the target hardware
How it compares
It provides an automated check for hardware compatibility issues rather than relying on runtime crash logs.
Compared to similar skills
validate-binaries side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| validate-binaries (this skill) | 1 | 7mo | Review | Intermediate |
| equilateral-agents | 5 | 9mo | No flags | Intermediate |
| dynamic-instrumentation | 3 | 6mo | Review | Advanced |
| secrets-manager | 1 | 7mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by peteonrails
View all by peteonrails →You might also like
equilateral-agents
Equilateral-AI
22 production-ready AI agents with database-driven orchestration for security reviews, code quality analysis, deployment validation, infrastructure checks, and compliance. Auto-activates for security concerns, deployment tasks, code reviews, quality checks, and compliance questions. Includes upgrade paths to enterprise features (GDPR, HIPAA, multi-account AWS, ML-based optimization).
dynamic-instrumentation
gmh5225
Expertise in LLVM-based dynamic binary instrumentation, runtime tracing, and program monitoring. Use this skill when implementing runtime analysis tools, code coverage systems, profilers, or dynamic security monitors.
secrets-manager
itsmostafa
AWS Secrets Manager for secure secret storage and rotation. Use when storing credentials, configuring automatic rotation, managing secret versions, retrieving secrets in applications, or integrating with RDS.
vertex-engine-inspector
jeremylongshore
Execute inspect and validate Vertex AI Agent Engine deployments including Code Execution Sandbox, Memory Bank, A2A protocol compliance, and security posture. Generates production readiness scores. Use when asked to "inspect agent engine" or "validate depl... Trigger with relevant phrases based on skill purpose.
swarm-act
ethersphere
Guide to Swarm ACT encryption and access control: create grantees, upload protected data, grant/revoke access, and troubleshoot not-found/history issues.
azure-artifact-signing
orgdevendra
Expert knowledge for Azure Artifact Signing development including best practices, decision making, security, configuration, and integrations & coding patterns. Use when managing signing cert lifecycle, RBAC roles, DGSSv2 migration, diagnostic logs, or CI/CD signing workflows, and other Azure Artifac