Miyamura80Miyamura80/MCP-Template/skills/gmail-mcp/SKILL.md

gmail-mcp

Skill1 starsChanged 5 months agoMITView on GitHub

Triage and curate a Gmail inbox by connecting to the GmailMCP server over MCP and calling its typed tools.

In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent.mdcCursor rule
- .cursor/rules/coding_style.mdcCursor rule
- .cursor/rules/commit_msg.mdcCursor rule
- .cursor/rules/common.mdcCursor rule
- .cursor/rules/deprecated.mdcCursor rule
- .cursor/rules/github_actions.mdcCursor rule
- .cursor/rules/langfuse.mdcCursor rule
- .cursor/rules/llm.mdcCursor rule
- .cursor/rules/long_run_code.mdcCursor rule
- .cursor/rules/makefile-commands.mdCursor rule
- .cursor/rules/package-management.mdCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typing.mdcCursor rule
- .cursor/rules/uv.mdcCursor rule
- frontend-design-principlesSkill
- goose-gui-e2eSkill
- local-sandboxSkill
- manage-agent-configSkill
- new-agent-ruleSkill
- onboardingSkill
- push-releaseSkill
- cleanupSkill
- code-qualitySkill
- prek-precommit-hookSkill
- thermo-nuclear-code-quality-reviewSkill
- usageSkill
- waitSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Add the MCP server to your client, then discover its tools.
line 14
Very specific:
Call a tool with tools/call and typed JSON arguments.
line 23

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

GmailMCP

GmailMCP is a Model Context Protocol (MCP) server. Use it to rank, triage, and draft replies for a Gmail inbox. The same tools are also reachable over a CLI and a plain HTTP API; behaviour is identical across all three transports.

Connect

Add the MCP server to your client, then discover its tools.

Endpoint (streamable HTTP): https://mcp.gmailmcp.com/mcp
Server name: gmail-mcp
Discovery metadata: https://gmailmcp.com/.well-known/mcp.json

Use

List the available tools with the MCP tools/list method.

Call a tool with tools/call and typed JSON arguments. For example, to triage the inbox:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gmail_curate_inbox",
    "arguments": { "limit": 3 }
  }
}

The server returns structured output (e.g. threads ranked by an importance score, with a flag for whether a draft reply was prepared).

Learn more

Full description for LLMs: https://gmailmcp.com/llms-full.txt
Human documentation: https://gmailmcp.com/docs
Source code: https://github.com/Miyamura80/MCP-Template

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