ki-memory-write

Writes seven types of project memory atoms into ki-search with deduplication and fallback handling.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill ki-memory-write-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ki-memory-write
Source: https://github.com/HACK-WU/skills/tree/main/skills/ki-memory-write
Command: npx skills add https://github.com/HACK-WU/skills --skill ki-memory-write-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It consolidates the scattered logic for writing memories into ki-search into one single source of truth, eliminating duplicated format constraints, availability checks, scope resolution, and deduplication rules across skills like expert-team, strong-relation, debug, and code-review. ## Core Features & Use Cases - Seven Memory Type Strategies: Dispatches writes for topic memories, API interfaces, data flows, decisions, error library, strong relations, and pending changes, each with its own reference policy file. - Write-Time Hard Constraints: Enforces plain-text formatting (no YAML, headings, or tables), mandates ki_sync_relation APIs over ki_store, and controls vectorization via the vector parameter. - Deduplication and Degradation: Queries existing group entries before writing to update instead of duplicating, and gracefully skips writes when ki is unavailable without blocking callers. - Use Case: After expert-team builds a module expert, call this skill to write the topic memory, interface info, and data flow atoms into ki-search with correct groups, tags, and dedup checks. ## Quick Start Ask the AI to record a decision or error into ki memory, for example: record this decision about using polling instead of webhooks into ki memory.

Frequently Asked Questions about ki-memory-write

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write project memories into ki-search?

Invoke this skill with a memory type and the prepared content. It detects ki availability, resolves the scope, selects the matching strategy reference, validates formatting, deduplicates against existing group entries, and writes via ki_bulk_sync_relation.

What memory types does ki-memory-write support?

It supports seven types: topic memories, API interface info, data flows, decision records, error library entries, strong relations, and pending changes. Each type has its own group naming, relation convention, tags, and field template defined in a dedicated reference file.

Why must writes use ki_sync_relation instead of ki_store?

ki_store and ki_bulk_store only write the vector layer without the local knowledge base, producing orphan vectors. ki_sync_relation and ki_bulk_sync_relation write both KB and vectors, keeping storage consistent.

How does the skill prevent duplicate memory entries?

Before writing, it runs ki_query_group with mode="full" on the target group and compares relation names. Existing relations are updated rather than recreated, and batch writes query the group only once for the full comparison.

What happens when ki-search is unavailable?

The skill skips the write, outputs the memory content as an in-conversation list to the caller, and does not block the caller's main workflow. Pending changes fall back to writing full entries into AGENTS.md instead.

When should pending changes use vector=false?

Pending changes are a to-do ledger, not knowledge, so they are written with vector=false to stay out of semantic search while remaining in the KB. They are verified with ki_query_group direct queries, never ki_search.