Tencent SkillHub · Developer Tools

ForesigxtMemory

Structured memory system for AI agents. Context death resilience (checkpoint/recover), structured storage, Obsidian-compatible markdown, and local semantic search.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Structured memory system for AI agents. Context death resilience (checkpoint/recover), structured storage, Obsidian-compatible markdown, and local semantic search.

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: INSTALL.md, SKILL.md, templates/daily.md, templates/decision.md, templates/episode.md, templates/handoff.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.0

Provenance

Publisher: azrijamil
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 30 sections Open source page

Foresigxt Memory

Structured memory system for AI agents.

Install

npm install -g @foresigxt/foresigxt-cli-memory

Option 1: Initialize New Vault

# Initialize vault (creates folder structure + templates) fsxmemory init ~/memory

Option 2: Use Existing Vault

For isolated workspace memory (each workspace has its own vault): # Create .env in workspace root echo 'FSXMEMORY_PATH=/path/to/workspace/memory' > .env # All agents in THIS workspace use this isolated vault fsxmemory stats # Works automatically! For shared memory across all workspaces: # Set global environment variable (in ~/.bashrc or ~/.zshrc) export FSXMEMORY_PATH=/path/to/shared/memory # All agents in ALL workspaces share the same vault Or: Use --vault flag for one-time override: fsxmemory stats --vault /path/to/other/vault

Store memories by type

# Types: fact, feeling, decision, lesson, commitment, preference, relationship, project, procedural, semantic, episodic fsxmemory remember decision "Use Postgres over SQLite" --content "Need concurrent writes for multi-agent setup" fsxmemory remember lesson "Context death is survivable" --content "Checkpoint before heavy work" fsxmemory remember relationship "Justin Dukes" --content "Client contact at Hale Pet Door" fsxmemory remember procedural "Deploy to Production" --content "1. Run tests 2. Build 3. Deploy" fsxmemory remember semantic "Event Loop Concept" --content "JavaScript's concurrency model..." fsxmemory remember episodic "First Production Deploy" --content "Deployed v2.0 today, team was nervous but it went well"

Quick capture to inbox

fsxmemory capture "TODO: Review PR tomorrow"

Search (requires qmd installed)

# Keyword search (fast) fsxmemory search "client contacts" # Semantic search (slower, more accurate) fsxmemory vsearch "what did we decide about the database"

Checkpoint (save state frequently)

fsxmemory checkpoint --working-on "PR review" --focus "type guards" --blocked "waiting for CI"

Recover (check on wake)

fsxmemory recover --clear # Shows: death time, last checkpoint, recent handoff

Handoff (before session end)

fsxmemory handoff \ --working-on "Foresigxt Memory improvements" \ --blocked "npm token" \ --next "publish to npm, create skill" \ --feeling "productive"

Recap (bootstrap new session)

fsxmemory recap # Shows: recent handoffs, active projects, pending commitments, lessons

Migration from Other Formats

Migrate existing vaults from OpenClaw, Obsidian, or other markdown-based systems:

Analyze First (Dry Run)

# See what would be changed without modifying files fsxmemory migrate --from openclaw --vault /path/to/vault --dry-run

Migrate with Backup

# Recommended: Creates automatic backup before migration fsxmemory migrate --from openclaw --vault /path/to/vault --backup # The migration: # ✅ Adds YAML frontmatter to all markdown files # ✅ Renames directories (procedural→procedures, semantic→knowledge, episodic→episodes) # ✅ Creates .fsxmemory.json config file # ✅ Preserves all content and custom categories # ✅ Creates timestamped backup for rollback

Rollback if Needed

# Restore from backup if something went wrong fsxmemory migrate --rollback --vault /path/to/vault

Migration Options

# Available source formats --from openclaw # OpenClaw vault format --from obsidian # Obsidian vault format --from generic # Generic markdown vault # Migration flags --dry-run # Preview changes without modifying files --backup # Create backup before migration (recommended) --force # Skip confirmation prompts --verbose # Show detailed progress --rollback # Restore from last backup

Example: Migrate OpenClaw Vault

# 1. Analyze first fsxmemory migrate --from openclaw --vault ~/.openclaw/workspace/memory --dry-run # 2. Run migration with backup fsxmemory migrate --from openclaw --vault ~/.openclaw/workspace/memory --backup --verbose # 3. Verify migration worked fsxmemory stats --vault ~/.openclaw/workspace/memory fsxmemory doctor --vault ~/.openclaw/workspace/memory Migration Speed: ~53 files in 0.07 seconds ⚡

Auto-linking

Wiki-link entity mentions in markdown files: # Link all files fsxmemory link --all # Link single file fsxmemory link memory/2024-01-15.md

Templates Reference

Foresigxt Memory includes structured templates for consistent documentation. Location: templates/ directory.

Available Templates

TemplateTypeUse ForSectionsdecision.mddecisionKey choices, architecture decisionsContext, Options, Decision, Outcomeprocedure.mdproceduralHow-to guides, workflows, SOPsPurpose, Prerequisites, Steps, Pitfalls, Verificationknowledge.mdsemanticConcepts, definitions, mental modelsDefinition, Key Concepts, Examples, Why It Mattersepisode.mdepisodicEvents, experiences, meetingsWhat Happened, Context, Key Moments, Reflectionperson.mdpersonContacts, relationshipsContact, Role, Working With, Interactionsproject.mdprojectActive work, initiativesGoal, Status, Next Actions, Blockerslesson.mdlessonInsights, patterns learnedSituation, Lesson, Applicationhandoff.mdhandoffSession continuityWorking On, Context, Next Steps, Blockersdaily.mddailyDaily notes, journalFocus, Done, Notes

Template Usage

Templates are automatically selected by memory type: fsxmemory remember decision "Title" --content "..." # → templates/decision.md fsxmemory remember procedural "Title" --content "..." # → templates/procedure.md fsxmemory remember semantic "Title" --content "..." # → templates/knowledge.md fsxmemory remember episodic "Title" --content "..." # → templates/episode.md fsxmemory remember relationship "Name" --content "..." # → templates/person.md fsxmemory remember lesson "Title" --content "..." # → templates/lesson.md To view template structure: Read the template file in templates/ directory before creating a memory document. Template features: YAML frontmatter with metadata (title, date, type, status) Structured sections with placeholder guidance Wiki-link suggestions for connections Auto-generated tags

Folder Structure

vault/ ├── .fsxmemory/ # Internal state │ ├── last-checkpoint.json │ └── dirty-death.flag ├── decisions/ # Key choices with reasoning ├── lessons/ # Insights and patterns ├── people/ # One file per person ├── projects/ # Active work tracking ├── procedures/ # How-to guides and workflows ├── knowledge/ # Concepts and definitions ├── episodes/ # Personal experiences ├── handoffs/ # Session continuity ├── inbox/ # Quick captures └── templates/ # Document templates (9 types)

Best Practices

Checkpoint every 10-15 min during heavy work Handoff before session end — future you will thank you Recover on wake — check if last session died Use types — knowing WHAT you're storing helps WHERE to put it Wiki-link liberally — [[person-name]] builds your knowledge graph

Integration with qmd

Foresigxt Memory uses qmd for search: # Install qmd bun install -g github:tobi/qmd # Add vault as collection qmd collection add /path/to/vault --name my-memory --mask "**/*.md" # Update index qmd update && qmd embed

Configuration

Foresigxt Memory supports three ways to set the vault path (in order of precedence):

1. Command-line flag (highest priority)

fsxmemory stats --vault /path/to/vault

2. Environment variable

export FSXMEMORY_PATH=/path/to/memory fsxmemory stats

3. .env file (for workspace-isolated memory)

# Create .env in workspace root cat > .env << 'EOF' FSXMEMORY_PATH=/home/user/.openclaw/workspace/memory EOF # All fsxmemory commands in this workspace use this isolated vault fsxmemory stats fsxmemory checkpoint --working-on "task" Use .env when: ✅ Isolating workspace memory — Each project has its own separate vault ✅ Per-project configuration — Different agents in different workspaces use different vaults ✅ Portable — Workspace agents automatically use the right vault ✅ Git-safe — Add .env to .gitignore to protect paths Use global export when: ✅ Sharing memory across workspaces — All agents everywhere use one vault ✅ Centralized knowledge — One source of truth for all projects Environment Variables: FSXMEMORY_PATH — Vault path (can be set in shell or .env file)

Publishing Skill Package

To create a distributable skill package (includes SKILL.md and templates/): # Package the skill npm run package-skill # Output: dist-skill/fsxmemory-skill.zip (~8KB) Package contents: SKILL.md - Complete documentation and reference templates/ - All 9 memory templates .env.example - Configuration template INSTALL.md - Quick setup guide Distribution: Share the fsxmemory-skill.zip file with other agents/teams. They can extract it to get: Complete skill documentation Ready-to-use templates Configuration examples For OpenClaw/ClaudeHub: The packaged skill is ready for upload to skill repositories.

Links

npm: https://www.npmjs.com/package/@foresigxt/foresigxt-cli-memory GitHub: https://github.com/Foresigxt/foresigxt-cli-memory Issues: https://github.com/Foresigxt/foresigxt-cli-memory/issues

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

6 Docs

SKILL.md Primary doc
INSTALL.md Docs
templates/daily.md Docs
templates/decision.md Docs
templates/episode.md Docs
templates/handoff.md Docs