Skip to the rows

agentsclimarketplace

Memory query workflow

Skill yeaight7/agent-powerups/skills/memory-query-workflow

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

Install

npx -y skills add yeaight7/agent-powerups --skill memory-query-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus.

SKILL.md

2.3 KB, as published. Nobody here has run it

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

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

Confirm graphify-out/graph.json exists.
Choose query, path, or explain based on question shape.
Answer from graph evidence first.
If result quality is weak, say why: missing graph, stale graph, low coverage, or weak node match.
Escalate to build/update or targeted reread only when needed.

Common Failure Modes

skipping graph lookup and rereading everything
hiding that the graph is stale or incomplete
using query for a question that clearly needs a path trace
treating no-result output as proof the corpus lacks the concept

Verification

Graph existence was confirmed before any query ran
The command matched the question shape: query for breadth, path for traces, explain for one node
The answer is grounded in graph nodes and edges — no overclaiming
Staleness, sparseness, or weak node matches were stated explicitly
Escalation to build, update, or targeted reread happened only when graph evidence was insufficient

Reference

../graphify/UPSTREAM.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.