Legacy — Qoris Memory (use qoris-memory-mcp)

v1.0.5

⚠️ LEGACY LISTING. The canonical home for this skill is now qoris-memory-mcp under the @qoris-ai org publisher. Please run: clawhub install qoris-memory-mcp.

0· 145·0 current·0 all-time
byQoris AI@apps-debug

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for apps-debug/qoris-memory.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Legacy — Qoris Memory (use qoris-memory-mcp)" (apps-debug/qoris-memory) from ClawHub.
Skill page: https://clawhub.ai/apps-debug/qoris-memory
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: QORIS_API_KEY, QORIS_WORKSPACE_ID
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install qoris-memory

ClawHub CLI

Package manager switcher

npx clawhub@latest install qoris-memory
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, declared env vars (QORIS_API_KEY, QORIS_WORKSPACE_ID), mcp endpoint (https://mcp.qoris.ai/mcp), and documented tools all align with a memory-MCP integration. The requested credentials are exactly what you'd expect for a hosted memory service.
Instruction Scope
SKILL.md and mcp-config.json explicitly describe calling the MCP server and list only memory-related tools. Instructions do not direct the agent to read unrelated files, scan system state, or transmit data outside the documented MCP endpoint; they state that only data explicitly passed to tool calls is sent.
Install Mechanism
No install spec and no code files to execute — the skill is instruction-only. This minimizes disk/installation risk.
Credentials
Two environment variables are requested and both are justified (API key and workspace ID). primaryEnv is correctly set to QORIS_API_KEY. No unrelated secrets or excessive env access are requested.
Persistence & Privilege
always is false and autonomous invocation is allowed (platform default). The skill does not request persistent/privileged system modifications or access to other skills' configs.
Assessment
This legacy listing is internally consistent and appears safe in that it only requires a Qoris API key and workspace ID and talks to the documented MCP endpoint. Before installing: prefer the canonical package (qoris-memory-mcp) as recommended in the README; verify you trust the domain (mcp.qoris.ai) and the publisher; provide a least-privilege API key if possible (workspace-scoped, revocable); avoid sending sensitive secrets or PII to the memory tools unless you accept them being stored in Qoris’s service; rotate your QORIS_API_KEY if you suspect compromise.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

EnvQORIS_API_KEY, QORIS_WORKSPACE_ID
Primary envQORIS_API_KEY
deprecatedvk979p8a3kvzsft6sbbrygrvtn584wcralatestvk979p8a3kvzsft6sbbrygrvtn584wcralegacyvk979p8a3kvzsft6sbbrygrvtn584wcramcpvk979p8a3kvzsft6sbbrygrvtn584wcramemoryvk979p8a3kvzsft6sbbrygrvtn584wcra
145downloads
0stars
5versions
Updated 1w ago
v1.0.5
MIT-0

Legacy — Qoris Memory

⚠️ This skill has moved

Install qoris-memory-mcp instead.

clawhub install qoris-memory-mcp

This qoris-memory slug under @apps-debug is kept only for backward compatibility with users who installed earlier versions. All future updates, new features, and new versions will be published exclusively to qoris-memory-mcp under the @qoris-ai org publisher.

Why did it move?

We set up a dedicated @qoris-ai organization publisher on ClawHub and migrated the canonical listing to it. This @apps-debug listing is the original pre-migration home and will no longer receive feature updates.

What to do

If you're already using qoris-memory, switch to qoris-memory-mcp:

clawhub uninstall qoris-memory
clawhub install qoris-memory-mcp

Your existing QORIS_API_KEY and QORIS_WORKSPACE_ID work identically with the new slug — same underlying MCP server at https://mcp.qoris.ai/mcp, same tools, same behavior.

Data Handling & Privacy

This skill connects to the Qoris MCP server (https://mcp.qoris.ai/mcp) and exposes explicit memory tools (save_memory, search_knowledge, etc.). The skill does not capture or persist conversation content automatically — only data you explicitly pass to a tool call is transmitted.

  • What gets sent: only content you pass to explicit tool calls
  • Where it's stored: https://mcp.qoris.ai/mcp scoped to your QORIS_WORKSPACE_ID
  • Credential ownership: QORIS_API_KEY is your own per-user secret, not bundled
  • Retention: per https://qoris.ai/privacy
  • Revocation: rotate QORIS_API_KEY in your dashboard

Available Memory Tools (inherited from canonical)

save_memory, get_memories, search_knowledge, update_memory, delete_memory, list_knowledge_documents, get_document_full_content.

See the full documentation at the canonical listing: qoris-memory-mcp.

Support

  • Canonical listing: https://clawhub.ai/qoris-memory-mcp
  • Documentation: https://docs.qoris.ai/memory
  • Source: https://github.com/QORIS-AI/qoris-memory-openclaw-skill
  • Support: eliel@qoris.ai

About Qoris AI

Qoris AI builds the trust and governance layer for enterprise AI agents. NVIDIA Inception Program member. Claude Partner Network member. Patent pending U.S. 63/907,730. Based in Stamford, CT.

qoris.ai

Comments

Loading comments...