SkillFoxx

Cordys CRM Skill

A Cordys CRM skill that answers on clients, deals, contracts and payments and adapts the reply to the role of the asker

  • 74 ★ on the repository
  • Last commit
Skill

Broad access

Why this level

  • Reads customer, contract, payment and invoice data and can create and edit CRM records through API keys
  • Access keys sit in a `.env` file beside the skill
All reasons and checks

1panel-dev/cordyscrm-skillsAuthor:1Panel-dev

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/cordys-crm-skill

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Reads customer, contract, payment and invoice data and can create and edit CRM records through API keys
  • Access keys sit in a `.env` file beside the skill

This is third-party code. Review the repository files before installing.

What it does

The skill connects an agent to Cordys CRM through a thin `cordys.sh` shell wrapper that calls the REST API. The agent turns a plain-language request into a CRM call, while the skill works out who is asking and presents the answer from that role's viewpoint. Five roles are recognized: a salesperson gets a prioritized action list, a manager a team summary, a contracts administrator statuses and deadlines, and finance the chain from contract to payment and invoice. It runs as nine engines loaded by intent. At startup only the roles engine of about 150 lines loads, and the rest attach on demand: queries, the lead-to-cash chain, the funnel, intents, approvals, writes, output formatting and gap detection. The gap engine finds leads stuck beyond 30 days, opportunities without a contract, contracts without a payment plan and unpaid invoices. Writes are guarded: the skill fetches the object form, validates fields, writes and rechecks the result, and deletion is forbidden. Requests go only to the domain set in `CORDYS_CRM_DOMAIN`, and keys sit in `.env` and never reach the output.

Who it is for. Sales reps, department heads and finance staff at companies running Cordys CRM who want to query the CRM in plain speech.

Good fit when

  • A rep starts the morning by asking what to do today and gets a prioritized list across their leads and deals
  • A department head asks whose conversion dropped and drills from the team summary to a specific rep
  • You need to trace one deal from lead to invoice and see where the chain is broken, for example a missing payment plan
  • Finance needs a receivables overview and a collection queue for overdue payments

Not a fit when

  • You do not use Cordys CRM: the skill works only with its REST API
  • You need the agent to delete records: the skill forbids any deletion
  • Access keys cannot be stored in `.env` beside the skill

Example request

Show me what to do today across my leads and deals, and flag the ones stuck longer than 30 days

Limitations

  • It needs the keys `CORDYS_ACCESS_KEY` and `CORDYS_SECRET_KEY` and the address `CORDYS_CRM_DOMAIN`, stored in `.env` inside the skill folder.
  • Install is described for OpenClaw and WorkBuddy: through `clawdhub install cordys-crm`, by copying the folder, or as a zip for the WorkBuddy marketplace.
  • The documentation is in Chinese with no Russian version.
  • Roles are detected from the CRM profile, and nonstandard job titles are mapped with `ROLE_MAP`.

How to disable. Delete the cordys-crm skill folder from the agent's skills directory, for example `~/.openclaw/workspace/skills/`. The `.env` file with the keys goes with it. Revoke the keys in Cordys CRM if they are no longer needed.

FAQ

How do I install the Cordys CRM skill?

Run clawdhub install cordys-crm or copy skills/cordys-crm from the repository into the agent's skills directory. Then fill `.env` with the keys and the CRM address.

What does it need to connect?

An access key, a secret key and the address of your Cordys CRM instance. The variables are `CORDYS_ACCESS_KEY`, `CORDYS_SECRET_KEY` and `CORDYS_CRM_DOMAIN`.

Can the skill change data in the CRM?

Yes, it creates and edits records and converts leads, but it fetches the form and validates fields before writing and rechecks the result after. Deletion is forbidden.

What is L2C in this skill?

It is the lead-to-cash chain: lead, customer, opportunity, quote, contract, order, payment plan, payment and invoice. The skill looks for gaps in it, such as an opportunity with no contract.

Does the skill work with Claude Code?

The README describes install for OpenClaw and WorkBuddy. The skill is a folder with `SKILL.md`, so it can also go into another agent's skills folder, but that path is not documented.

Discussion

No questions or reviews yet.

Skills
Russian stack

A skill for agent work with the amoCRM API v4: search, create and update deals, contacts, companies, tasks and notes

SkillBroad access
Official

Zapier's GTM team skills for coding agents: marketing campaigns, lead work, customer stories and support tickets

SkillBroad access362
Official

RetailCRM plugin for Claude Code and Codex: a remote MCP server with GraphQL access to the CRM and a skill with safe-use rules

PluginBroad access3

Two LinkedIn skills via Linked API: people and company search, messages, posts and a lead pipeline with connection invites.

SkillBroad access110

README in short

The repository presents the skill as an AI assistant for CRM that speaks plainly and respects the role of the asker. It describes five roles and their view of the same data, an architecture of nine lazily loaded engines and the lead-to-cash chain with examples of breaks. The quick start gives install through clawdhub, a manual OpenClaw install and packaging for WorkBuddy, then three lines of configuration. Security principles close it: one domain for requests, key isolation, write protection.

README badge

Report a problem