Skip to the rows

agentsclimarketplace

Memory build workflow

Skill yeaight7/agent-powerups/skills/memory-build-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-build-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 user needs to build or refresh persistent graph memory from a mixed corpus and the right path may include graphify, incremental update, or helper conversion before ingestion.

SKILL.md

3.0 KB, as published. Nobody here has run it

Memory Build Workflow

Overview

Build persistent graph memory with graphify.

Use helper tools only when source format would otherwise reduce graph quality or waste context.

When to Use

first graph build for a repo, notes folder, research corpus, or mixed raw folder
corpus changed enough that persistent graph memory is worth refreshing
input includes PDFs, Office docs, or noisy web pages that should be normalized before graph build
user wants durable graph outputs instead of one-shot file reading

Do not use for:

one small plain-text file or a narrow one-off question
cases where an existing graph already answers the question better via query

Required Checks

apx check graphify
apx check markitdown-file-intake
apx check defuddle

Stop and report missing tools. Do not auto-install without approval.

Routing

Situation	Action
ready local corpus of readable files	run `graphify`
existing graph plus changed sources	run `graphify --update`
PDF, Office doc, slide deck, or similar hard-to-read format	convert with `markitdown-file-intake`, then build with `graphify`
article or noisy web page	clean with `defuddle`, then build with `graphify`
user wants vault browsing after build	offer optional Obsidian export

Core Rules

graphify is the primary engine
prefer graphify --update over full rebuild when a graph already exists
use helpers only to improve source readability before graph ingestion
keep Obsidian optional and post-build
keep source provenance intact when converting inputs

Minimal Workflow

Check whether a usable graph already exists.
If it exists and sources changed, prefer graphify --update.
If sources are noisy or binary, normalize them with the narrowest helper.
Build or refresh with graphify.
Offer query workflow next instead of rereading the corpus.

Common Failure Modes

missing graphify: stop and report; no fallback build path
rebuilding from scratch when update would work: unnecessary cost and churn
using helpers on already-readable Markdown or code: wasted step
treating Obsidian as required: wrong; it is optional output only

Verification

Required tool checks ran; missing tools were reported, not auto-installed
An existing usable graph was checked for before any build
Incremental update was preferred over full rebuild when a graph existed
Helpers were used only on sources that would otherwise degrade graph quality
Source provenance survived any conversion; Obsidian was offered, never assumed

References

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.