Quack Memory

Store and recall persistent memories via FlightBox (Quack Network). Use when storing agent memories, recalling past context, searching agent memory, or persi...

Security Scan

The skill appears internally consistent with its stated purpose: it stores and recalls agent memories via the FlightBox API and only reads a local Quack credential file; nothing requested or installed is disproportionate to that goal.

Purpose & Capability

Name/description claim persistent memory storage via FlightBox. The scripts call FlightBox endpoints (remember/recall/timeline/forget) and read a local quack.json for agentId/apiKey — this matches the described purpose.

Instruction Scope

Runtime instructions and scripts consistently instruct reading ~/.openclaw/credentials/quack.json and calling the FlightBox API. Minor inconsistency: SKILL.md shows a bash snippet creating a QUACK_KEY env var and documents an Authorization header with <QUACK_API_KEY>, but the provided scripts do not use an environment variable — they read the local credentials file directly.

Install Mechanism

No install spec or remote downloads. The skill is instruction-only with included JS scripts; nothing is fetched or written to disk during install by the skill itself.

Credentials

No environment variables or external credentials declared in registry metadata, but the scripts require a local credentials file (~/.openclaw/credentials/quack.json) containing apiKey and agentId. That is proportionate to the task but should be documented/verified (it relies on the quack-identity registration step).

Persistence & Privilege

always:false and normal model invocation settings. The skill does not modify other skills or global agent configuration and does not request persistent elevated privileges.

Assessment

This skill appears to do what it claims: it reads a local Quack credential file (~/.openclaw/credentials/quack.json) and sends memory data to FlightBox (https://flightbox.replit.app). Before installing, confirm that (1) the quack.json file is created by a trusted quack-identity flow and contains only the expected agentId/apiKey, (2) you are comfortable storing any agent memory on a third-party FlightBox service (sensitive data saved there will be transmitted off-host), and (3) you accept the small SKILL.md inconsistency where it references an env var (QUACK_API_KEY) but the scripts read the credentials file directly. If you need stricter isolation, review/modify the scripts to sanitize content before sending or run the skill in an isolated environment.

Store and recall persistent memories via FlightBox on the Quack Network.

Prerequisites

Quack credentials at ~/.openclaw/credentials/quack.json (run the quack-identity skill's registration first if not).

QUACK_KEY=$(node -p "JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.openclaw/credentials/quack.json','utf8')).apiKey")

Store a Memory

node {baseDir}/scripts/remember.mjs --type "lesson" --content "Always verify before reporting"

Types: decision, fact, lesson, todo, context

Optional flags: --tags "safety,ops" --importance 0.9

Recall Memories

node {baseDir}/scripts/recall.mjs --query "user preferences"

Optional flags: --type "fact" --limit 5

View Timeline

node {baseDir}/scripts/timeline.mjs

Optional flags: --type "decision" --limit 10

Forget a Memory

node {baseDir}/scripts/forget.mjs --id "mem_7f3a2b"

API Reference

Base URL: https://flightbox.replit.app/api/v1 Auth: Authorization: Bearer <QUACK_API_KEY>

Endpoint	Method	Description
/remember	POST	Store a memory
/recall	GET	Semantic search across memories
/timeline	GET	Chronological memory timeline
/forget	DELETE	Remove a specific memory

⚠️ Status

FlightBox may be temporarily offline. If endpoints return errors, check https://flightbox.replit.app/api/v1/remember — the app needs to be redeployed on Replit.

Works Great With

• quack-identity — Register on the Quack Network first
• quackgram — Send messages to other agents
• quack-sdk — Full API reference

Powered by Quack Network 🦆