Google Contacts

Community

win4r

google_contacts

Search, view, create, update, and delete the user's Google Contacts.

Overview

Publisher	win4r
Repository	`MuseAI-Skills`
Skill name	`google_contacts`
Stars	382
Forks	116
Bundled files	2
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by win4r on GitHub. Read the source before you install it.

Installation

Install the Google Contacts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/win4r/MuseAI-Skills/tree/main/opt/hatch/skills/google-contacts
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/win4r/MuseAI-Skills.git /tmp/MuseAI-Skills
mkdir -p .claude/skills
cp -r /tmp/MuseAI-Skills/opt/hatch/skills/google-contacts .claude/skills/google_contacts

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Contacts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Contacts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Contacts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Google Contacts

Everything runs through hatch_gws_cli people <resource> <method> — resource and method as separate words, with parameters in a --params JSON object and, for creates and edits, a --json request body. The flows below give the exact command for each task, so start there; for a command's flags run hatch_gws_cli people <resource> <method> --help, and for a method's --params/--json shape run hatch_gws_cli schema people.people.searchContacts (and so on).

A contact's id is an opaque resourceName like people/c1234567890, and people/me is the connected account itself. Reads must name the fields they want: searches take a readMask, and get/connections list take a personFields mask (both a comma list like names,emailAddresses,phoneNumbers). Never invent a resourceName — carry the one a read returned straight through to the edit or delete.

Connecting

Contacts needs a one-time connect before commands return data. Run hatch_gws_cli people status. If it is not connected, post the exact connect_url it returns as [Connect Google Contacts](<connect_url>) and wait for the user to tap it. Don't invent a URL, send the user to Settings, or ask for credentials.

To disconnect, run hatch_gws_cli people disconnect and post its disconnect_url as [Disconnect Google Contacts](<disconnect_url>).

If a command reports an auth failure or not-connected, rerun status and follow the link it returns. If status is unavailable, say Google Contacts isn't available on this device and stop. Auth flows only through status and disconnect, with no hand-authored credential files or raw gws auth.

Common flows

Find a contact

Look someone up by name or email: people people searchContacts --params '{"query":"alice","readMask":"names,emailAddresses,phoneNumbers","pageSize":10}'.
Browse the whole address book: people people connections list --params '{"resourceName":"people/me","personFields":"names,emailAddresses,phoneNumbers","pageSize":50}'. Use this for "who's in my contacts" or to page through everyone.
One person's full detail, once you have their resourceName: people people get --params '{"resourceName":"people/<id>","personFields":"names,emailAddresses,phoneNumbers"}'.

Add a contact

people people createContact --json '{"names":[{"givenName":"Alice","familyName":"Smith"}],"emailAddresses":[{"value":"alice@example.com"}],"phoneNumbers":[{"value":"+15551234567"}]}'. A name is enough; add emailAddresses and phoneNumbers when the user gives them.

Edit a contact

people people updateContact --params '{"resourceName":"people/<id>","updatePersonFields":"emailAddresses"}' --json '{"etag":"<etag>","emailAddresses":[<the full list with your change>]}'.

Delete a contact

people people deleteContact --params '{"resourceName":"people/<id>"}'.

Rules

Contact creation, editing, and deletion may proceed from a clear, unambiguous user request without an additional confirmation. Resolve the exact person before editing or deleting.
Read before you edit or delete: resolve the person with a search or browse first, use the exact resourceName (and etag) that read returned, and never act on a contact you did not find. For an edit, include the fields you are keeping so an update does not drop them.
Talk to the user in plain language only. The commands and their JSON output are for you, not the user: keep them out of your replies — no command or flag (hatch_gws_cli, --params), no status word (not_connected, unavailable), no resourceName, and no API field (etag, page tokens) or raw JSON. A contact's own name, email, and phone number are what the user asked for, so keep those in your reply.
Never print tokens, secrets, or credential material. Redact them if they appear in tool output.
Read results add contact_source_updated_at with UTC and user-local forms when Google supplies a source update time. Birthdays remain calendar dates.

Limits

Contact groups and labels, "other contacts" (addresses auto-saved from mail, not full contacts), and directory or domain people are not first-class flows here. If a task needs one, check its shape with hatch_gws_cli schema people.<resource>.<method> and confirm before any change, but there is no seeded, tested recipe for it.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

eval/scenarios.yaml14 KB
manifest.yaml3 KB

Frequently asked questions

What does the Google Contacts AI skill do?

Search, view, create, update, and delete the user's Google Contacts.

Why use Google Contacts on TypingMind?

Because you install it once and use it with any model. Google Contacts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Contacts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/win4r/MuseAI-Skills/tree/main/opt/hatch/skills/google-contacts. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Google Contacts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Contacts?

As many as you like. As long as a model supports skills, you can use Google Contacts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Contacts AI skill free?

It is published on GitHub by win4r. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Authoring Skills

vercel

OrganizationPopular

How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs…

Dce Edge

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…

Gh Stack

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or…

Agent Transcript

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Google Contacts

Connecting

Common flows

Find a contact

Add a contact

Edit a contact

Delete a contact

Rules

Limits

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now