hermes-skills/architecture/wealth-mcp-architecture/SKILL.md
WEALTH MCP physics-inspired redesign — 50 tools to 32 atomic tools + 8 prompts + 20+ resources. Tool/prompt/resource primitive allocation for capital intelligence MCP servers.
npx skillsauth add ariffazil/openclaw-workspace wealth-mcp-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
DITEMPA BUKAN DIBERI — Forged, Not Given
WEALTH MCP exposes 50 tools via @mcp.tool() decorators — everything dumped as tools: atomic calculators, orchestration wrappers, reasoning workflows, and duplicate aliases. MCP has 3 primitives:
| Primitive | Purpose | Should contain | |---|---|---| | tool | Atomic actions/computations | Calculate, validate, fetch, write | | prompt | Reasoning templates | Orchestration rituals, multi-step judgments | | resource | Readable knowledge/state | Schemas, formulas, policies, ontology |
wealth_<dimension>_<operation>
See the full blueprint at: /root/WEALTH/docs/WEALTH_MCP_ARCHITECTURE.md
| Category | Before | After | |---|---|---| | Tools | 50 | 32 | | Prompts | 0 | 8 | | Resources | 7 | 20+ |
Phase 1 (low risk): Rename V2_CANONICAL_MAP keys only Phase 2 (medium risk): Demote umbrella tools to prompts Phase 3 (low risk): Register resources Phase 4: Deploy + verify initialize handshake
development
Governed intelligence skill for AAA as the abstraction, attestation, and abduction control plane across arifOS, APEX, A-FORGE, GEOX, WEALTH, WELL, and the ariffazil profile repository. Use when the user asks to explain or design AAA, route agentic work, reduce chaos/entropy in an arifOS federation task, create AREP/task declarations, classify risk, plan multi-repo changes, review governance boundaries, or translate human intent into evidence-backed, authority-safe, recursively agentic workflows. Provides deterministic F1-F13 floor checking, bounded abduction, and FederationReceipt composition.
development
Check every skill’s “use when” and “do not use when” clauses for collisions, missing negatives, and vague verbs like “help,” “assist,” or “improve.” Load when linting, reviewing, or validating trigger boundaries.
development
Bootstrap, design, and package new skills. Load when capturing user intent for a new skill or drafting its initial instruction framework.
content-media
Diagnose which federation services are up, down, or drifting. Produce a prioritized remediation plan.