agentleFS
Sign inStart free
stardustaistardustai/stardust-skills/skills/fxiaoke-crm-cli/SKILL.md

fxiaoke-crm-cli

Skill0 starsChanged 2 months agoMITView on GitHub

Use for Fxiaoke or 纷享销客 CRM tasks, including records, customers, contacts, opportunities, contracts, deal cycles, conversion, sales orders, delivery, payments, receivables, follow-ups, statistics, and writes through the official sharecrm CLI.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat Fxiaoke CRM as the fact source and use the official sharecrm CLI.

    line 13
  2. Very specific:

    Verify the current remote command surface with sharecrm --help and the relevant subcommand --help before relying on syntax.

    line 23
  3. Distinctive:

    Before any CRM create, update, delete, follow-up, or other write, show the exact intended change and obtain explicit confirmation …

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fxiaoke CRM CLI

Treat Fxiaoke CRM as the fact source and use the official sharecrm CLI. Results are limited to the authenticated user's CRM permissions. Never ask for tokens, secrets, cookies, credentials, or manual token paste.

Workflow

  1. Check authentication:
sharecrm auth status
  1. Verify the current remote command surface with sharecrm --help and the relevant subcommand --help before relying on syntax.
  2. Inspect the live object schema before querying:
sharecrm data describe get -d '{"apiName":"ContractObj"}'

The following legacy form is incomplete and must not be run because it omits the required payload:

sharecrm data describe get
  1. Query records using the live object, field names, and options. Default to read-only work. Page with LIMIT 50 OFFSET n until .queryMeta.returnedCount and .queryMeta.totalNumber show the result set is complete.
  2. Before any CRM create, update, delete, follow-up, or other write, show the exact intended change and obtain explicit confirmation immediately before executing it.

Tenant schemas and CLI commands can change. Never guess fields, option values, or write syntax. For every metric, disclose the date range and timezone, source object, date field, metric field, status field and filter, included records, formula, and numerator/denominator when applicable.

See CLI reference for commands, metric recipes, examples, and troubleshooting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free