← Back to Skills Marketplace
480
Downloads
1
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install tricore
Description
TriCore Architecture - A deterministic (Code-First) three-layer memory and cognitive framework designed for low-resource servers/Agents. It includes the unde...
Usage Guidance
This package is internally consistent: it implements a local memory engine (tools/memctl.py), templates for planning/ReAct/self-evolution, and an installer that enforces use of the engine by modifying POLICY.md and OpenClaw config. Before installing, consider: 1) Back up POLICY.md and MEMORY.md (install will move/rename a large MEMORY.md). 2) Review tools/memctl.py and install.sh yourself (they are local and do not fetch remote code). 3) Be aware install.sh will call 'openclaw config set' to override compaction behavior and inject a Linter policy — this is intrusive and affects other skills; test installation in an isolated workspace or sandbox first. 4) The self-evolution skill uses edit/write permissions (it can modify code); only enable it if you trust the skill and are prepared to review/monitor automated code changes. 5) If you are unsure, run the installer manually in a throwaway environment, inspect the created files in memory/ and policy changes, and verify you can revert them with uninstall.sh.
Capability Analysis
Type: OpenClaw Skill
Name: tricore
Version: 1.0.1
This skill bundle is classified as suspicious due to its extensive use of highly privileged tools and its design to perform broad system modifications and agent self-modification. The `install.sh` script directly alters the agent's core `POLICY.md` and OpenClaw's `compaction.memoryFlush.prompt` configuration. Furthermore, the `cognitive-skills/self-evolution.md` skill explicitly instructs the agent to modify its own code and system configurations using powerful tools like `default_api:exec`, `default_api:edit`, and `default_api:write`. While the stated intent is architectural enforcement and self-improvement, these capabilities introduce a significant attack surface and high potential for unintended consequences or exploitation, even without clear evidence of intentional malicious behavior like data exfiltration or backdoor installation.
Capability Assessment
Purpose & Capability
The package implements a code-first memory manager (tools/memctl.py), cognitive-skill templates, and an installer — all consistent with a 'TriCore' memory/cognition framework. Requiring Python, adding memctl, and providing planning/React/self-evolution templates is proportional to the described purpose. However, the installer also injects system policy rules and overrides OpenClaw's compaction prompt (system-wide configuration), which is a stronger footprint than many memory helper skills would need.
Instruction Scope
SKILL.md and the included files explicitly instruct agents to forbid arbitrary file creation, route all persistence through memctl.py, run memctl.py lint for any automation, and use memory_search for retrieval. Those instructions align with the skill's goal (centralize memory), but they place strong constraints on normal agent behavior and tell the agent to read/migrate any existing MEMORY.md (migrate_legacy). The instructions do not request unexplained credentials or network exfiltration.
Install Mechanism
There is no remote download of code; install.sh copies files from the package into the workspace and runs local Python scripts. No external URLs, shorteners, or remote archives are fetched. That lowers supply-chain risk compared to fetching remote binaries. The script does call 'openclaw config set' (a system CLI) which is expected to configure OpenClaw but will fail if OpenClaw isn't present.
Credentials
The skill does not request environment variables, tokens, or credentials. It does, however, recommend (but not require) optional components like an 'agent-browser' and expects the agent to have exec/write/edit permissions to perform self-evolution — this is documented and consistent with the skill's self-modifying/evolution objectives.
Persistence & Privilege
The installer injects a TriCore block into POLICY.md and overrides OpenClaw's pre-compaction memory flush prompt (openclaw config set). Those are persistent, system-wide changes that affect global behavior and other skills. The skill also provides a self-evolution template that uses default_api:edit/write (ability to modify code). While these are coherent with a 'memory OS' designer's goals, they grant broad, persistent influence over the runtime and tooling and could lock or interfere with other workflows.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tricore - After installation, invoke the skill by name or use
/tricore - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Added pre-compaction override and bilingual support
v0.1.2
tricore v0.1.2 Changelog
- Added a “System Compatibility (Compaction Hook)” feature to TriCore architecture, automatically patching the OpenClaw prompt for memory compaction to prevent unauthorized file writing loops.
- Updated SKILL.md documentation to include details about this compaction hook and clarify its role in preventing HTTP 429 burst errors during memory flush.
- install.sh and uninstall.sh scripts updated to implement/handle the new compatibility mechanism.
- No breaking changes; existing usage is unaffected, but environments are now more robust against write-related compaction problems.
v0.1.1
TriCore 0.1.1 Changelog
- Added `uninstall.sh` for easier skill removal.
- Updated documentation for clarity and consistency in English.
- Improved and clarified the setup, operation, and compliance instructions across README and cognitive skill files.
- Enhanced guidance on using and enforcing `memctl.py`-based memory operations.
- Minor content and formatting improvements throughout.
v0.1.0
Initial release of TriCore: a deterministic, code-first memory and cognition architecture for low-resource Agents.
- Implements a strict three-layer memory system with unified management via memctl.py.
- Enforces memory access and updates exclusively through command-line tools and semantic search (memory_search), prohibiting ad-hoc file writing.
- Includes built-in linting to block non-compliant file operations or script automation.
- Provides a streamlined installation process with automatic migration of legacy memory files.
- Bundles core cognitive skill templates (planning, ReAct, self-evolution) optimized for the TriCore system.
- Designed for compatibility with OpenClaw (v2026+), Python 3.6+, and key system utilities.
Metadata
Frequently Asked Questions
What is TriCore?
TriCore Architecture - A deterministic (Code-First) three-layer memory and cognitive framework designed for low-resource servers/Agents. It includes the unde... It is an AI Agent Skill for Claude Code / OpenClaw, with 480 downloads so far.
How do I install TriCore?
Run "/install tricore" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is TriCore free?
Yes, TriCore is completely free (open-source). You can download, install and use it at no cost.
Which platforms does TriCore support?
TriCore is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created TriCore?
It is built and maintained by bertonhan (@bertonhan); the current version is v1.0.1.
More Skills