Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

memorax-ai

@memorax-ai source repo

3 published skills

  1. ▌
    Use Dsh Harmony · memorax-ai bundle
    Install and operate dsh-harmony, choose between Source, Semantic, Loader, React-aware, and Studio Patches, author Patch provider plugins, inspect transformed runtime source, control order and enablement, and troubleshoot failed or incompatible Patches. Use when an agent is asked to install Harmony, modify DeepSeek Harness Host or WebUI plugins without forks, create, review, or debug Harmony providers, integrate dsh-harmony-react or Studio previews, or diagnose Harmony status, ordering, reload, version, selector, or profile issues.
    0
    installs
  2. ▌
    Use Dsh Patchouli · memorax-ai bundle
    Install and operate Patchouli for DeepSeek Harness, call its common update/retrieve/subscribe service, build and register memory or knowledge plugins and connectors, use the storage client or JSON-RPC protocol, configure the Rust backend and providers, and troubleshoot profile, daemon, routing, subscription, or consistency failures. Use when an agent is asked to install Patchouli, integrate it with DSH, implement a MemoryPlugin, add a connector or indexer, call storage CRUD, configure scope or consistency, or contribute to dsh-patchouli.
    0
    installs
  3. ▌
    Memorax Code · memorax-ai bundle
    Use this skill as the single router for persistent coding and repository-local memory. Invoke it whenever a request may involve prior-work knowledge, repository memory, reusable procedures or rules, durable profile or interaction preferences, or information worth retaining beyond the current task. This applies without memory wording, including habits, preferences, checklists, action sequences, prerequisites, gates, exceptions, validation rules, communication style, preferred language, or result presentation. Classify the request as coding memory, repository memory, personal procedure memory, personal profile memory, or no persistent memory, then route it to the matching operation. Invoking this router does not require coding-memory search. Reuse a relevant coding-memory result already retrieved in this conversation; otherwise let the matching operation decide on search. Prefer this router over underlying memory workflows. Ask one focused question only when memory authority remains ambiguous.
    0
    installs