メニュー
Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/imbue-ai/latchkey --skill latchkeyコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| 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 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:
latchkey curl instead of regular curl for supported services.latchkey services list to get a list of supported services. Use --viable to only show the currently configured ones.latchkey services info <service_name> to get information about a specific service (auth options, credentials status, API docs links, special requirements, etc.).latchkey auth set on the machine where latchkey is installed (using the setCredentialsExample from the services info command).latchkey auth browser <service_name>browser auth command, avoid bot-only endpoints.valid or unknown - the user might just not have the necessary permissions for the action you're trying to do.latchkey curl [curl arguments]
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.)
latchkey curl 'https://discord.com/api/v10/users/@me'
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).
latchkey services list --viable
Lists services that either have stored credentials or can be authenticated via a browser.
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.
Aside from the latchkey auth browser case, it is the user's responsibility to supply credentials.
The user would typically do something like this:
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:
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.
It is possible to associate credentials with a specific account:
latchkey --account alice@example.com auth set ...
And then reference it in curl calls:
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".
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.
Note for humans: users can also add limited support for new services
at runtime using the latchkey services register command.