ownify-memory-enhanced

Enforce memory-first workflows for ownify questions with semantic search and knowledge-graph lookups.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/HaraldeRoessler/ownify-microclaw --skill ownify-memory-enhanced
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ownify-memory-enhanced
Source: https://github.com/HaraldeRoessler/ownify-microclaw/tree/main/skills/built-in/ownify-memory-enhanced
Command: npx skills add https://github.com/HaraldeRoessler/ownify-microclaw --skill ownify-memory-enhanced

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a strict memory protocol for ownify workflows, ensuring the assistant searches stored knowledge before answering and records newly learned facts immediately after each interaction.

Core Features & Use Cases

  • Mandatory memory lookup: Searches prior records before responding, even for simple acknowledgements.
  • Entity-aware retrieval: Queries knowledge graph entries when users mention specific projects, services, people, or infrastructure.
  • Immediate persistence: Stores decisions, preferences, todos, workspace facts, diary notes, and events as soon as they are discovered.
  • Use Case: A user asks about a tenant project or a previously discussed configuration, and the Skill retrieves relevant memory so the answer reflects established context instead of generic training data.

Quick Start

Ask the assistant to look up prior ownify context for the topic you care about and respond using stored records.

Frequently Asked Questions about ownify-memory-enhanced

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

FAQPage Schema
How does a memory-first knowledge graph workflow preserve tenant context?

A memory-first workflow preserves tenant context by enforcing a mandatory semantic search and knowledge-graph lookup before responding, ensuring answers reflect established project records. It then immediately writes newly discovered facts back into structured memory.

How do I retrieve tenant infrastructure and project context from stored memory?

You retrieve tenant infrastructure and project context by requesting a lookup of prior ownify records. The system performs semantic search and entity-aware knowledge graph queries to fetch relevant decisions, preferences, and configurations.

What is entity-aware retrieval for named infrastructure and project context?

Entity-aware retrieval queries a knowledge graph for specific named entities like projects, services, people, or infrastructure. It fetches structured relationships and stored facts to provide context-aware responses instead of generic answers.

When do I need immediate structured memory writes for tenant preferences and todos?

You need immediate structured memory writes whenever new decisions, preferences, todos, or workspace facts are discovered during an interaction. This persistence ensures future queries retrieve the updated tenant context accurately.

Can I use semantic search and knowledge graph lookup for tenant diary notes and events?

Yes, semantic search and knowledge graph lookup apply to tenant diary notes and events. The system retrieves stored records for these factual follow-up tasks and immediately persists any newly learned event data.

What are the limitations of enforcing mandatory memory retrieval before simple acknowledgements?

Enforcing mandatory memory retrieval before simple acknowledgements adds latency to every interaction. However, it ensures no response bypasses established tenant context, preventing loss of continuity in project workflows.