verify-with-oql skillA
verify-with-oql is agent-read markdown (skill) from mendixlabs/mxcli: Verify microflow side effects and data changes with OQL against a running app. Use after executing changes to confirm data was created, updated or deleted as expected, or to back a browser test with a data assertion..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Verify with OQL Skill This skill documents how to verify microflow side effects and data changes using OQL queries against a running Mendix app. ## When to Use This Skill Use this when: - You've deployed changes and want to verify data was created/updated/deleted correctly - You need to confirm a microflow produced the expected side effects - You're combining Playwright UI tests with backend data verification - You want a fast feedback loop: deploy, trigger, verify ## The Pattern The core verification workflow is: 1. **Deploy** — apply MDL changes and rebuild 2. **Trigger** — execute the action (via UI, microflow call, or API) 3. **Verify** — query the database with OQL to confirm the result ```bash # 1. Deploy mxcli exec changes.mdl -p app.mpr mxcli docker build -p app.mpr --skip-check mxcli docker reload -p app.mpr # or: mxcli docker up -p app.mpr --fresh --wait # 2. Trigger (example: call a microflow that creates test data) # This could be via Playwright, a rest call, or manual interaction # 3. Verify mxcli oql -p app.mpr "select Name, Email from MyModule.Customer where Name = 'Jane Doe'" ``` ## OQL Verification Examples ### Check data was created ```bash …
Read the whole file at its exact version.
How to install
mdr add mendixlabs/mxcli/verify-with-oql@git:20260821.ff81a24mdr add mendixlabs/mxcli/verify-with-oql@sha256:933d52575f981e71Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_bm66pyztgxbkxirr)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6616 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mendixlabs/mxcli · 124 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bm66pyztgxbkxirr GET https://markdownregistry.com/api/v1/resolve?ref=mendixlabs/mxcli/verify-with-oql GET https://markdownregistry.com/api/v1/blob/933d52575f981e7109286c6f0b223cfa27097ef457d27787376be4df01678c28
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.