Assistant guides

Your coding assistant already knows how to work on DeskcommCRM.

Six guides teach Claude Code, Codex, Cursor, Antigravity and OpenCode to install the CRM, set up a client, read the metrics, tune the AI agent and contribute code — following the project's rules. No names to memorize: say what you want and the right guide kicks in on its own.

curl -fsSL https://raw.githubusercontent.com/melgarafael/DeskcommCRM/main/scripts/instalar-guias.sh | bash

How it works

  1. 1

    Install once

    One command makes the guides available in any folder on your computer, for every assistant.

  2. 2

    Start a new session

    Assistants read guides when a session starts. A conversation that was already open won't see what just arrived.

  3. 3

    Ask your own way

    “The agent is answering wrong.” The assistant recognizes the topic and follows the guide. You can also call it by name.

The guides

One guide for each job.

Four are for people who install and run the CRM, no coding required. Two are for people who work on the code.

Install and operate

/deskcomm-instalar

For CRM operators

Gets the CRM running on a VPS and looks after it: updates, backups, domain, WhatsApp and installation errors.

What it does

  • Walks you through the installation and runs the kit's scripts.
  • Fixes SSL, DNS, Supabase, proxy and AI key issues.
  • Updates, backs up and restores.

Ask like this

  • I want to install the CRM on my VPS
  • my site has no padlock
  • how do I back it up?

Who it's for: People who install it — technical or not — agencies and VPS operators.

View the guide on GitHub

Set up a client

/deskcomm-cliente-novo

For CRM operators

Builds a client's customer service by niche — clinic, real estate, services, courses, store — in the right order, through the screens.

What it does

  • Creates AI agents, routers and follow-ups.
  • Uploads the knowledge base and builds the pipeline.
  • Hands you ready-to-paste text and guides you to the test.

Ask like this

  • set up the CRM for a clinic
  • what prompt should I use for the real estate agency's AI agent?
  • I finished onboarding, now what?

Who it's for: Business owners, agencies and people implementing it for others.

View the guide on GitHub

Analyze the metrics

/deskcomm-metricas

For CRM operators

Reads your operation like a seasoned analyst: conversion, pipeline, response time, human handoff and AI cost.

What it does

  • Shows where the pipeline gets stuck and why conversion dropped.
  • Tells you what the AI costs and when customers talk the most.
  • States the yardstick and time zone behind every number.

Ask like this

  • is the agent selling?
  • why did conversion drop?
  • how much am I spending on AI?

Who it's for: Business owners, agencies and operators.

View the guide on GitHub

Tune the AI agent

/deskcomm-prompt

For CRM operators

Improves the prompt of an agent that isn't performing, like a senior prompt engineer — using your operation's data.

What it does

  • Diagnoses from the agent's runs, blocks and costs.
  • Writes the new version as a draft and tests it with the Test button.
  • Leaves Publish to you.

Ask like this

  • the agent sounds robotic
  • it makes up prices
  • improve the sales agent's prompt

Who it's for: Business owners, agencies and implementers.

View the guide on GitHub

Contribute code

/deskcomm-contribuir

For developers

Checks before your pull request what the maintainer checks after — so you avoid rework and rejected PRs.

What it does

  • Warns when your branch is behind main.
  • Asks for the migration, the missing test and the release fragment.
  • Shows how to prove the change on screen.

Ask like this

  • I'm going to open a PR
  • is my branch behind?
  • why did CI go red?

Who it's for: Contributors, especially from a fork, and agency developers.

View the guide on GitHub

Follow the code rules

/deskcomm-doutrina

For developers

Points to this repository's non-negotiable rules whenever someone writes or reviews code.

What it does

  • Tenant isolation with RLS.
  • Migration, baseline and manifest moving together.
  • What changes for people who already installed it on a VPS.

Ask like this

  • review this code
  • how do I create a migration here?
  • can I add this column?

Who it's for: Anyone — person or AI — writing code in the project.

View the guide on GitHub

In your assistant

How to use them in each one.

They all follow the same open guide standard (Agent Skills) and pick the guide on their own from the topic. What changes is where they look and how you call a guide by name.

Where it looks

In the project's .claude/skills folder and in your personal folder.

  • Project.claude/skills/
  • Global~/.claude/skills/
On its own
Reads each guide's description and triggers the one that matches your request.
By name

Type a slash and the name. Whatever follows goes along to the guide.

/deskcomm-instalar my domain is crm.mycompany.com
See the list

Shows every loaded guide.

/skills

Another assistant? Tools that follow the Agent Skills standard — like GitHub Copilot and Gemini CLI — usually read the .agents/skills folder, and the installer also links the guides into ~/.agents/skills.

Install

Two ways to get the guides.

If you haven't cloned the project yet, or you work from another folder, use the installer. If you're in an up-to-date clone, you already have everything.

In any folder

Recommended

Paste it into your computer's terminal — not the VPS. It works before you clone the project.

curl -fsSL https://raw.githubusercontent.com/melgarafael/DeskcommCRM/main/scripts/instalar-guias.sh | bash
  • Keeps a copy of just the guides in ~/.deskcomm/guias.
  • Links each guide into the folders assistants read: ~/.claude/skills, ~/.agents/skills and ~/.gemini/config/skills.
  • Never deletes a skill of yours with the same name: it warns and skips it.

To update, run the same command again.

To undo:

curl -fsSL https://raw.githubusercontent.com/melgarafael/DeskcommCRM/main/scripts/instalar-guias.sh | bash -s -- --remover

Inside a clone

The guides live in the repository itself. Open your assistant in the project folder and they're already there.

git clone https://github.com/melgarafael/DeskcommCRM.git
cd DeskcommCRM
  • They sit in .agents/skills, with a copy in .claude/skills for Claude Code.
  • Keep your branch up to date with main: on an old branch, the guides are old too.

On Windows, run it from Git Bash when the assistant is installed on Windows itself. Use WSL only if the assistant also runs inside WSL: there your home folder is the Linux one, which Windows apps don't read. Where the system can't create folder links, the installer copies the guides instead — then run the command again whenever you want to update.

For contributors

Changing a guide.

Guides are project code: they go in through a pull request and they have tests.

  1. 1

    Edit the source

    The file is .agents/skills/<guide>/SKILL.md. Keep the header description in quotes: a stray colon breaks strict parsers, and the guide disappears without a warning.

  2. 2

    Update the mirror

    Copies the guides into .claude/skills, the Claude Code folder.

    pnpm skills:sync
  3. 3

    Run the test

    Fails on an invalid header, an outdated mirror or a description that's too long.

    pnpm test:unit tests/unit/skills-embutidas.test.ts
  4. 4

    Try your version

    In Claude Code, a guide installed globally wins over the project's. Point the installer at your clone before testing.

    bash scripts/instalar-guias.sh --fonte .

Frequently asked questions

Do I need to know the guide's name?

No. The assistant picks the guide from what you ask. The name is for when you want to be sure which guide runs.

Will the assistant change my server on its own?

It follows your assistant's permissions: commands ask for your confirmation unless you've allowed them. In the prompt guide, publishing the agent's new version is always up to you.

Do the guides read my customers' conversations?

The metrics guide doesn't: it reads the database only with queries that sum and count, without opening message text or personal data. The prompt guide may read an excerpt when it's essential to see how the agent talks, and only with your knowledge: the messages the agent itself sent in a few recent conversations — not the customer's — without copying anything out of the session.

Does it work if I write in English or Spanish?

Yes. The guides are written in Portuguese, and the assistant follows them while answering in the language you write in.

I already have a skill with the same name. Now what?

The installer leaves it alone: it says it skipped it and carries on with the other guides.

I installed them and the guide doesn't show up.

Start a new assistant session. In Antigravity, also confirm that you trust the project folder: there, an untrusted folder doesn't load its guides.