← Back to Skills Marketplace
XDV Engineer
by
Marlon Hanks
· GitHub ↗
· v1.0.0
· MIT-0
84
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install xdv-engineer
Description
Expert XDV Engineer grounded in the full XDV platform, with the XDV Specification as canon and all XDV organization repositories treated as supporting corpus.
Usage Guidance
Before installing, ask the publisher to clarify how the XDV repositories are provided: either include the canonical xdv-spec and necessary repos in the skill bundle or add a documented, auditable install step that clones from the official GitHub URLs and verifies commit hashes. Inspect the repository contents (or require the publisher to provide commit SHAs) before enabling the skill — the SKILL.md explicitly authorizes reading all files in the skill directory (including CI, configs, scripts, templates) which could contain secrets or unrelated data. If you plan to allow autonomous invocation, prefer a version that: (1) restricts the working corpus to a minimal set (e.g., xdv-spec and a small set of implementation repos), (2) documents integrity checks (commit hashes), and (3) limits which file types or paths the agent may consume. If the publisher cannot explain the missing install/fetch steps and provide reproducible provenance, avoid installing or run the skill in a tightly sandboxed review environment first.
Capability Tags
Capability Assessment
Purpose & Capability
The skill's stated purpose is to operate over the full XDV platform repos as an authoritative corpus. However, the package contains no repository files and no install spec to fetch them (no git clone, no download). That mismatch means the skill either assumes an out-of-band provisioning mechanism (not documented) or is incomplete. Requesting the entire org as corpus is plausible for an 'XDV Engineer', but only if the repositories are actually provided or fetched; here they are not.
Instruction Scope
SKILL.md instructs the agent to treat 'every file cloned into the skill directory' (including README, CI, configs, scripts, tests, templates) as working corpus and to not limit reasoning to top-level docs. This is broad: it will cause the agent to parse and potentially expose any file present in the skill directory (which may contain secrets or unrelated data). The instructions also do not include steps to obtain the repos, so it's unclear what files the agent should read.
Install Mechanism
There is no install specification and no code files — from a disk-write/execution-risk perspective this is low risk. However, the lack of an install mechanism is the root of the coherence problem: the skill claims to operate over cloned repos but does not provide or fetch them. A correct package should either bundle the required corpus or include a safe, documented fetch step (with integrity checks).
Credentials
The skill declares no required environment variables or credentials, which is proportionate. That said, the instruction to ingest all files in the skill directory means it could process sensitive configuration or credential material if present — a data exposure risk unrelated to declared env vars.
Persistence & Privilege
The skill is not marked 'always: true' and uses default autonomous invocation settings. It does not request persistent system privileges or to modify other skills/config. No persistence/privilege red flags in metadata.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install xdv-engineer - After installation, invoke the skill by name or use
/xdv-engineer - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
xDV Engineer skill 1.0.0 initial release.
- Introduced a dedicated XDV Engineer agent specialized in the full XDV Platform, grounded in the XDV Specification as canon.
- Clearly defined repository scope to treat every file from all XDV organization repositories as part of the active corpus, not just top-level docs.
- Listed all 35 primary XDV organization repositories, grouped by subsystem and architectural role.
- Codified architectural identity and domain definitions (K/Q/Φ), emphasizing determinism, domain boundaries, unified memory, and cross-domain orchestration.
- Established canonical reasoning policies, output structure, and precise conflict resolution hierarchy (spec > verification > core repos > tooling > drafts).
- Outlined core competency areas, best practices for repository examination, and boundaries for interpreting and reasoning about the XDV platform.
Metadata
Frequently Asked Questions
What is XDV Engineer?
Expert XDV Engineer grounded in the full XDV platform, with the XDV Specification as canon and all XDV organization repositories treated as supporting corpus. It is an AI Agent Skill for Claude Code / OpenClaw, with 84 downloads so far.
How do I install XDV Engineer?
Run "/install xdv-engineer" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is XDV Engineer free?
Yes, XDV Engineer is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does XDV Engineer support?
XDV Engineer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created XDV Engineer?
It is built and maintained by Marlon Hanks (@litecreator); the current version is v1.0.0.
More Skills