Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
Install Media Inbox Triage
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .claude/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .claude/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .agents/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .agents/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .cursor/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .cursor/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zapier/gtm-cheat-codes.git --path skills/marketing/mcp-media-inbox-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .gemini/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .gemini/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .github/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .github/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-media-inbox-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/marketing/mcp-media-inbox-triage .opencode/skills/mcp-media-inbox-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mcp-media-inbox-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/marketing/mcp-media-inbox-triage into .opencode/skills/mcp-media-inbox-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-media-inbox-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mcp-media-inbox-triage- GitHub stars
- 342
- Token cost
- ~1.6k tokens
- SKILL.md length
- 633 words
- Files
- 6
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
- Works in 5 steps: Define The Inbox Window → Pull Minimal Email Context → Classify The Request → …
- A shared inbox mixes press requests, pitches and partnership notes
- SKILL.md covers What This Skill Does, When You Need This Pattern, Architecture and Required Connections Through…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
A bounded Gmail search comes first, such as the last seven days of mail not yet labeled as triaged, and the agent reads only what it needs: sender, subject, date, plain-text body, thread count and thread link. Full email bodies are not pasted into Slack. Each message is sorted into media request, partnership inquiry, customer or community lead, urgent executive risk, vendor pitch, spam or no action, or unclear.
The agent then scores urgency, recommends an owner, and posts summaries or urgent alerts to Slack and a persistent log to Google Sheets, with a triage doc as an alternative route. Suggested replies are drafted only for human review and are never sent. Gmail, Slack and Google Sheets connect through Zapier MCP, while Google Docs, Google Calendar and a CRM are optional. README, SETUP, SCHEMA-MAP and an onboarding prompt come with the skill.
When your agent uses it
- A shared inbox mixes press requests, pitches and partnership notes
- One person spends hours each week skimming mail for the real asks
- Routing inbound requests to PR, partnerships or community owners
Example prompts
- “Triage last week's press inbox and post the urgent media requests to Slack.”
- “Log this week's partnership inquiries in the triage sheet with a suggested owner for each.”
- “Draft replies for the media requests, but leave them for me to review before anything is sent.”
Requirements
- Zapier MCP with Gmail, Slack and Google Sheets connected
- Access to the shared Gmail inbox or label
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 022a288. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Media Inbox Triage loads about 1.6k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 633 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from zapier/gtm-cheat-codes at commit 022a288, republished under its MIT licence (© zapier). 633 words, ~1,645 tokens.
Download SKILL.mdSave it as
.claude/skills/mcp-media-inbox-triage/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- mcp-media-inbox-triage
- description
- Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.
MCP Media Inbox Triage
Use this skill when a marketing, PR, community, or partnerships team needs a lightweight triage layer for a shared Gmail inbox.
What This Skill Does
- Searches a configured Gmail inbox or label in a bounded window.
- Reads only the message context needed for classification.
- Classifies each message as media request, partnership inquiry, customer/community lead, urgent executive risk, vendor pitch, spam/no action, or unclear.
- Scores urgency and recommends the right owner.
- Routes relevant requests to Slack, Google Sheets, or a triage doc.
- Drafts suggested replies only for human review.
When You Need This Pattern
- A shared inbox mixes press requests, creator pitches, partnership notes, customer signals, newsletters, and vendor spam.
- One person spends time each week skimming every email just to find the real asks.
- The team needs human review before any reply is sent.
- The team already works in Gmail, Slack, and Google Sheets.
- You want a practical Zapier MCP workflow that saves attention, not just time.
Architecture
Shared Gmail inbox
-> Zapier MCP Gmail search and read
-> AI classification
-> Slack summary, Google Sheets triage log, or Gmail draftRequired Connections Through Zapier MCP
- Gmail: search and read messages from the shared inbox.
- Slack: post triage summaries or urgent alerts.
- Google Sheets: append a persistent triage log.
- LLM: classify and summarize.
Optional:
- Google Docs: create a weekly media-request digest.
- Google Calendar: check deadline windows or schedule follow-ups.
- CRM or advocacy database: match senders to known customers, partners, or advocates.
Core Workflow
1. Define The Inbox Window
Start with a bounded search:
to:{SHARED_INBOX} newer_than:7d -label:triagedAdjust the inbox address, label, and time window for your team.
2. Pull Minimal Email Context
For each candidate message, read only:
| Field | Why |
|---|---|
| Sender name and email | Identify source and possible owner |
| Subject | Fast classification signal |
| Date received | Urgency and SLA |
| Plain-text body | Extract the ask |
| Thread count | Spot follow-ups and repeated requests |
| Gmail thread link | Source of truth |
Do not dump full email bodies into Slack.
3. Classify The Request
| Category | Signal | Default action |
|---|---|---|
| Media request | Journalist, publication, interview, quote, deadline | Route to PR or comms |
| Partnership inquiry | Co-marketing, integration, affiliate, event, sponsorship | Route to partnerships or marketing |
| Customer/community lead | Customer story, testimonial, community invite, user feedback | Route to advocacy or community |
| Urgent executive risk | Legal threat, brand risk, sensitive complaint, public escalation | Alert owner immediately |
| Vendor pitch | Agency, list purchase, ad buy, unrelated service offer | Log or ignore |
| Spam/no action | Generic blast, irrelevant outreach, phishing indicators | Archive or leave unassigned |
| Unclear | Not enough context to decide | Send to human review |
Show full SKILL.md (230 more words)Show less
4. Score Urgency
| Urgency | Signals | Response target |
|---|---|---|
| High | Deadline within 48 hours, named journalist, public brand risk, customer escalation | Same day |
| Medium | Specific ask, relevant sender, no immediate deadline | Two business days |
| Low | Useful but exploratory, vague timing, non-critical | Weekly batch |
| Ignore | Spam, irrelevant vendor pitch, duplicate | No response |
5. Output The Summary
Media inbox triage: 14 messages scanned, 4 need action
High urgency
- Jane Lee, TechWeekly: asks for comment on AI workflow story by Friday.
Owner: PR
Suggested action: reply with availability and approved spokesperson.
Source: Gmail thread link
Ignored
- 8 vendor pitches
- 2 unrelated newslettersGoogle Sheets Log
| Column | Purpose |
|---|---|
| received_at | Message timestamp |
| sender_name | Human-readable sender |
| sender_email_domain | Domain only if privacy matters |
| subject | Email subject |
| category | Classification |
| urgency | High / Medium / Low / Ignore |
| summary | One-sentence ask |
| suggested_owner | Team or person |
| suggested_next_action | Concrete next step |
| gmail_thread_link | Source link |
| status | New / Routed / Done / Ignored |
Classification Prompt
You are triaging a shared media inbox.
Classify this email for a human team. Do not draft a reply unless the email needs action.
Return JSON:
{
"category": "media_request|partnership_inquiry|customer_community_lead|urgent_executive_risk|vendor_pitch|spam_no_action|unclear",
"urgency": "high|medium|low|ignore",
"sender_name": "string or unknown",
"sender_org": "string or unknown",
"deadline": "string or null",
"summary": "One sentence describing the actual ask",
"why_it_matters": "One sentence explaining relevance",
"suggested_owner": "PR|Community|Marketing|Partnerships|Support|Leadership|Human review|Ignore",
"suggested_next_action": "Concrete next action",
"draft_reply_needed": true,
"confidence": "high|medium|low"
}
Rules:
- Do not expose private email content in team channels.
- If the message is vague, classify as unclear.
- If the message is a generic vendor pitch, classify as vendor_pitch or spam_no_action.
- If the message mentions legal risk, public complaint, a journalist deadline, or a customer escalation, mark high urgency.Zapier MCP And SDK Role
- Use Zapier MCP to search Gmail, read message context, post Slack summaries, append Google Sheets rows, and create Gmail drafts when approved.
- Use Zapier SDK for recurring runs, owner routing, retry handling, status logging, follow-up reminders, and weekly reporting when the workflow becomes productionized.
Guardrails
- Never auto-send replies.
- Do not expose full private email threads in Slack.
- Keep Gmail thread links as the source of truth.
- Route uncertain messages to a human.
- Treat generic vendor pitches as vendor_pitch or spam_no_action unless there is a specific relevant ask.
- Keep ignored messages auditable during tuning.
Inspired By
Generalized from Matt Canning and NoPlex. The reference workflow uses Zapier MCP and Gmail to reduce media inbox review from about 4 hours per week to about 15 minutes.
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in skills/marketing/mcp-media-inbox-triage of zapier/gtm-cheat-codes.
- SKILL.md
- ONBOARDING-PROMPT.md
- README.md
- SCHEMA-MAP.md
- SETUP.md
- metadata.yaml
Open the folder on GitHubat commit 022a288
Compare with similar skills
Media Inbox Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Media Inbox Triage this skillzapier/gtm-cheat-codes | 342 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Managing Google Workspacetaylorwilsdon/google_workspace_mcp | 3.3k | — | ~2.9k | Automated safety check: Pass | MIT | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Openloomi Connectorsmelandlabs/openloomi | 1k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Managing Google Workspace
taylorwilsdon/google_workspace_mcp
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search).
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Openloomi Connectors
melandlabs/openloomi
openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…
- Official
Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
More from zapier/gtm-cheat-codes
All 21 skills in this repo- Official
Customer Deck Builder
zapier/gtm-cheat-codes
Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.
- Official
Customer Story Writer
zapier/gtm-cheat-codes
Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.
- Official
Customer Social Proof Finder
zapier/gtm-cheat-codes
Finds approved case studies, quotes, stats, logos and peer examples for campaigns, decks, emails and sales conversations, and flags anything that still needs approval.
- Official
Install Zapier
zapier/gtm-cheat-codes
Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.
- Official
MCP Sheet Cache Bridge
zapier/gtm-cheat-codes
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
- Official
MCP Urgent Caller Triage
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
Related
Categories
Questions about Media Inbox Triage
What does Media Inbox Triage do?
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review. A bounded Gmail search comes first, such as the last seven days of mail not yet labeled as triaged, and the agent reads only what it needs: sender, subject, date, plain-text body, thread count and thread link. Full email bodies are not pasted into Slack.
When should I use Media Inbox Triage?
Media Inbox Triage fits situations like: A shared inbox mixes press requests, pitches and partnership notes; one person spends hours each week skimming mail for the real asks; routing inbound requests to PR, partnerships or community owners.
How do I install Media Inbox Triage in Claude Code?
Run `npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a claude-code`. Or copy the skill folder (skills/marketing/mcp-media-inbox-triage in zapier/gtm-cheat-codes) into .claude/skills/mcp-media-inbox-triage in your project. Claude Code loads it when a task matches its description.
How do I install Media Inbox Triage in Codex?
Run `npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a codex`. Or copy the skill folder (skills/marketing/mcp-media-inbox-triage in zapier/gtm-cheat-codes) into .agents/skills/mcp-media-inbox-triage in your project. Codex loads it when a task matches its description.
Can I use Media Inbox Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/gtm-cheat-codes --skill mcp-media-inbox-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-media-inbox-triage, .gemini/skills/mcp-media-inbox-triage, .github/skills/mcp-media-inbox-triage and .opencode/skills/mcp-media-inbox-triage in your project.
What does Media Inbox Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Media Inbox Triage is instructions for the agent only. Our summary lists: Zapier MCP with Gmail, Slack and Google Sheets connected; Access to the shared Gmail inbox or label.
Does Media Inbox Triage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Media Inbox Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Media Inbox Triage use?
Media Inbox Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Media Inbox Triage use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Media Inbox Triage?
Skills that share tags, products or a category with Media Inbox Triage: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Managing Google Workspace (taylorwilsdon/google_workspace_mcp, 3.3k stars), Composio (ComposioHQ/composio, 30k stars) and Openloomi Connectors (melandlabs/openloomi, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Media Inbox Triage?
zapier (a GitHub organization, an official publisher) maintains it in zapier/gtm-cheat-codes, which has 342 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 13, 2026.
Source: zapier/gtm-cheat-codes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.