Agent skill

Latchkey

Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

MITAuto-check passedBackend & APIs

Install Latchkey

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/generic/latchkey .claude/skills/latchkey && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .claude/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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

$skill-installer install https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey

Type 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.

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/generic/latchkey .agents/skills/latchkey && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .agents/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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.

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/generic/latchkey .cursor/skills/latchkey && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .cursor/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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

$ gemini skills install https://github.com/imbue-ai/latchkey.git --path skills/generic/latchkey

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/generic/latchkey .gemini/skills/latchkey && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .gemini/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey

Installs 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).

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/generic/latchkey .github/skills/latchkey && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .github/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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.

skills CLI

$ npx skills add imbue-ai/latchkey --skill latchkey -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install imbue-ai/latchkey latchkey --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/imbue-ai/latchkey.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/generic/latchkey .opencode/skills/latchkey && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "latchkey" agent skill from https://github.com/imbue-ai/latchkey/tree/main/skills/generic/latchkey into .opencode/skills/latchkey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "latchkey", 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: latchkey
GitHub stars: 130
Token cost: ~1.3k tokens
SKILL.md length: 613 words
Files: 1
Skills in repo: 2
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

Works in 8 steps: Use latchkey curl instead of regular… → Pass through all regular curl arguments… → Check for latchkey services list to get… → …
Tasks that involve REST APIs
SKILL.md covers Instructions, Examples, Storing credentials and Using multiple accounts, plus 2 more sections
Reaches discord.com and slack.com

What it does

Latchkey is an agent skill from imbue-ai/latchkey. Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality.

It sits in Backend & APIs, covering REST APIs and Cloud office suites. It works with Slack, GitHub, Google Workspace and Dropbox. The repository describes itself as: A command-line tool that injects credentials to curl requests to known public APIs. The licence is MIT.

When your agent uses it

Tasks that involve REST APIs
Tasks that involve Cloud office suites

Example prompts

“/latchkey”

Requirements

Node.js
Compatibility (from SKILL.md): Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality.

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

Use latchkey curl instead of regular curl for supported services.
Pass through all regular curl arguments - latchkey is a transparent wrapper.
Check for latchkey services list to get a list of supported services. Use --viable to only show the currently configured ones.
Use latchkey services info to get information about a specific service (auth options, credentials status, API docs links, special…
If necessary, ask the user to configure credentials first. Tell the user to run latchkey auth set on the machine where latchkey is…
Alternatively, let the user log in with the browser. If supported for the given service, run latchkey auth browser to open a browser login…
Look for the newest documentation of the desired public API online. If using the browser auth command, avoid bot-only endpoints.
Do not initiate a new login if the credentials status is valid or unknown - the user might just not have the necessary permissions for the…

What it can do on your machine

Read from SKILL.md and the folder at commit a5217f1. 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 (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- discord.com
- slack.com
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.
Compatibility
Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality.
From compatibility in the SKILL.md frontmatter.

Context cost

Latchkey loads about 1.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 613 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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 imbue-ai/latchkey at commit a5217f1, republished under its MIT licence (© imbue-ai). 613 words, ~1,323 tokens.

Download SKILL.mdSave it as .claude/skills/latchkey/SKILL.md (or your agent's skills folder).

name: latchkey
description: Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
compatibility: Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality.

Latchkey

Instructions

Latchkey is a CLI tool that automatically injects credentials into curl commands. Credentials (mostly API tokens) can be either manually managed or, for some services, Latchkey can open a browser login pop-up window and extract API credentials from the session.

Use this skill when the user asks you to work on their behalf with services that have HTTP APIs, like AWS, GitLab, Google Drive, Discord or others.

Usage:

Use latchkey curl instead of regular curl for supported services.
Pass through all regular curl arguments - latchkey is a transparent wrapper.
Check for latchkey services list to get a list of supported services. Use --viable to only show the currently configured ones.
Use latchkey services info <service_name> to get information about a specific service (auth options, credentials status, API docs links, special requirements, etc.).
If necessary, ask the user to configure credentials first. Tell the user to run latchkey auth set on the machine where latchkey is installed (using the setCredentialsExample from the services info command).
Alternatively, let the user log in with the browser. If supported for the given service, run latchkey auth browser <service_name> to open a browser login pop-up window.
Look for the newest documentation of the desired public API online. If using the browser auth command, avoid bot-only endpoints.
Do not initiate a new login if the credentials status is valid or unknown - the user might just not have the necessary permissions for the action you're trying to do.

Examples

Make an authenticated curl request

bash

latchkey curl [curl arguments]

Creating a Slack channel

bash

latchkey curl -X POST 'https://slack.com/api/conversations.create' \
  -H 'Content-Type: application/json' \
  -d '{"name":"my-channel"}'

(Notice that -H 'Authorization: Bearer is not present in the invocation.)

Getting Discord user info

bash

latchkey curl 'https://discord.com/api/v10/users/@me'

bash

latchkey services info discord  # Check the "credentialStatus" field - shows "invalid"
latchkey auth browser discord
latchkey curl 'https://discord.com/api/v10/users/@me'

Only do this when you notice that your previous call ended up not being authenticated (HTTP 401 or 403).

List usable services

bash

latchkey services list --viable

Lists services that either have stored credentials or can be authenticated via a browser.

Get service-specific info

bash

latchkey services info slack

Returns auth options, credentials status, and developer notes about the service. If browser is not present in the authOptions field, the service requires the user to directly set API credentials via latchkey auth set or latchkey auth set-nocurl before making requests.

Show full SKILL.md (247 more words)Show less

Storing credentials

Aside from the latchkey auth browser case, it is the user's responsibility to supply credentials. The user would typically do something like this:

bash

latchkey auth set my-gitlab-instance -H "PRIVATE-TOKEN: <token>"

When credentials cannot be expressed as static curl arguments, the user would use the set-nocurl subcommand. For example:

bash

latchkey auth set-nocurl aws <access-key-id> <secret-access-key>

If a service doesn't appear with the --viable flag, it may still be supported; the user just hasn't provided the credentials yet. latchkey service info <service_name> can be used to see how to provide credentials for a specific service.

Using multiple accounts

It is possible to associate credentials with a specific account:

bash

latchkey --account alice@example.com auth set ...

And then reference it in curl calls:

bash

latchkey --account alice@example.com curl ...

The --account option must go right after latchkey.

You can see the existing accounts as keys in the credential dictionary produced by latchkey services info. An empty string in the key means "unknown account".

Notes

All curl arguments are passed through unchanged
Return code, stdout and stderr are passed back from curl
Credentials are always stored encrypted and are never transmitted anywhere beyond the endpoints specified by the actual curl calls.

Currently supported services

Latchkey currently offers varying levels of support for the following services: AWS, Calendly, Coolify, Discord, Dropbox, Figma, GitHub, GitLab, Gmail, Google Analytics, Google Calendar, Google Docs, Google Drive, Google Sheets, Hugging Face, Linear, Mailchimp, ngrok, Notion, OpenRouter, Ramp, Sentry, Slack, Stripe, Telegram, Tailscale, Todoist, Umami, Yelp, Zoom, and more.

User-registered services

Note for humans: users can also add limited support for new services at runtime using the latchkey services register command.

Files

Just SKILL.md in skills/generic/latchkey of imbue-ai/latchkey.

Open the folder on GitHubat commit a5217f1

Compare with similar skills

Latchkey 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.

Latchkey compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Latchkey this skillimbue-ai/latchkey	130	—	~1.3k	Automated safety check: Pass	MIT	today
Implementing Zero Trust For SaaS Applicationsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
API GatewayCraftOS-dev/CraftBot	392	3 repos	~7.1k	Automated safety check: Pass	MIT	today
Frontmcp Channelsagentfront/frontmcp	146	—	~3.7k	Automated safety check: Pass	Apache-2.0	2 days ago
Chat SDK Botslobehub/lobehub	83k	—	~1.5k	Automated safety check: Pass	Custom licence	today
Chat SDKvercel/vercel-plugin	301	—	~2.9k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Implementing Zero Trust For SaaS Applications
mukul975/Anthropic-Cybersecurity-Skills
Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…
34k GitHub stars~2.9k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
API Gateway
CraftOS-dev/CraftBot
Connect to 100+ APIs (Google Workspace, Microsoft 365, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth.
392 GitHub starsUsed in 3 repos~7.1k tokens
Backend & APIsAuto-check passed
Frontmcp Channels
agentfront/frontmcp
A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.
146 GitHub stars~3.7k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
Chat SDK Bots
lobehub/lobehub
Builds chat bots once for Slack, Teams, Google Chat, Discord, GitHub and Linear with the Chat SDK, covering event handlers, cards, modals, streaming and state adapters.
83k GitHub stars~1.5k tokensUpdated today
Backend & APIsAuto-check passed
Chat SDK
vercel/vercel-plugin
Official
Vercel Chat SDK expert guidance. An agent skill from vercel/vercel-plugin.
301 GitHub stars~2.9k tokensUpdated yesterday
Backend & APIsAuto-check passed
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…
1k GitHub stars~3.3k tokensUpdated 15 days ago
Productivity & AutomationAuto-check passed

Questions about Latchkey

What does Latchkey do?

Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf. Latchkey is an agent skill from imbue-ai/latchkey.) using their HTTP APIs on the user's behalf.

When should I use Latchkey?

Latchkey fits situations like: tasks that involve REST APIs; tasks that involve Cloud office suites.

How do I install Latchkey in Claude Code?

Run `npx skills add imbue-ai/latchkey --skill latchkey -a claude-code`. Or copy the skill folder (skills/generic/latchkey in imbue-ai/latchkey) into .claude/skills/latchkey in your project. Claude Code loads it when a task matches its description.

How do I install Latchkey in Codex?

Run `npx skills add imbue-ai/latchkey --skill latchkey -a codex`. Or copy the skill folder (skills/generic/latchkey in imbue-ai/latchkey) into .agents/skills/latchkey in your project. Codex loads it when a task matches its description.

Can I use Latchkey 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 imbue-ai/latchkey --skill latchkey -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/latchkey, .gemini/skills/latchkey, .github/skills/latchkey and .opencode/skills/latchkey in your project.

What does Latchkey need to run?

SKILL.md names no scripts, command-line tools or credentials: Latchkey is instructions for the agent only. Our summary lists: Node.js. Compatibility (from SKILL.md): Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality..

Does Latchkey access the network?

SKILL.md names 2 domains. In commands or code: discord.com and slack.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Latchkey 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 Latchkey use?

Latchkey 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 Latchkey use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Latchkey?

Skills that share tags, products or a category with Latchkey: Implementing Zero Trust For SaaS Applications (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), API Gateway (CraftOS-dev/CraftBot, 392 stars), Frontmcp Channels (agentfront/frontmcp, 146 stars) and Chat SDK Bots (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Latchkey?

imbue-ai (a GitHub organization) maintains it in imbue-ai/latchkey, which has 130 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: imbue-ai/latchkey on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Latchkey

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Latchkey

Instructions

Examples

Make an authenticated curl request

Creating a Slack channel

Getting Discord user info

Detect expired credentials and force a new login to Discord

List usable services

Get service-specific info

Storing credentials

Using multiple accounts

Notes

Currently supported services

User-registered services

Files

Compare with similar skills

Similar skills

Implementing Zero Trust For SaaS Applications

API Gateway

Frontmcp Channels

Chat SDK Bots

Chat SDK

Openloomi Connectors

More from imbue-ai/latchkey

Latchkey

Related

Questions about Latchkey