agentleFS
HybridAIOneHybridAIOne/hybridclaw/skills/zoho/SKILL.md

zoho

Skill159 starsChanged 33 days agoMITView on GitHub

Use the configured Zoho MCP server for Zoho CRM, Desk, Mail, Calendar, Books, Projects, WorkDrive, Cliq, Campaigns, and related Zoho business workflows. Use when the user asks to search, summarize, create, update, schedule, send, invoice, escalate, or report on Zoho data through MCP.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for Zoho work through the configured Zoho MCP server.

    line 45
  2. Very specific:

    Use the HybridClaw MCP server configured as zoho.

    line 53
  3. Very specific:

    Prefer visible MCP tools named zoho__<tool> and follow each tool's schema.

    line 54
  4. Distinctive:

    If the server is configured under a different name, use that namespace only after confirming it is the Zoho MCP server.

    line 55
  5. Very specific:

    If no Zoho MCP tools are visible, tell the operator to run /mcp list, /mcp status zoho, or /mcp login zoho.

    line 57
  6. Distinctive:

    Do not ask for Zoho OAuth tokens, passwords, cookies, or refresh tokens in chat.

    line 59
  7. Very specific:

    Use sse instead of http only when Zoho's connection details specify SSE.

    line 73
  8. Distinctive:

    Start with a read or search tool to resolve exact IDs and current state.

    line 78
  9. Distinctive:

    Do not claim a write succeeded until the MCP tool returns a success result.

    line 85
  10. Distinctive:

    Treat reads, searches, and report generation as green.

    line 104
  11. Distinctive:

    Treat creates, updates, status changes, assignments, replies, sends, schedule changes, and invoice generation as amber.

    line 105
  12. Distinctive:

    Treat bulk deletion, permission/admin changes, payment or refund execution, mass messaging, and irreversible accounting changes as …

    line 107
  13. Distinctive:

    Never expose secrets or bearer tokens in outputs, logs, files, or command arguments.

    line 113

≈ “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

Zoho

Use this skill for Zoho work through the configured Zoho MCP server. The MCP server owns the exact Zoho app connections, OAuth scopes, tool schemas, and allowed actions.

Official reference: https://www.zoho.com/mcp/

Required Surface

  • Use the HybridClaw MCP server configured as zoho.
  • Prefer visible MCP tools named zoho__<tool> and follow each tool's schema.
  • If the server is configured under a different name, use that namespace only after confirming it is the Zoho MCP server.
  • If no Zoho MCP tools are visible, tell the operator to run /mcp list, /mcp status zoho, or /mcp login zoho.
  • Do not ask for Zoho OAuth tokens, passwords, cookies, or refresh tokens in chat. Do not use browser login or raw Zoho REST calls for normal skill work.

Setup Guidance

For a new connection, use the Zoho MCP endpoint details from Zoho MCP and store the server in HybridClaw as zoho:

/mcp add zoho {"transport":"http","url":"<zoho-mcp-server-url>","auth":"oauth","enabled":true}
/mcp login zoho
/mcp status zoho

Use sse instead of http only when Zoho's connection details specify SSE.

Default Workflow

  1. Identify the Zoho app, object type, record target, and requested action.
  2. Start with a read or search tool to resolve exact IDs and current state.
  3. For read-only requests, summarize the MCP result with record names, dates, statuses, owners, amounts, links, and IDs needed for follow-up actions.
  4. For writes, show the exact target and change, then wait for explicit confirmation before calling the MCP write tool.
  5. Execute multi-app workflows one confirmed write step at a time. Stop after the first failed step and report which steps did and did not run.
  6. Do not claim a write succeeded until the MCP tool returns a success result.

Task Routing

  • CRM and Bigin: leads, contacts, accounts, deals, stages, owners, notes, meetings, and follow-up tasks.
  • Desk: ticket lookup, thread summaries, status changes, assignments, and replies.
  • Mail, Calendar, and Cliq: searches and summaries are read-only; sending mail, scheduling events, or posting messages requires confirmation.
  • Books, Billing, and Expense: read invoices, bills, expenses, payments, and reports; creating invoices or expenses requires confirmation.
  • Projects and WorkDrive: task, project, milestone, file, and folder lookup; file moves or task edits require confirmation.
  • Creator and other configured apps: follow the MCP tool descriptions and prefer low-risk reads before any record mutation.

Safety Rules

  • Treat reads, searches, and report generation as green.
  • Treat creates, updates, status changes, assignments, replies, sends, schedule changes, and invoice generation as amber; confirm each operation.
  • Treat bulk deletion, permission/admin changes, payment or refund execution, mass messaging, and irreversible accounting changes as unsupported through this skill unless a separate operator-approved procedure exists.
  • Preserve user-level Zoho permissions. If MCP returns an OAuth, scope, permission, or login error, ask the operator to run /mcp login zoho or adjust Zoho MCP scopes; do not retry unrelated tools.
  • Never expose secrets or bearer tokens in outputs, logs, files, or command arguments.

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.