New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Latchkey

by imbue-ai in imbue-ai/latchkey

Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.

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/openclaw/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/

Facts

Skill name
latchkey
GitHub stars
130
Token cost
~1.1k tokens
SKILL.md length
487 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.

  • Works in 7 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 slack.com and discord.com

What it does

Latchkey is an agent skill from imbue-ai/latchkey. Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.

Its SKILL.md is about 1.1k 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).

It sits in Backend & APIs, covering REST APIs. It works with Slack, Amazon Web Services, GitLab and Google Drive. 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

Example prompts

  • “/latchkey”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires node.js, curl and latchkey (npm install -g latchkey).

Workflow steps

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

  1. Use latchkey curl instead of regular curl for supported services.
  2. Pass through all regular curl arguments - latchkey is a transparent wrapper.
  3. Check for latchkey services list to get a list of supported services. Use --viable to only show the currently configured ones.
  4. Use latchkey services info to get information about a specific service (auth options, credentials status, API docs links, special…
  5. If necessary, ask the user to configure credentials first. Tell the user to run latchkey auth set on the machine where latchkey is…
  6. Look for the newest documentation of the desired public API online.
  7. 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:

    • slack.com
    • discord.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).

    From compatibility in the SKILL.md frontmatter.

Context cost

Latchkey loads about 1.1k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 487 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.1k

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). 487 words, ~1,135 tokens.

Download SKILL.mdSave it as .claude/skills/latchkey/SKILL.md (or your agent's skills folder).
name
latchkey
description
Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.
compatibility
Requires node.js, curl and latchkey (npm install -g latchkey).

Latchkey

Instructions

Latchkey is a CLI tool that automatically injects credentials into curl commands. Credentials (mostly API tokens) need to be manually managed by the user.

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

Usage:

  1. Use latchkey curl instead of regular curl for supported services.
  2. Pass through all regular curl arguments - latchkey is a transparent wrapper.
  3. Check for latchkey services list to get a list of supported services. Use --viable to only show the currently configured ones.
  4. Use latchkey services info <service_name> to get information about a specific service (auth options, credentials status, API docs links, special requirements, etc.).
  5. 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).
  6. Look for the newest documentation of the desired public API online.
  7. 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'
Detect expired credentials
bash
latchkey services info discord  # Check the "credentialStatus" field - shows "invalid"
List usable services
bash
latchkey services list --viable

Lists services that have stored credentials.

Get service-specific info
bash
latchkey services info slack

Returns auth options, credentials status, and developer notes about the service.

Storing credentials

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.

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

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.

© imbue-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/openclaw/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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Latchkey this skillimbue-ai/latchkey130—~1.1kAutomated safety check: PassMIT
Security SecretsIgorWarzocha/Opencode-Workflows122—~1.2kAutomated safety check: NotesNone
Scanning For Hardcoded Secretsjeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: NotesMIT
AWS Deploymentaws/agent-toolkit-for-aws2.8k—~1.8kAutomated safety check: PassApache-2.0
Repo2skillzhangyanxs/repo2skill246—~3.6kAutomated safety check: PassNone
Kql ValidatorAzure/azqr795—~703Automated safety check: PassMIT

Similar skills

  • Security Secrets

    IgorWarzocha/Opencode-Workflows

    Review secret detection patterns and scanning workflows. An agent skill from IgorWarzocha/Opencode-Workflows.

    122 GitHub stars~1.2k tokensUpdated 8 mo ago
    SecurityAuto-check: notes

  • Scanning For Hardcoded Secrets

    jeremylongshore/tons-of-skills-marketplace

    Scan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic…

    2.8k GitHub stars~2.1k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • AWS Deployment

    aws/agent-toolkit-for-aws

    Official

    Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact.

    2.8k GitHub stars~1.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Repo2skill

    zhangyanxs/repo2skill

    Convert GitHub/GitLab/Gitee repositories into comprehensive OpenCode Skills using embedded LLM calls with multiple mirrors and rate limit handling

    246 GitHub stars~3.6k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed

  • Kql Validator

    Azure/azqr

    Official

    Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions.

    795 GitHub stars~703 tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • API Gateway

    itsmostafa/aws-agent-skills

    AWS API Gateway for REST and HTTP API management. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub stars~2.2k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed

More from imbue-ai/latchkey

  • Latchkey

    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.

    130 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Latchkey

What does Latchkey do?

Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs. Latchkey is an agent skill from imbue-ai/latchkey.) using their HTTP APIs.

When should I use Latchkey?

Latchkey fits situations like: tasks that involve REST APIs.

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/openclaw/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/openclaw/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)..

Does Latchkey access the network?

SKILL.md names 2 domains. In commands or code: slack.com and discord.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.1k tokens (SKILL.md is roughly 4.5k 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: Security Secrets (IgorWarzocha/Opencode-Workflows, 122 stars), Scanning For Hardcoded Secrets (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), AWS Deployment (aws/agent-toolkit-for-aws, 2.8k stars) and Repo2skill (zhangyanxs/repo2skill, 246 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.