← Back to Skills Marketplace
jeff0052

Fpms Memory

by jeff0052 · GitHub ↗ · v0.2.0 · MIT-0
cross-platform ⚠ suspicious
110
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install fpms-memory
Description
Cognitive memory engine — gives your AI persistent work tracking, proactive risk alerts, and cross-conversation continuity. Never lose track of projects again.
README (SKILL.md)

FPMS — Focal Point Memory System

Your AI forgets everything between conversations. FPMS fixes that.

Not just memory — attention management. FPMS tracks your projects, detects stuck tasks, and loads the right context at the right time.

What You Get

  • Cross-conversation memory — Start Monday, continue Wednesday, review Friday
  • Structured work tracking — Projects → Tasks → Subtasks with status lifecycle
  • Proactive alerts — "Task X has been blocked for 3 days"
  • Smart context loading — Only loads what fits your token budget
  • GitHub sync — Issues auto-sync as FPMS nodes

How It's Different From Other Memory Tools

Mem0/Zep FPMS
Remembers conversations Yes Yes (via prompt rules)
Tracks tasks & projects No Yes
Alerts you about stuck work No Yes (heartbeat)
Manages token budget No Yes (L0/L1/L2)
Parent-child task hierarchy No Yes
GitHub integration No Yes

Other tools remember what was said. FPMS manages what needs to be done.

Setup

1. Install

pip install focalpoint

2. Add MCP server to openclaw.yaml

mcp_servers:
  fpms:
    command: focalpoint

3. Restart OpenClaw

That's it. 18 tools are now available in your conversations.

Use Cases

Project tracking

You: "Create a project for the product launch with 3 tasks"
(Next day)
You: "What's the launch status?"
AI:  "3 tasks: 1 done, 1 active, 1 blocked. The blocked task
      is waiting on design review — it's been 2 days."

Decision memory

You: "We're going with Stripe for payments"
(Two weeks later)
You: "Why did we pick Stripe?"
AI:  "You decided on March 15 — better API and lower international fees."

Risk detection

AI automatically runs heartbeat and finds:
  - Deploy task BLOCKED for 4 days
  - Docs update STALE — no activity for a week
  - Bug fix AT RISK — deadline is tomorrow

Available Tools (18)

Tool What it does
bootstrap Load memory context (call at conversation start)
heartbeat Scan for risks: blocked, stale, at-risk tasks
create_node Create a project/task/goal
update_status Change status (inbox/active/waiting/done/dropped)
append_log Record decisions, progress, links
get_context_bundle Get token-budgeted context payload
search_nodes Find tasks by status, parent, source
get_node Get full details of a work item
shift_focus Switch AI attention to a specific task
expand_context See parent, children, dependencies
update_field Update title, summary, deadline, etc.
attach_node / detach_node Move tasks in hierarchy
add_dependency / remove_dependency Manage task dependencies
unarchive Restore completed/dropped tasks
set_persistent Protect tasks from auto-archive
get_assembly_trace Debug context assembly

Automatic Memory Rules

Follow these rules in EVERY conversation:

  1. Conversation start → Call bootstrap to load memory
  2. User mentions a task/project/goalcreate_node
  3. User makes a decisionappend_log to the relevant node
  4. Task progressesupdate_status
  5. Before conversation endsappend_log key takeaways
  6. Every ~10 minheartbeat to check for risks

Requirements

  • Python 3.10+
  • No external services — runs 100% locally on SQLite

Links

Usage Guidance
Do not install blindly. Before installing, verify the upstream package and provenance: check PyPI/GitHub for a package named 'focalpoint' (and reconcile the 'fpms' references), inspect the package source, and confirm what the 'focalpoint' binary does and whether it makes network calls. Ask the maintainer how GitHub sync authenticates (does it require a token? where to set it?) and what data is transmitted during 'heartbeat' and syncs. Prefer installing in a sandbox or VM and running the binary with network disabled until you confirm its behavior. If you rely on this skill for sensitive projects, require explicit documentation of authentication and a vetted release (signed GitHub release or well-known package on PyPI). If any of these points are unclear or the package is only available from an untrusted URL, treat the skill as unsafe to install.
Capability Analysis
Type: OpenClaw Skill Name: fpms-memory Version: 0.2.0 The skill bundle describes a 'Focal Point Memory System' (FPMS) designed to provide persistent task tracking and memory for AI agents using a local SQLite database. It installs the 'focalpoint' Python package and provides a set of 18 tools for managing project nodes, logs, and context. The instructions in SKILL.md are consistent with the stated purpose of a productivity and memory tool, and no indicators of data exfiltration, malicious execution, or harmful prompt injection were found.
Capability Assessment
Purpose & Capability
The claimed purpose — a local, Python-based memory/task engine — matches the requirement for python3 and a local binary named 'focalpoint'. However the SKILL.md and registry metadata use multiple package names (focalpoint, fpms, focalpoint/fpms on PyPI/GitHub) and a GitHub sync feature is listed without describing how GitHub auth is provided. These naming/auth mismatches are inconsistent with the stated purpose and should be clarified.
Instruction Scope
The runtime instructions tell the agent to add an MCP server entry and call a range of tools automatically (bootstrap on conversation start, append_log for decisions, update_status, and run 'heartbeat' every ~10 minutes). While these are coherent for a memory tool, the instructions also mandate continuous/periodic operations and automatic actions in 'EVERY conversation' — this could lead to frequent autonomous activity. The document does not describe whether those periodic heartbeats run entirely locally, whether they reach remote endpoints, or what data is transmitted during GitHub sync.
Install Mechanism
The registry's install spec uses 'uv' with package 'focalpoint', while the SKILL.md shows 'pip install focalpoint' and links to a PyPI page for 'fpms'. These inconsistencies (uv vs pip, focalpoint vs fpms vs fpms on PyPI) are red flags: the install mechanism is not clearly specified and could point to a poorly-documented or misconfigured package. No code files are bundled in the skill, so the installer will be the primary source of code — verify the upstream package before running it.
Credentials
The skill declares no required environment variables or credentials, yet advertises GitHub integration and auto-sync of issues. A GitHub sync normally requires a token or OAuth config; the absence of declared auth requirements is a mismatch. Either the feature is disabled by default, or the skill is omitting a needed credential requirement — this should be clarified before granting network or repo access.
Persistence & Privilege
The skill is not marked 'always:true' and is user-invocable, which is the expected default. However, the instructions push for automatic calls in every conversation and periodic heartbeat checks. Combined with the installation of a local MCP server binary, this gives the skill a persistent presence on the agent platform when enabled — reasonable for a memory tool but worth confirming (especially network behavior).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install fpms-memory
  3. After installation, invoke the skill by name or use /fpms-memory
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.2.0
**Major update: Improved install/setup, new description, and enhanced documentation.** - Updated description to emphasize proactive work tracking, alerts, and project continuity. - Installation now uses the focalpoint package and bin (was: fpms). - Updated Python requirement from python3.11 to python3. - Simplified setup instructions for easier use. - Added clear feature comparison against other memory tools. - Enhanced use case examples and tool documentation for better clarity.
v0.1.0
- Initial release of fpms-memory: a cognitive memory engine for AI agents. - Enables tracking of work items, risk detection, and context persistence across conversations. - Proactive heartbeat alerts help prevent context amnesia and detect at-risk or stale items. - Provides 18 MCP tools, including creating/updating tasks, logging decisions, and memory bootstrapping. - Includes clear setup instructions and recommended usage rules for integrating with AI workflows.
Metadata
Slug fpms-memory
Version 0.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Fpms Memory?

Cognitive memory engine — gives your AI persistent work tracking, proactive risk alerts, and cross-conversation continuity. Never lose track of projects again. It is an AI Agent Skill for Claude Code / OpenClaw, with 110 downloads so far.

How do I install Fpms Memory?

Run "/install fpms-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Fpms Memory free?

Yes, Fpms Memory is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Fpms Memory support?

Fpms Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Fpms Memory?

It is built and maintained by jeff0052 (@jeff0052); the current version is v0.2.0.

💬 Comments