Memory Import

OrganizationPopular

Prismer-AI

memory-import

Bulk-import an external knowledge base into Prismer memory via the three-layer import pipeline (07 §3.1). Use when the user asks to import/migrate documents, a knowledge base, or notes into workspace memory. Layer 1 lands raw documents (zero LLM, instantly searchable); Layer 2 is YOUR distillation work — you read the landed documents and write candidate pages; Layer 3 commits candidates through the memory evolution gate. Distinct from the native memory_write tool face (that is for single, in-conversation writes).

Overview

Publisher	Prismer-AI
Repository	`PrismerCloud`
Skill name	`memory-import`
Stars	1.6K
Forks	17
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Prismer-AI on GitHub. Read the source before you install it.

Installation

Install the Memory Import AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/cloud/catalog/skills/memory-import
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/cloud/catalog/skills/memory-import

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git /tmp/PrismerCloud
mkdir -p .claude/skills
cp -r /tmp/PrismerCloud/sdk/cloud/catalog/skills/memory-import .claude/skills/memory-import

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Memory Import in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Memory Import on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Memory Import is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Memory Import

Bulk-import external material into workspace memory through a session — the unit of quota, audit, and gate evaluation. Three layers, two of which are yours:

Layer 1 — land the documents (zero LLM, do this first)

bash
cloud memory imports open --workspace <ws>          # → { id }
cloud memory imports write-documents <id> --workspace <ws> --documents '[{"name":"…","content":"…"}]'

Raw documents become searchable in seconds. No quality bar here — that is Layer 2's job.

Layer 2 — distill (YOUR LLM, your compute)

Read the landed documents, then author candidate pages and submit them:

One page per coherent topic, attached under the right hub (<hub>/<topic>.pkf, relative to the Memory root; do not prepend another memory/).
Every candidate MUST carry the memory frontmatter block — the pipeline rejects the whole batch otherwise: {"type":"note","title":"…","description":"…","memory":{"memoryRole":"knowledge|procedure|action_result","source":"<where this came from, in words a human can read>"}}.
Distill, don't dump: conclusions and procedures, not transcripts. The raw documents stay in Layer 1 as the reference layer.

bash
cloud memory imports write-batch <id> --workspace <ws> --candidates '[{"pagePath":"…","contentDiff":"<full PKF body>"}]'

Layer 3 — commit (cloud-side gate, zero negotiation)

bash
cloud memory imports commit <id> --workspace <ws>   # runs the evolution gate
cloud memory imports status <id> --workspace <ws>   # per-candidate verdicts

The gate REJECTS batches that lose retrieval coverage (a candidate replacing a page must not delete its keywords) or lack metadata. A rejected commit is final for the session: read the verdict, fix the candidates, open a NEW session, resubmit. Never re-submit an identical rejected batch — the Ledger rejects same-shape candidates for 30 days.

Routing: raw archive / small batch → L1 + owner review. Knowledge-base migration / high-quality distillation → L1 → L2 → L3 (semantic work on YOUR compute; the cloud only gates and records).

Frequently asked questions

What does the Memory Import AI skill do?

Why use Memory Import on TypingMind?

Because you install it once and use it with any model. Memory Import is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Memory Import in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/cloud/catalog/skills/memory-import. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Memory Import?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Memory Import?

As many as you like. As long as a model supports skills, you can use Memory Import with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Memory Import AI skill free?

Yes. It is published on GitHub by Prismer-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Graincrawl

openclaw

OrganizationPopular

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Memory Import

Layer 1 — land the documents (zero LLM, do this first)

Layer 2 — distill (YOUR LLM, your compute)

Layer 3 — commit (cloud-side gate, zero negotiation)

Frequently asked questions

Related AI Skills

Set up your own AI workspace now