Project Trident

Give your AI agent genuine continuity, identity, and resilience across every session and deployment with a four-tier persistent memory stack.

This skill largely does what it claims (local SQLite + organized .md memory + optional semantic upgrade), but there are important mismatches to resolve before installing: - Credentials: The docs and code call for OpenAI/Anthropic/Gemini API access, Qdrant/FalkorDB cloud keys, and Git (SSH) push capability. The registry metadata lists no required env vars. Do not run the Layer 0.5 cron or embedding scripts until you have validated where and how API keys/SSH keys are provided and stored. - Review scripts: Inspect scripts/migrate-existing-memory.sh and scripts/template-integrity-check.sh line-by-line in a safe environment before running. Although the migration script promises backups, verify the backup location and test the --dry-run path first. - Network installs: The docs recommend curl | sh installers and downloading binaries from GitHub. Treat these as high-risk — prefer to manually download and verify checksums, or run in an isolated/test environment. - Git push risk: The example Layer 2 cron runs git add/commit/push; confirm your configured remote and credentials and consider adding a restrictive .gitignore (the docs include one example). If you want local-only memory, skip configuring remote pushes. - Start in a sandbox: Test Trident Lite on a throwaway workspace or VM, with cron jobs disabled, to validate behavior and outputs. Only enable autonomous cron runs and remote services once you confirm the behavior and supply appropriate credentials. If you want, I can: (a) list the exact lines in the included scripts that modify files or run network installs, (b) extract all places the SKILL.md references external endpoints/APIs and produce a checklist of credentials to supply, or (c) walk you through a safe, minimal manual installation sequence.

Type: OpenClaw Skill Name: project-trident-skill Version: 2.0.1 Project Trident is a sophisticated memory persistence framework designed to provide AI agents with long-term continuity and identity. The bundle consists of detailed documentation, architectural guides, and shell scripts for migrating existing memory and verifying the integrity of agent prompts via SHA256 hashes (template-integrity-check.sh). While the skill requires broad permissions to manage files and cron jobs, its behavior is transparently documented and strictly aligned with its stated purpose of hierarchical memory curation. No evidence of malicious intent, data exfiltration, or unauthorized remote execution was found.