Mx Space Remote Db Access logo

Mx Space Remote Db Access

Community
Innei
mx-space-remote-db-access

Access the remote mx-space PostgreSQL through ssh to the swarm host, then docker exec into the Postgres container and run psql inside the container. Use for inspecting tables, sampling rows, validating topic assignments, and performing guarded updates in the specific mx-space deployment pattern where direct host-level Postgres access is unreliable.

Overview

PublisherInnei
RepositorySKILL
Skill namemx-space-remote-db-access
Stars
81
Forks
2
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Innei on GitHub. Read the source before you install it.

Installation

Install the Mx Space Remote Db Access AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Innei/SKILL.git /tmp/SKILL
mkdir -p .claude/skills
cp -r /tmp/SKILL/skills/infrastructure/mx-space-remote-db-access .claude/skills/mx-space-remote-db-access
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mx Space Remote Db Access in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mx Space Remote Db Access on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mx Space Remote Db Access is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

mx-space Remote DB Access

Use this skill when inspecting or updating the remote mx-space PostgreSQL via the swarm host.

This deployment migrated MongoDB → PostgreSQL. Older notes referencing mongosh, collections, or camelCase fields are stale.

Deployment-specific facts

FactValue
Databasemx_core
Rolemxpostgres role does not exist
Container name patternmx-space-pg-* (dynamic swarm task suffix; resolve via grep '^mx-space-pg-')
In-container envPOSTGRES_USER / POSTGRES_PASSWORD / POSTGRES_DB already set, so psql -U mx -d mx_core works without PGPASSWORD
Host port forwardingunreliable in this deployment — stay inside docker exec

Quick start

bash
PG_CONTAINER=$(ssh -p "$SSH_PORT" "$SSH_USER@$SSH_HOST" \
  "docker ps --format '{{.Names}}' | grep '^mx-space-pg-' | head -1")

ssh -p "$SSH_PORT" "$SSH_USER@$SSH_HOST" \
  "docker exec '$PG_CONTAINER' psql -U mx -d mx_core -c 'SELECT 1;'"

For multi-statement queries pipe through docker exec -i ... psql <<'EOF' ... EOF.

Table of Contents

TopicReference
Full table catalog grouped by domain (content / ai / auth / ops / migration)references/tables.md
Topic / notes relation, guarded UPDATE templatereferences/topic-workflow.md

Schema conventions worth remembering

  • All id-shaped columns (id, topic_id, ref_id, category_id) are text (snowflake / cuid) — quote them.
  • Column names are snake_case. Don't paste old camelCase Mongo fields into SQL.
  • Polymorphic refs use the (ref_type, ref_id) pair (see comments, recentlies, drafts, ai_translations, search_documents).

Update rules

Writes only after explicit user approval. Filter every write with both a null guard (e.g. topic_id IS NULL) and an explicit id list, wrap in a transaction, and verify immediately after.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Mx Space Remote Db Access AI skill do?

Access the remote mx-space PostgreSQL through ssh to the swarm host, then docker exec into the Postgres container and run psql inside the container. Use for inspecting tables, sampling rows, validating topic assignments, and performing guarded updates in the specific mx-space deployment pattern where direct host-level Postgres access is unreliable.

Why use Mx Space Remote Db Access on TypingMind?

Because you install it once and use it with any model. Mx Space Remote Db Access is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mx Space Remote Db Access in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Innei/SKILL/tree/main/skills/infrastructure/mx-space-remote-db-access. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Mx Space Remote Db Access?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mx Space Remote Db Access?

As many as you like. As long as a model supports skills, you can use Mx Space Remote Db Access with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mx Space Remote Db Access AI skill free?

It is published on GitHub by Innei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇