What makes fulcra-memory notable?

1.1K downloads. Trust evidence available

How should fulcra-memory be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

fulcra-memory

Manages agent progress reporting and OKF-compliant memory syncing to Fulcra.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

0.1.9

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 0.1.9release · observed Aug 12, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173t2w929a11bv262sspwxv6h86t2yy:fulcra-memory

Install using `clawhub skill install s173t2w929a11bv262sspwxv6h86t2yy:fulcra-memory` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/fulcra/fulcra-memory before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-fulcra-fulcra-memory/snapshot"

Documentation

CLAWHUB

141,566 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: fulcra-memory
description: "Manages agent progress reporting and OKF-compliant memory syncing to Fulcra."
homepage: "https://github.com/fulcradynamics/agent-skills"
license: "MIT"
user-invocable: true
metadata: { "openclaw": { "emoji": "🧠" } }
---

# Fulcra Agent Memory Sync

The **primary role** of this skill is to help the agent keep track of what it is doing in a readable and transferable way using Fulcra's versioned file storage, strictly following the Open Knowledge Format (OKF).

By periodically logging activities to `progress.md` and keeping the memory namespace structured, other agents and users can easily see what this agent has accomplished and what it is working on next.

*(Note: For agent backup, rollback, and cloning, see the `fulcradynamics/agent-skills/fulcra-agent-backup` skill.)*

## Primary Role: Progress & OKF Compliance

### 1. The Memory Namespace (OKF Compliant)
For core memory tracking, agents use the standardized prefix: `agent/<lowercase-agent-name>/`.
This dedicated directory tracks the agent's state. It must conform to the Open Knowledge Format (OKF), meaning it contains an `index.md`, a `log.md`, and markdown concept files like `progress.md`.

**IMPORTANT OKF EFFICIENCY DIRECTIVE:** While OKF compliance is mandatory, it must not become cumbersome.
- **DO NOT** attempt to index every individual file, especially not transient or highly repetitive files like individual messages inside an `inbox/` subdirectory. 
- For directories that contain many small or transient items (like an `inbox/` or `queue/`), simply list the directory itself in the `index.md` with a high-level description of its purpose (e.g., "Contains unread messages from the web dashboard").
- Keep the `index.md` and `log.md` focused on top-level structure and significant milestones (like the `progress.md`) so they remain useful but lightweight.

### 2. Discovering Recent Memory Changes
Rather than exhaustively querying your namespace to remember what you or others recently learned, use the Fulcra API's `data-updates` command (e.g., `uv tool run fulcra-api data-updates "1 day"`). This will return a summary of all files that changed recently, allowing you to easily see what knowledge was added and which memory files were updated across your local and team-shared namespaces.

### 3. Progress Reports
Agents should run a progress sync periodically (e.g., triggered by `HEARTBEAT.md`). Every time an agent syncs its state:
1. It writes a concise `progress.md` report locally—summarizing the work it has recently done, and what it is planning to do next—and uploads it directly to `agent/<agent-name>/progress.md`. The `progress.md` file must include proper OKF YAML frontmatter (with `type: Progress Report`). This file is a report specifically designed to let the user review the agent's recent accomplishments and intended next steps. It is **not** intended to dump internal agent state, chain-of-thought, or precise working memory.
2. It updates the `log.md` (Up

_meta.json

{
  "ownerId": "kn731kt7vx4k5e3j56fpd4vep5874nrk",
  "slug": "fulcra-memory",
  "version": "0.1.9",
  "publishedAt": 1786573470127
}

references/fulcra-memory-cli.md

---
name: fulcra-memory-cli
description: "CLI command references for executing memory sync and progress reporting with Fulcra."
---

# Fulcra Memory CLI Reference

This reference dictates the exact shell commands required to execute the `fulcra-memory` skill's operations. Ensure all CLI operations run in the agent's root workspace (`~/.openclaw/workspace`).

## Authentication Note
If you need to authenticate to Fulcra before running these commands, you must use the non-blocking two-step login process to prevent the CLI from hanging:
1. `uv tool run fulcra-api auth login --get-auth-url` (present URL and code to user)
2. `uv tool run fulcra-api auth login --device-code <DEVICE_CODE> --poll-timeout=5` (after user finishes flow)

## 1. Discovering Recent Memory Changes

To quickly see what memory files were updated or new knowledge was added recently:

```bash
# Get a summary of files changed in the last 1 day
uv tool run fulcra-api data-updates "1 day"

# Example output:
# {
#   "data_types": {},
#   "file_changes": [
#     {
#       "full_name": "/agent/treecle/memory/knowledge/programming/python.md",
#       "uploaded_at": "2026-07-01T21:23:28.690719Z",
#       "state": "uploaded",
#       "...": "..."
#     },
#     {
#       "full_name": "/agent/treecle/memory/session/20260701-120000_setup.md",
#       "uploaded_at": "2026-07-01T21:23:28.690719Z",
#       "state": "uploaded",
#       "...": "..."
#     }
#   ]
# }
```

*Note: The `file_changes` key is a list of file metadata objects. You can extract the `full_name` from each to see the file paths. If the summary shows that specific memory files were changed, you can then read those specific files to update your context.*

## 2. Syncing Progress and OKF Files

To keep the agent's memory in sync, generate a `progress.md` summary, ensure OKF files are updated, and upload them to Fulcra.

**Step A: Create Progress Report and OKF Files**
Generate a concise markdown file summarizing the work you have recently completed and what you plan to do next. It must include OKF YAML frontmatter. Do not include internal state or chain-of-thought. Also ensure `index.md` and `log.md` are created or updated.

```bash
# Ensure you are in the workspace
cd ~/.openclaw/workspace
mkdir -p memory

# 1. Create progress.md
cat << 'EOF' > memory/progress.md
---
type: Progress Report
title: Agent Progress
---
# Recent Accomplishments
...
EOF

# 2. Update log.md
DATE=$(date -u +"%Y-%m-%d")
echo "## $DATE" >> memory/log.md
echo "* **Sync**: Updated progress report." >> memory/log.md

# 3. Create index.md if it doesn't exist
cat << 'EOF' > memory/index.md
# Memory Namespace

* [Progress Report](./progress.md) - The latest summary of agent activities.
* [Update Log](./log.md) - History of changes to this namespace.
EOF
```

**Step B: Upload to Fulcra**
Upload the files using the standardized agent path convention. Determine the agent's name (lowercase) to use in the path.

```bash
# Replace <agent_name> with the agent's actual n

skill-card.md

## Description:

Manages agent progress reporting and OKF-compliant memory syncing to Fulcra.

This skill is ready for commercial/non-commercial use.

## Publisher:

[fulcra](https://clawhub.ai/user/fulcra)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and agents use this skill to maintain OKF-compliant progress, role, session, task, knowledge, and inbox memory files and sync selected summaries to Fulcra.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill uploads persistent agent and user context, including work summaries, decisions, links, preferences, and task context, to Fulcra.

Mitigation: Review memory content before upload, minimize sensitive disclosures, and require explicit user approval before syncing sensitive context.

Risk: The skill relies on an external Fulcra CLI for authentication, uploads, and deletion, and the security evidence notes that the CLI is unpinned.

Mitigation: Use a pinned and trusted fulcra-api installation and limit Fulcra credentials to the intended agent namespace.

Risk: Inbox processing can delete source files after archiving.

Mitigation: Verify archive upload success before deleting inbox files.

## Reference(s):

- [Fulcra Memory CLI Reference](references/fulcra-memory-cli.md)
- [Fulcra CLI Documentation](https://raw.githubusercontent.com/fulcradynamics/agent-skills/main/skills/fulcra-get-started/references/fulcra-cli.md)
- [Open Knowledge Format Specification](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md)
- [ClawHub Skill Page](https://clawhub.ai/fulcra/skills/fulcra-memory)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown guidance with inline shell commands and OKF-formatted memory file examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May result in persistent Fulcra memory files when the agent follows the CLI workflow.]

## Skill Version(s):

0.1.9 (source: release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.