memory-build-workflow
/memory-build-workflow
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.
- Author
- yeaight7 ↗
- Repository
- agent-powerups ↗
- Licence
- Apache-2.0
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- Overview
- When to Use
- Required Checks
- Routing
- Core Rules
- Minimal Workflow
- Common Failure Modes
- Verification
- References
SKILL.md preview
--- name: memory-build-workflow description: 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. --- # 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 ```powershell 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 1. Check whether a usable graph already exists. 2. If it exists and sources changed, prefer `graphify --update`. 3. If sources are noisy or binary, normalize them with the narrowest helper. 4. Build or refresh with `graphify`. 5. 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 - [`../graphify/UPSTREAM.md`](../graphify/UPSTREAM.md) - [`../../references/HELPER_TOOLS.md`](../../references/HELPER_TOOLS.md) - [`../../references/OBSIDIAN_EXPORT.md`](../../references/OBSIDIAN_EXPORT.md)
Versions
The database has no other skills named memory-build-workflow.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 01e0911dbbc0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100memory-optimization-workflow
Use when deciding the lowest-cost context path for a mixed corpus, especially when choosing among direct reading, helper conversion, graph build, graph update, or graph query. - 95graphify
Drive Graphify from its CLI to build, refresh, query, export, and serve a durable code/corpus knowledge graph. Use when the user wants `.graphify/GRAPH_REPORT.md`, `graph.json`, `graph.html`, `graphify update`/`summary`/`query`/`path`/`explain`/`tree`, change-aware review… - 100agent-memory
Give an agent persistent semantic memory with @three-ws/agent-memory. Use when code needs to remember facts across sessions, recall them by meaning, read the entity graph, or curate an agent's working context. - 100build-memory
Use this skill when the user wants to build, refresh, or teach their Aicoo agent memory from their real context — files, repo, git history, docs, or Claude/agent memory. Triggers on: 'build my memory', 'build my agent memory', 'teach my agent about me', 'what should my agent… - 100knowledge-graph
Knowledge graph and smart memory management using graphify + Obsidian-inspired patterns. Use when: setting up a knowledge graph, managing memory health, cross-linking notes, compiling wiki pages from scattered notes, adding structured frontmatter, or running memory health… - 100graphify-agents
Use a graphify knowledge graph to give agents low-token codebase context — query the graph instead of reading raw files during research, decomposition, and impact analysis. Use when wiring graphify into an agent-loop, an Explore/research subagent, or an MCP-enabled agent, or…