How do I install the Gescall Back skill?

Run npx skillmds@latest add tomevault-io/gescall-back in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gescall Back safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gescall Back?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gescall Back free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gescall Back?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gescall Back by tomevault-io — Agent Skill

Name: Gescall Back
Author: tomevault-io

Gescall Back

Guides work on the GesCall Node.js Express backend in back/ (API routes, Socket.IO, PostgreSQL, migrations, .env). Use when editing back/, server.js, routes under /api, sockets, migrations, or when the user mentions backend, API, or port 3001. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

GesCall backend (back/)

Scope

Work only inside back/ unless the task explicitly spans dialer, frontend, or deploy. The repo root is not an npm package — always cd back before npm scripts.

Commands

cd back && npm run dev    # nodemon, localhost:3001

There is no project-wide test, lint, or typecheck; do not add or run these unless the user asks.

Environment

back/.env: Loaded manually in server.js with fs + dotenv.parse (not dotenv.config()).
Go dialer reads the same file at the hardcoded path /opt/gescall/back/.env — keep variable names and paths consistent when changing env layout.
Migrations (JS under back/migrations/) parse .env the same way before requiring pgDatabase. Standalone node -e scripts that import pgDatabase without that pattern will fail.

Architecture shortcuts

Concern	Where
HTTP API	Routes under `/api/*`, JWT via `middleware/jwtAuth.js` (login and pubkey excluded as documented in AGENTS.md)
Realtime	`sockets/index.js` (not all logic in `server.js`)
DB access	`pgDatabase` — `query(text, params)` and `pool` (large pool, default not 10)
Swagger	`/api/docs`, `/api/docs.json`
One-off ops	`back/cli/`

Migrations

Numbered JS migrations: back/migrations/NNN_<name>.js.
Run from back/: node migrations/<name>.js.
Mixed with raw .sql in the same tree — check format before editing.

Vicidial / legacy

services/vicidialApi.js and config/vicidial.js exist as fallback; primary data path is native PostgreSQL. Prefer PG unless the task is explicitly Vicidial-related.

Full repo context

For end-to-end call flow, frontend triple-service pattern, PM2, and infrastructure, read AGENTS.md at the repository root.

Source: Lecmbogota/gescall — distributed by TomeVault.

---name: gescall-backdescription: Guides work on the GesCall Node.js Express backend in back/ (API routes, Socket.IO, PostgreSQL, migrations, .env). Use when editing back/, server.js, routes under /api, sockets, migrations, or when the user mentions backend, API, or port 3001. Use when this capability is needed.---# GesCall backend (back/)## ScopeWork only inside `back/` unless the task explicitly spans dialer, frontend, or deploy. The repo root is not an npm package — always `cd back` before `npm` scripts.## Commands```bashcd back && npm run dev # nodemon, localhost:3001```There is no project-wide test, lint, or typecheck; do not add or run these unless the user asks.## Environment- **`back/.env`**: Loaded manually in `server.js` with `fs` + `dotenv.parse` (not `dotenv.config()`).- **Go dialer** reads the same file at the hardcoded path `/opt/gescall/back/.env` — keep variable names and paths consistent when changing env layout.- **Migrations** (JS under `back/migrations/`) parse `.env` the same way before requiring `pgDatabase`. Standalone `node -e` scripts that import `pgDatabase` without that pattern will fail.## Architecture shortcuts| Concern | Where ||--------|--------|| HTTP API | Routes under `/api/*`, JWT via `middleware/jwtAuth.js` (login and pubkey excluded as documented in AGENTS.md) || Realtime | `sockets/index.js` (not all logic in `server.js`) || DB access | `pgDatabase` — `query(text, params)` and `pool` (large pool, default not 10) || Swagger | `/api/docs`, `/api/docs.json` || One-off ops | `back/cli/` |## Migrations- Numbered JS migrations: `back/migrations/NNN_<name>.js`.- Run from `back/`: `node migrations/<name>.js`.- Mixed with raw `.sql` in the same tree — check format before editing.## Vicidial / legacy`services/vicidialApi.js` and `config/vicidial.js` exist as fallback; primary data path is native PostgreSQL. Prefer PG unless the task is explicitly Vicidial-related.## Full repo contextFor end-to-end call flow, frontend triple-service pattern, PM2, and infrastructure, read [AGENTS.md](../../../AGENTS.md) at the repository root.---> Source: [Lecmbogota/gescall](https://github.com/Lecmbogota/gescall) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions