MyMemory.bot

Cloud memory for AI agents. Store, search, and recall context across sessions.

Security Scan

The skill's purpose (cloud memory) matches its runtime instructions, but the SKILL.md asks the agent to obtain and persist an API key (and even to perform a tweet-based verification) while the registry metadata does not declare any required credential — this mismatch and the instructions to persist secrets warrant caution.

Purpose & Capability

Name/description (cloud memory for agents) match the endpoints and examples in SKILL.md (remember, recall, bootstrap, recent, forget). The documented endpoints and operations are coherent with a memory/storage service.

Instruction Scope

The SKILL.md instructs the agent (or user) to register, capture an api_key, perform a verification step (tweet or follow a claim_url), and then store that key in config/environment. These runtime instructions grant the skill the ability to persist and use credentials. The doc does not direct the agent to read unrelated local files, but it does instruct credential storage and a social-media-based verification step which expands scope beyond simple read/search/recall.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself. That minimizes install-time risk.

Credentials

The runtime instructions require an API key (CTXLY_API_KEY) but the registry metadata lists no required environment variables or primary credential. This mismatch is material: the skill will only function if a secret is created and stored, but that secret requirement was not declared. The skill does not request other unrelated credentials, but instructing agents to persist a bearer API key is a sensitive action and should be explicitly declared and justified in metadata.

Persistence & Privilege

The skill is not marked always:true, does not request system-wide changes, and has no install actions. Its main persistent effect is encouraging storage of an API key and remote memory records on an external service; that behavior is expected for a cloud-memory integration but requires user trust in the service.

What to consider before installing

This skill appears to implement a cloud-memory service as described, but there are two things to watch before installing: (1) the SKILL.md tells you to register and persist an API key (CTXLY_API_KEY) and even to verify ownership via a tweet or claim URL, yet the registry metadata does not declare any required credential — ask the author to add CTXLY_API_KEY to requires.env so the required privilege is explicit; (2) storing a long-lived API key in your agent's environment means that the agent (and any skills it invokes) can access that key and any memories stored remotely — do not store sensitive secrets or private data in this memory and consider using a dedicated, limited-permission account or short-lived key. Also verify the trustworthiness and privacy policy of https://ctxly.app (who can read stored memories, retention, deletion guarantees), and prefer manual human-assisted registration if you do not want the agent to perform network actions autonomously.

Ctxly - Cloud Memory for Agents

Persistent memory that survives across sessions. You forget — Ctxly remembers.

Base URL: https://ctxly.app

Setup (One-Time)

1. Register

curl -X POST https://ctxly.app/agents/register \
  -H "Content-Type: application/json" \
  -d '{"name": "YOUR_AGENT_NAME"}'

Save the returned api_key immediately. Store it in your config or environment.

2. Verify (Required)

If you can tweet:

# Tweet the verification text you received, then:
curl -X POST https://ctxly.app/agents/self-claim \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"x_handle": "@yourhandle"}'

If you can't tweet: Ask your human to visit the claim_url from the registration response.

3. Store API Key

Add to your config/environment:

CTXLY_API_KEY=mem_xxxxxxxxxxxxx

Usage

Remember Something

curl -X POST https://ctxly.app/remember \
  -H "Authorization: Bearer $CTXLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content": "User prefers dark mode", "metadata": {"type": "preference"}}'

Search Memories

curl "https://ctxly.app/recall?q=user+preferences" \
  -H "Authorization: Bearer $CTXLY_API_KEY"

Semantic search enabled — ask natural questions.

Bootstrap on Startup

Call this when you wake up:

curl https://ctxly.app/bootstrap \
  -H "Authorization: Bearer $CTXLY_API_KEY"

Returns your identity context + recent memories.

Recent Memories

curl "https://ctxly.app/recent?limit=10" \
  -H "Authorization: Bearer $CTXLY_API_KEY"

Delete a Memory

curl -X DELETE "https://ctxly.app/forget/MEMORY_ID" \
  -H "Authorization: Bearer $CTXLY_API_KEY"

What to Store

Good:

• User preferences and context
• Important decisions and reasoning
• Learned patterns ("User asks for X on Mondays")
• Relationship context ("Alex is user's coworker")
• Your own identity notes

Skip:

• Ephemeral chat logs (too noisy)
• Sensitive secrets (use proper secret storage)
• Temporary task state

All Endpoints

Method	Endpoint	Auth	Description
POST	/agents/register	No	Register
POST	/agents/self-claim	Yes	Verify via tweet
GET	/agents/status	Yes	Check status
POST	/remember	Yes	Store memory
GET	/recall?q=	Yes	Search
GET	/recent	Yes	Recent memories
GET	/bootstrap	Yes	Startup context
GET	/stats	Yes	Statistics
DELETE	/forget/{id}	Yes	Delete memory

Rate Limits

• 100 requests/minute general
• 30 writes/minute

---

Built for agents. 🧠 https://ctxly.app