Not in the top 1,000 by GitHub stars
imbue-ai/latchkey
A command-line tool that injects credentials to curl requests to known public APIs.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/generic/latchkey/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → c1c2b098be72
No earlier version was observed for comparison.
skills/openclaw/latchkey/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → c1c2b098be72
No earlier version was observed for comparison.
Verified commit c1c2b098be72f906e660694c50608622df6d64c5
git clone --filter=blob:none --no-checkout https://github.com/imbue-ai/latchkey.git .hotskills/imbue-ai-latchkey && git -C .hotskills/imbue-ai-latchkey checkout --detach c1c2b098be72f906e660694c50608622df6d64c5
# Copy each selected skill directory from .hotskills/imbue-ai-latchkey into .agents/skills/<skill-name>/Heat
1.8- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
How it works
latchkey
When your agent uses it
Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
What it loads into context
Frontmatter
73 tokensAlways available to the agent
SKILL.md
1,302 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Examples
- Storing credentials
- Using multiple accounts
- Notes
- Currently supported services
Files
SKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytesSKILL.mdcore5,522 bytes
Read SKILL.md
# 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:
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.).View the complete source on GitHublatchkey
When your agent uses it
Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,148 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Examples
- Storing credentials
- Using multiple accounts
- Notes
- Currently supported services
Files
SKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytesSKILL.mdcore4,774 bytes
Read SKILL.md
# 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.).View the complete source on GitHubSkills included
- latchkey
- latchkey
Repository facts
- License
- MIT
- Created
- Jan 15, 2026
- Last pushed
- Nov 6, 2026
- Forks
- 5
- Open issues
- 4
- Project activity
- Active
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 6, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 20 notes
skills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generic/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/openclaw/latchkey/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 32 network referencesin 2 files: latchkey/SKILL.md:2 latchkey/SKILL.md:2
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 32 signals by file
skills/generic/latchkey/SKILL.md
- Network accessline 2
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 - Network accessline 3
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 lat - Network accessline 4
compatibility: Requires node.js, curl and latchkey (npm install -g latchkey). A desktop/GUI environment is required for the browser functionality. - Network accessline 11
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 credenti - Network accessline 17
1. **Use `latchkey curl`** instead of regular `curl` for supported services. 2. **Pass through all regular curl arguments** - latchkey is a transparent wrapper. - Network accessline 18
2. **Pass through all regular curl arguments** - latchkey is a transparent wrapper. - Network accessline 29
### Make an authenticated curl request - Network accessline 31
latchkey curl [curl arguments] - Network accessline 36
latchkey curl -X POST 'https://slack.com/api/conversations.create' \ - Network accessline 45
latchkey curl 'https://discord.com/api/v10/users/@me' - Network accessline 50
latchkey services info discord # Check the "credentialStatus" field - shows "invalid" latchkey auth browser discord latchkey curl 'https://discord.com/api/v10/users/@me' - Network accessline 52
latchkey curl 'https://discord.com/api/v10/users/@me' - Network accessline 86
When credentials cannot be expressed as static curl arguments, the user would use the `set-nocurl` subcommand. For example: - Network accessline 106
And then reference it in curl calls: - Network accessline 109
latchkey --account alice@example.com curl ... - Network accessline 121
- All curl arguments are passed through unchanged - Network accessline 123
- Credentials are always stored encrypted and are never transmitted anywhere beyond the endpoints specified by the actual curl calls.
skills/openclaw/latchkey/SKILL.md
- Network accessline 2
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 i - Network accessline 3
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 latch - Network accessline 4
compatibility: Requires node.js, curl and latchkey (npm install -g latchkey). - Network accessline 12
Latchkey is a CLI tool that automatically injects credentials into curl commands. Credentials (mostly API tokens) need to be manually managed by the user. - Network accessline 18
1. **Use `latchkey curl`** instead of regular `curl` for supported services. 2. **Pass through all regular curl arguments** - latchkey is a transparent wrapper. - Network accessline 19
2. **Pass through all regular curl arguments** - latchkey is a transparent wrapper. - Network accessline 29
### Make an authenticated curl request - Network accessline 31
latchkey curl [curl arguments] - Network accessline 36
latchkey curl -X POST 'https://slack.com/api/conversations.create' \ - Network accessline 45
latchkey curl 'https://discord.com/api/v10/users/@me' - Network accessline 78
When credentials cannot be expressed as static curl arguments, the user would use the `set-nocurl` subcommand. For example: - Network accessline 98
And then reference it in curl calls: - Network accessline 101
latchkey --account alice@example.com curl ... - Network accessline 113
- All curl arguments are passed through unchanged - Network accessline 115
- Credentials are always stored encrypted and are never transmitted anywhere beyond the endpoints specified by the actual curl calls.
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Signal confidence: 32 facts
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:2Low confidence
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:3Low confidence
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:4Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:11Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:17Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:18Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:29Low confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:31High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:36High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:45High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:50High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:52High confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:86Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:106Low confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:109High confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:121Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:123Low confidence
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:2Low confidence
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:3Low confidence
- Network access in the frontmatter of the SKILL.mdlatchkey/SKILL.md:4Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:12Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:18Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:19Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:29Low confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:31High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:36High confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:45High confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:78Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:98Low confidence
- Network access in code of the SKILL.mdlatchkey/SKILL.md:101High confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:113Low confidence
- Network access in prose of the SKILL.mdlatchkey/SKILL.md:115Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Compatible | Standard SKILL.md skills/generic/latchkey/SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/generic/latchkey/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/generic/latchkey/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/generic/latchkey/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/generic/latchkey/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.