memory-query-workflow skillA
memory-query-workflow is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus..
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
# Memory Query Workflow ## Overview Use existing graph memory first. Query the graph before rereading source files unless the graph is missing, stale, or too weak for the question. ## Required Check ```powershell apx check graphify ``` ## Required State - existing `graphify-out/graph.json` ## Routing | Question shape | Action | |---|---| | broad question about connected concepts | `graphify query` | | trace between two concepts, files, or systems | `graphify path` | | explain one concept or node in context | `graphify explain` | | no graph exists | switch to `memory-build-workflow` | | graph exists but corpus changed | recommend `graphify --update` before trusting results | ## Core Rules - prefer graph retrieval over full-corpus reread - say explicitly when the graph is missing, stale, sparse, or weakly matched - do not overclaim beyond what graph nodes and edges support - when graph coverage is weak, use the graph result to target the next direct read instead of restarting broad exploration ## Minimal Workflow 1. Confirm `graphify-out/graph.json` exists. 2. Choose `query`, `path`, or `explain` based on question shape. 3. Answer from graph evidence first. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/memory-query-workflow@git:20260606.b4c6095mdr add yeaight7/agent-powerups/memory-query-workflow@sha256:5f1b986199214e66Pin 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_uctvl73kcth7anty)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.b4c6095 latest | 2026-06-06 | b4c6095 | 2,307 B | A | view · diff |
| git:20260509.3a5a68e | 2026-05-09 | 3a5a68e | 1,877 B | A | view · diff |
| git:20260509.9238157 | 2026-05-09 | 9238157 | 734 B | A | view |
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 (2307 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uctvl73kcth7anty GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/memory-query-workflow GET https://markdownregistry.com/api/v1/blob/5f1b986199214e6649884269e1adc68be858b1adf00de688685ec07bb7a373f6
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.