wiki-ask

Convert MemoryLane natural-language questions into structured TASK JSON payloads.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/itsmarsss/memento --skill wiki-ask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-ask
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.skills/wiki-ask
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a natural-language question about the MemoryLane vault into a frontend-renderable, machine-readable TASK object instead of a human-only prose answer.

Core Features & Use Cases

  • Structured retrieval-to-render output: Executes the same retrieval behavior as wiki-query but reshapes results into the exact JSON schema the frontend expects.
  • Deterministic, tab-friendly task IDs: Produces a stable question hash (q_<8-hex>) so the UI can dedupe and consistently render results.
  • Rich, component-oriented response payload: Returns activated node IDs, moments, entities, session metadata, synthesis insight, and block summaries for interactive right-panel display.

Quick Start

Run wiki-ask with your question text to get a single JSON object containing moments, entities, session metadata, and an optional synthesis insight.

Frequently Asked Questions about wiki-ask

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

FAQPage Schema
How do I convert natural language vault queries into structured JSON for frontend rendering?

To convert natural language vault queries into structured JSON, you need a retrieval mechanism that parses questions and emits a schema-compliant payload. This skill resolves MemoryLane questions into a machine-readable TASK JSON object containing moments, entities, and citations for direct frontend tab rendering.

What is the best way to retrieve memory vault data with deterministic task IDs?

Retrieving memory vault data with deterministic task IDs requires computing a stable question hash during the query process. This skill generates a unique 8-character hexadecimal identifier (`q_<8-hex>`) for each query, enabling the UI to deduplicate and consistently render structured retrieval results.

How does semantic search work with Obsidian vault querying for backend route usage?

Semantic search for backend route usage in Obsidian vault querying involves spawning a retrieval process that returns machine-readable answers. This skill executes vault retrieval to compute activated node IDs and subassembly tags, emitting exactly one parseable JSON object matching the required frontend schema.

Can I use structured JSON payloads for interactive right-panel display in a memory retrieval system?

Yes, you can use structured JSON payloads for interactive right-panel display by including component-oriented response data. This skill returns a rich payload containing session metadata, synthesis insights, and block summaries, satisfying the requirements for rendering interactive right-panel components.

What limitations exist when hashing natural language questions for frontend tab rendering?

Hashing natural language questions for frontend tab rendering is limited by the deterministic nature of the hash, meaning identical questions yield identical IDs. This approach relies on exact string matching to deduplicate UI elements, so paraphrased questions will generate new unique task IDs instead of reusing existing ones.