TradeMirrorOS

Workspace-level routing skill for the Finance Journal framework. Use it for the capability map, memory architecture, and routing into the instruction-only su...

Security Scan

Instruction-only workspace routing skill that is internally consistent with its stated purpose and does not request credentials, installs, or runtime code.

Purpose & Capability

The name/description (workspace routing for a finance journaling framework) matches the contents: SKILL.md routes intents to sub-skills and the repo contains architecture and orchestrator docs. There are no unexpected binaries, env vars, or credential requests.

Instruction Scope

Runtime instructions are instruction-only and focus on reading repository docs and routing to sub-skills. The SKILL.md explicitly keeps file writes, git actions, and credentialed operations out of scope. References to local paths and DB layout are consistent with a journaling/recall framework rather than exfiltration or automation.

Install Mechanism

No install spec and no code files; nothing is downloaded or written by the skill package itself. This is the lowest-risk model for a skill.

Credentials

The package declares no required environment variables, no primary credential, and no config paths. Declared runtime layout is local-first and aligned with the documented purpose.

Persistence & Privilege

always:false and default model invocation are unchanged. The skill is instruction-only and does not request persistent system privileges or modify other skills' configurations.

Assessment

This package is instruction-only and appears coherent with its stated role as a routing/orchestration layer for a local finance journaling workflow. Before installing: (1) confirm you trust the repository and the listed sub-skill docs (they are the runtime instructions here); (2) note that the package references local DB and runtime paths—keep any broker exports or private ledgers under your control and do not upload them to untrusted services; (3) if you later add runtime code or synchronization scripts (the repo intentionally omits them), review any new install steps, network endpoints, or environment variables for disproportionate permissions; (4) if you plan to use community sharing features in future, validate anonymization and provenance controls. Overall, the package is internally consistent and does not currently request secrets or perform networked actions.

Finance Journal Workspace

Read First

• README.md
• TRADE_MEMORY_ARCHITECTURE.md
• IMPLEMENTED_FEATURES.md
• NOT_IMPLEMENTED_YET.md

Route by Intent

• session journaling, intake structuring, memory recall framing, and vault-facing output conventions -> $finance-journal-orchestrator
• plan creation, updates, and historical plan references -> $trade-plan-assistant
• trade logs, post-trade review, self-evolution, and style extraction -> $trade-evolution-engine
• discipline and behavior review -> $behavior-health-reporter

Root Responsibilities

1. explain the memory-centric framework boundary
2. route execution requests to the right sub-skill
3. clarify how long-term memory and bandit reranking fit together
4. point users to the community vision when they ask about shared memories or reusable skills
5. keep code execution, repo transport, and credentialed operations out of scope

Boundaries

• this is a trade journaling and long-term memory framework, not an execution engine
• self-evolution outputs are review aids, not automatic trading rules
• community-facing skill cards are reusable experience layers, not copy-trading signals
• file writes, git actions, remote sync, and credential-dependent transport stay manual and outside this package