E2E
sendou-ink/sendou.ink
Run, debug, and manage Playwright e2e tests. An agent skill from sendou-ink/sendou.ink.
Diagnoses marchat client and server issues using -doctor, env configuration, and logs.
Install Debugging Marchat
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Cod-e-Codes/marchat debugging-marchat --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/debugging-marchat .claude/skills/debugging-marchat && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .claude/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchatType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Cod-e-Codes/marchat debugging-marchat --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/debugging-marchat .agents/skills/debugging-marchat && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .agents/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Cod-e-Codes/marchat debugging-marchat --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/debugging-marchat .cursor/skills/debugging-marchat && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .cursor/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Cod-e-Codes/marchat.git --path .cursor/skills/debugging-marchat--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Cod-e-Codes/marchat debugging-marchat --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/debugging-marchat .gemini/skills/debugging-marchat && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .gemini/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Cod-e-Codes/marchat debugging-marchatInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/debugging-marchat .github/skills/debugging-marchat && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .github/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Cod-e-Codes/marchat debugging-marchat --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cod-e-Codes/marchat.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/debugging-marchat .opencode/skills/debugging-marchat && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-marchat" agent skill from https://github.com/Cod-e-Codes/marchat/tree/main/.cursor/skills/debugging-marchat into .opencode/skills/debugging-marchat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-marchat", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-marchat- GitHub stars
- 137
- Token cost
- ~668 tokens
- SKILL.md length
- 253 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnoses marchat client and server issues using -doctor, env configuration, and logs.
- Works in 4 steps: Reproduce with minimal steps. → Run -doctor on client and server. → Read relevant test file for expected… → …
- Debugging connection failures
- SKILL.md covers Doctor (first step), Common issues, WebSocket and Logging, plus 1 more section
- Calls go; needs MARCHAT_GLOBAL_E2E_KEY
What it does
Debugging Marchat is an agent skill from Cod-e-Codes/marchat. Diagnoses marchat client and server issues using -doctor, env configuration, and logs. Use when debugging connection failures, E2E decryption, database DSN, handshake errors, or when the user mentions doctor, diagnostics, or MARCHAT environment variables.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging, End-to-end testing and Secrets management. It works with MySQL and SQLite. The repository describes itself as: Terminal chat for developers: Go WebSocket server + Bubble Tea TUI client, optional E2E, reactions, DMs, channels, plugins, files, code snippets, admin UI. Backends: SQLite… The licence is MIT.
When your agent uses it
- Debugging connection failures
- Handshake errors
- The user mentions doctor
- MARCHAT environment variables
Example prompts
- “Use the debugging-marchat skill to diagnose marchat client and server issues using -doctor, env configuration, and logs”
- “/debugging-marchat”
Requirements
- Docker
- A credential in MARCHAT_GLOBAL_E2E_KEY
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Reproduce with minimal steps.
- Run -doctor on client and server.
- Read relevant test file for expected behavior before changing production code.
- Fix root cause; add a regression test (testing-marchat).
What it can do on your machine
Read from SKILL.md and the folder at commit 3440f09. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
MARCHAT_GLOBAL_E2E_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Marchat loads about 668 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 253 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:20
r doctor lists `MARCHAT_*` after `config/.env` load (`godotenv.Overload`: file wins on same key).
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Cod-e-Codes/marchat at commit 3440f09, republished under its MIT licence (© Cod-e-Codes). 253 words, ~668 tokens.
Download SKILL.mdSave it as
.claude/skills/debugging-marchat/SKILL.md (or your agent's skills folder).- name
- debugging-marchat
- description
- Diagnoses marchat client and server issues using -doctor, env configuration, and logs. Use when debugging connection failures, E2E decryption, database DSN, handshake errors, or when the user mentions doctor, diagnostics, or MARCHAT_ environment variables.
Debugging marchat
Doctor (first step)
| Binary | Command |
|---|---|
| Client | go run ./client -doctor or marchat-client -doctor |
| Server | go run ./cmd/server -doctor or marchat-server -doctor |
| JSON | Add -doctor-json (plain JSON; no TTY colors) |
Server doctor lists MARCHAT_* after config/.env load (godotenv.Overload: file wins on same key).
Skip GitHub release compare in tests or offline:
export MARCHAT_DOCTOR_NO_NETWORK=1Implementation: internal/doctor/. DB dialect and DSN shape checks live there and in server/db_dialect.go.
Common issues
| Symptom | Check |
|---|---|
| Handshake rejected / username taken | Reserved names; duplicate connection; server hub lock |
| WSS behind proxy | deploy/, docker-compose.proxy.yml, README proxy section; client WSS URL |
| E2E decrypt fails | Same global key on all clients (MARCHAT_GLOBAL_E2E_KEY or shared keystore.dat); not X25519 per-user |
| Postgres boolean errors | Dialect boolean helpers in server/db_dialect.go (:search, pin toggle) |
| MySQL time parsing | mysql.Config with parseTime=true in InitDB |
| SQLite path vs remote DSN | MARCHAT_DB_PATH; mysql: / postgres: prefixes for driver detection |
SQLite SQLITE_BUSY / missing messages under load | Confirm InitDB DSN pragmas (_busy_timeout, WAL) and writer MaxOpenConns(1); not one-shot PRAGMA alone (#118). Health/admin read tail latency under writes: file-backed reader pool via dbRead (#126) |
| Plugin disable race | StopPlugin waits for stdout/stderr readers (plugin/host) |
| Rate limit | server/loadverify_ratelimit_test.go constants match client.go read pump |
WebSocket
- Serialized writes per connection (
server/client.go). - Origin checks use parsed hostnames; optional
MARCHAT_ALLOWED_ORIGINS. - Trusted proxy headers:
MARCHAT_TRUSTED_PROXIESforX-Forwarded-For/X-Real-IP.
Logging
Never log passphrases, admin keys, session secrets, or raw E2E keys.
Workflow
- Reproduce with minimal steps.
- Run
-doctoron client and server. - Read relevant test file for expected behavior before changing production code.
- Fix root cause; add a regression test (
testing-marchat).
© Cod-e-Codes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/debugging-marchat of Cod-e-Codes/marchat.
Open the folder on GitHubat commit 3440f09
Compare with similar skills
Debugging Marchat next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Marchat this skillCod-e-Codes/marchat | 137 | — | ~668 | Automated safety check: Notes | MIT | |
| E2Esendou-ink/sendou.ink | 297 | — | ~2.1k | Automated safety check: Notes | AGPL-3.0 | |
| Smt E2E Dataflow DebuggingGoogleCloudPlatform/DataflowTemplates | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Golang Databaseunxed/f4 | 240 | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Alefxberg-io/alef | 100 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Odc DebuggingDouglasNeuroInformatics/OpenDataCapture | 119 | — | ~2.8k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Smt E2E Dataflow Debugging
GoogleCloudPlatform/DataflowTemplates
Debugs logical errors and data discrepancies in Dataflow templates by launching jobs via Terraform and comparing source (e.g.
Golang Database
unxed/f4
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context…
Alef
xberg-io/alef
Use Alef correctly for Rust-to-polyglot binding generation. An agent skill from xberg-io/alef.
Odc Debugging
DouglasNeuroInformatics/OpenDataCapture
What actually breaks in Open Data Capture — a failing build, lint, unit test or e2e run; a change with no visible effect; a suite that stays green after you broke the code on purpose; an error…
OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
More from Cod-e-Codes/marchat
All 11 skills in this repoDeveloping Marchat
Cod-e-Codes/marchat
Implements and refactors marchat Go code with project toolchain and quality gates.
Git Workflow Marchat
Cod-e-Codes/marchat
Drafts conventional commit messages and pull request bodies for marchat without committing or pushing unless explicitly requested.
Testing Marchat
Cod-e-Codes/marchat
Writes and runs marchat tests with race detection, coverage, and dialect smoke patterns.
Client Marchat
Cod-e-Codes/marchat
Implements marchat terminal client TUI, commands, keystore, and WebSocket client behavior.
Database Marchat
Cod-e-Codes/marchat
Changes marchat SQL schema and queries across SQLite, PostgreSQL, and MySQL using dialect helpers.
Plugins Marchat
Cod-e-Codes/marchat
Develops and maintains marchat plugins: SDK, host IPC, manager install path, store downloads, and Ed25519 licenses.
Related
Categories
Questions about Debugging Marchat
What does Debugging Marchat do?
Diagnoses marchat client and server issues using -doctor, env configuration, and logs. Debugging Marchat is an agent skill from Cod-e-Codes/marchat. Diagnoses marchat client and server issues using -doctor, env configuration, and logs.
When should I use Debugging Marchat?
Debugging Marchat fits situations like: debugging connection failures; handshake errors; the user mentions doctor; MARCHAT environment variables.
How do I install Debugging Marchat in Claude Code?
Run `npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a claude-code`. Or copy the skill folder (.cursor/skills/debugging-marchat in Cod-e-Codes/marchat) into .claude/skills/debugging-marchat in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Marchat in Codex?
Run `npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a codex`. Or copy the skill folder (.cursor/skills/debugging-marchat in Cod-e-Codes/marchat) into .agents/skills/debugging-marchat in your project. Codex loads it when a task matches its description.
Can I use Debugging Marchat in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Cod-e-Codes/marchat --skill debugging-marchat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-marchat, .gemini/skills/debugging-marchat, .github/skills/debugging-marchat and .opencode/skills/debugging-marchat in your project.
What does Debugging Marchat need to run?
Going by SKILL.md and its folder, Debugging Marchat needs the command-line tools its instructions call (go) and credentials named MARCHAT_GLOBAL_E2E_KEY. Our summary lists: Docker; A credential in MARCHAT_GLOBAL_E2E_KEY.
Does Debugging Marchat access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Marchat safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Debugging Marchat use?
Debugging Marchat is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debugging Marchat use?
About 668 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugging Marchat?
Skills that share tags, products or a category with Debugging Marchat: E2E (sendou-ink/sendou.ink, 297 stars), Smt E2E Dataflow Debugging (GoogleCloudPlatform/DataflowTemplates, 1.3k stars), Golang Database (unxed/f4, 240 stars) and Alef (xberg-io/alef, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Marchat?
Cod-e-Codes (a GitHub user) maintains it in Cod-e-Codes/marchat, which has 137 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.
Source: Cod-e-Codes/marchat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.