latchkey 2.5.0 → 2.5.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "latchkey",
-  "version": "2.5.0",
+  "version": "2.5.1",
   "description": "A CLI tool that injects API credentials into curl requests to third-party services",
   "author": "Imbue <hynek@imbue.com>",
   "repository": {
@@ -66,6 +66,6 @@
     "vitest": "^4.0.18"
   },
   "pi": {
-    "skills": ["./skills/generic"]
+    "skills": ["./dist/skills/generic"]
   }
 }

package/dist/integrations/SKILL.md

@@ -1,114 +0,0 @@
----
-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:
-
-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. **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.
-7. **Look for the newest documentation of the desired public API online.** If using the `browser` auth command, avoid bot-only endpoints.
-8. **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 and force a new login to Discord
-```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.
-
-
-## 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.
-
-
-## 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,
-Linear, Mailchimp, Notion, Sentry, Slack, Stripe, Telegram, 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.

package/dist/integrations/openclaw/SKILL.md

@@ -1,106 +0,0 @@
----
-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).
-metadata: {"openclaw":{"emoji":"🔑","requires":{"bins":["latchkey"]},"install":[{"id":"node","kind":"node","package":"latchkey","bins":["latchkey"],"label":"Install Latchkey (npm)"}]}}
----
-
-# 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.
-
-
-## 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,
-Linear, Mailchimp, Notion, Sentry, Slack, Stripe, Telegram, 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.

package/dist/package.json

@@ -1,67 +0,0 @@
-{
-    "name": "latchkey",
-    "version": "2.3.0",
-    "description": "A CLI tool that injects API credentials into curl requests to third-party services",
-    "author": "Imbue <hynek@imbue.com>",
-    "repository": {
-        "type": "git",
-        "url": "git+https://github.com/imbue-ai/latchkey.git"
-    },
-    "homepage": "https://github.com/imbue-ai/latchkey#readme",
-    "bugs": {
-        "url": "https://github.com/imbue-ai/latchkey/issues"
-    },
-    "type": "module",
-    "main": "dist/src/index.js",
-    "types": "dist/src/index.d.ts",
-    "bin": {
-        "latchkey": "./dist/src/cli.js"
-    },
-    "files": [
-        "dist",
-        "README.md",
-        "LICENSE"
-    ],
-    "scripts": {
-        "prepublishOnly": "npm run build",
-        "build": "tsc && node -e \"require('fs').cpSync('integrations', 'dist/integrations', {recursive:true})\" ",
-        "dev": "tsc --watch",
-        "lint": "eslint src tests scripts",
-        "lint:fix": "eslint src tests scripts --fix",
-        "format": "prettier --write \"src/**/*.ts\" \"tests/**/*.ts\" \"scripts/**/*.ts\"",
-        "format:check": "prettier --check \"src/**/*.ts\" \"tests/**/*.ts\" \"scripts/**/*.ts\"",
-        "typecheck": "tsc --noEmit",
-        "test": "vitest run",
-        "test:watch": "vitest",
-        "start": "node dist/cli.js",
-        "bun-compile": "bun build ./src/cli.ts --compile --external chromium-bidi --external electron --outfile latchkey"
-    },
-    "keywords": [
-        "cli",
-        "curl",
-        "api",
-        "credentials",
-        "authentication",
-        "agents",
-        "imbue"
-    ],
-    "license": "MIT",
-    "engines": {
-        "node": ">=20"
-    },
-    "dependencies": {
-        "@napi-rs/keyring": "^1.2.0",
-        "commander": "^12.0.0",
-        "playwright": "^1.58.2",
-        "zod": "^3.22.0"
-    },
-    "devDependencies": {
-        "@eslint/js": "^9.39.2",
-        "@types/node": "^20.0.0",
-        "eslint": "^9.39.2",
-        "prettier": "^3.8.1",
-        "typescript": "^5.3.0",
-        "typescript-eslint": "^8.53.1",
-        "vitest": "^4.0.18"
-    }
-}

package/dist/scripts/encryptFile.d.ts

@@ -1,21 +0,0 @@
-#!/usr/bin/env npx tsx
-/**
- * CLI tool for encrypting and decrypting latchkey files.
- *
- * This is a developer utility for inspecting and modifying encrypted
- * credential and browser state files.
- *
- * Usage:
- *   npx tsx scripts/encryptFile.ts decrypt <file>     # Decrypt file to stdout
- *   npx tsx scripts/encryptFile.ts encrypt <file>     # Encrypt file in place
- *
- * The encryption key is sourced from:
- *   1. LATCHKEY_ENCRYPTION_KEY environment variable
- *   2. System keychain
- *
- * Examples:
- *   npx tsx scripts/encryptFile.ts decrypt ~/.latchkey/credentials.json
- *   npx tsx scripts/encryptFile.ts encrypt ~/.latchkey/credentials.json
- */
-export {};
-//# sourceMappingURL=encryptFile.d.ts.map

package/dist/scripts/encryptFile.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"encryptFile.d.ts","sourceRoot":"","sources":["../../scripts/encryptFile.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;GAiBG"}

package/dist/scripts/encryptFile.js

@@ -1,101 +0,0 @@
-#!/usr/bin/env npx tsx
-/**
- * CLI tool for encrypting and decrypting latchkey files.
- *
- * This is a developer utility for inspecting and modifying encrypted
- * credential and browser state files.
- *
- * Usage:
- *   npx tsx scripts/encryptFile.ts decrypt <file>     # Decrypt file to stdout
- *   npx tsx scripts/encryptFile.ts encrypt <file>     # Encrypt file in place
- *
- * The encryption key is sourced from:
- *   1. LATCHKEY_ENCRYPTION_KEY environment variable
- *   2. System keychain
- *
- * Examples:
- *   npx tsx scripts/encryptFile.ts decrypt ~/.latchkey/credentials.json
- *   npx tsx scripts/encryptFile.ts encrypt ~/.latchkey/credentials.json
- */
-import { program } from 'commander';
-import { existsSync, readFileSync, writeFileSync } from 'node:fs';
-import { CONFIG } from '../src/config.js';
-import { EncryptedStorage } from '../src/encryptedStorage.js';
-import { encrypt, generateKey } from '../src/encryption.js';
-import { isKeychainAvailable, retrieveFromKeychain } from '../src/keychain.js';
-const ENCRYPTED_FILE_PREFIX = 'LATCHKEY_ENCRYPTED:';
-function getEncryptionKey() {
-    // 1. Check environment variable via Config
-    if (CONFIG.encryptionKeyOverride) {
-        return CONFIG.encryptionKeyOverride;
-    }
-    // 2. Check keychain
-    if (isKeychainAvailable(CONFIG.serviceName, CONFIG.accountName)) {
-        const keychainKey = retrieveFromKeychain(CONFIG.serviceName, CONFIG.accountName);
-        if (keychainKey) {
-            return keychainKey;
-        }
-    }
-    console.error(`\
-Error: No encryption key available.
-Set LATCHKEY_ENCRYPTION_KEY or ensure the system keychain has a stored key.
-
-To generate a new key:
-  export LATCHKEY_ENCRYPTION_KEY="${generateKey()}"`);
-    process.exit(1);
-}
-function decryptCommand(filePath) {
-    if (!existsSync(filePath)) {
-        console.error(`Error: File not found: ${filePath}`);
-        process.exit(1);
-    }
-    const storage = new EncryptedStorage({
-        serviceName: CONFIG.serviceName,
-        accountName: CONFIG.accountName,
-    });
-    const content = storage.readFile(filePath);
-    if (content === null) {
-        console.error(`Error: Could not read file: ${filePath}`);
-        process.exit(1);
-    }
-    // Output to stdout
-    process.stdout.write(content);
-}
-function encryptCommand(filePath) {
-    if (!existsSync(filePath)) {
-        console.error(`Error: File not found: ${filePath}`);
-        process.exit(1);
-    }
-    const content = readFileSync(filePath, 'utf-8');
-    if (content.startsWith(ENCRYPTED_FILE_PREFIX)) {
-        console.error(`Error: File is already encrypted: ${filePath}`);
-        process.exit(1);
-    }
-    const key = getEncryptionKey();
-    const encryptedData = encrypt(content, key);
-    const dataToWrite = ENCRYPTED_FILE_PREFIX + encryptedData;
-    writeFileSync(filePath, dataToWrite, { encoding: 'utf-8', mode: 0o600 });
-    console.error(`Encrypted: ${filePath}`);
-}
-program.name('encryptFile').description(`\
-CLI tool for encrypting and decrypting latchkey files.
-
-The encryption key is sourced from:
-  1. LATCHKEY_ENCRYPTION_KEY environment variable
-  2. System keychain`);
-program
-    .command('decrypt')
-    .description('Decrypt file and print to stdout')
-    .argument('<file>', 'Path to the encrypted file')
-    .action((filePath) => {
-    decryptCommand(filePath);
-});
-program
-    .command('encrypt')
-    .description('Encrypt an unencrypted file in place')
-    .argument('<file>', 'Path to the file to encrypt')
-    .action((filePath) => {
-    encryptCommand(filePath);
-});
-program.parse();
-//# sourceMappingURL=encryptFile.js.map

package/dist/scripts/encryptFile.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"encryptFile.js","sourceRoot":"","sources":["../../scripts/encryptFile.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,SAAS,CAAC;AAClE,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAC1C,OAAO,EAAE,gBAAgB,EAAE,MAAM,4BAA4B,CAAC;AAC9D,OAAO,EAAE,OAAO,EAAE,WAAW,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,EAAE,mBAAmB,EAAE,oBAAoB,EAAE,MAAM,oBAAoB,CAAC;AAE/E,MAAM,qBAAqB,GAAG,qBAAqB,CAAC;AAEpD,SAAS,gBAAgB;IACvB,2CAA2C;IAC3C,IAAI,MAAM,CAAC,qBAAqB,EAAE,CAAC;QACjC,OAAO,MAAM,CAAC,qBAAqB,CAAC;IACtC,CAAC;IAED,oBAAoB;IACpB,IAAI,mBAAmB,CAAC,MAAM,CAAC,WAAW,EAAE,MAAM,CAAC,WAAW,CAAC,EAAE,CAAC;QAChE,MAAM,WAAW,GAAG,oBAAoB,CAAC,MAAM,CAAC,WAAW,EAAE,MAAM,CAAC,WAAW,CAAC,CAAC;QACjF,IAAI,WAAW,EAAE,CAAC;YAChB,OAAO,WAAW,CAAC;QACrB,CAAC;IACH,CAAC;IAED,OAAO,CAAC,KAAK,CAAC;;;;;oCAKoB,WAAW,EAAE,GAAG,CAAC,CAAC;IACpD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC;AAED,SAAS,cAAc,CAAC,QAAgB;IACtC,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC1B,OAAO,CAAC,KAAK,CAAC,0BAA0B,QAAQ,EAAE,CAAC,CAAC;QACpD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,MAAM,OAAO,GAAG,IAAI,gBAAgB,CAAC;QACnC,WAAW,EAAE,MAAM,CAAC,WAAW;QAC/B,WAAW,EAAE,MAAM,CAAC,WAAW;KAChC,CAAC,CAAC;IACH,MAAM,OAAO,GAAG,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC;IAE3C,IAAI,OAAO,KAAK,IAAI,EAAE,CAAC;QACrB,OAAO,CAAC,KAAK,CAAC,+BAA+B,QAAQ,EAAE,CAAC,CAAC;QACzD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,mBAAmB;IACnB,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;AAChC,CAAC;AAED,SAAS,cAAc,CAAC,QAAgB;IACtC,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC1B,OAAO,CAAC,KAAK,CAAC,0BAA0B,QAAQ,EAAE,CAAC,CAAC;QACpD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,MAAM,OAAO,GAAG,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAChD,IAAI,OAAO,CAAC,UAAU,CAAC,qBAAqB,CAAC,EAAE,CAAC;QAC9C,OAAO,CAAC,KAAK,CAAC,qCAAqC,QAAQ,EAAE,CAAC,CAAC;QAC/D,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,MAAM,GAAG,GAAG,gBAAgB,EAAE,CAAC;IAC/B,MAAM,aAAa,GAAG,OAAO,CAAC,OAAO,EAAE,GAAG,CAAC,CAAC;IAC5C,MAAM,WAAW,GAAG,qBAAqB,GAAG,aAAa,CAAC;IAE1D,aAAa,CAAC,QAAQ,EAAE,WAAW,EAAE,EAAE,QAAQ,EAAE,OAAO,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;IACzE,OAAO,CAAC,KAAK,CAAC,cAAc,QAAQ,EAAE,CAAC,CAAC;AAC1C,CAAC;AAED,OAAO,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC,WAAW,CAAC;;;;;qBAKnB,CAAC,CAAC;AAEvB,OAAO;KACJ,OAAO,CAAC,SAAS,CAAC;KAClB,WAAW,CAAC,kCAAkC,CAAC;KAC/C,QAAQ,CAAC,QAAQ,EAAE,4BAA4B,CAAC;KAChD,MAAM,CAAC,CAAC,QAAgB,EAAE,EAAE;IAC3B,cAAc,CAAC,QAAQ,CAAC,CAAC;AAC3B,CAAC,CAAC,CAAC;AAEL,OAAO;KACJ,OAAO,CAAC,SAAS,CAAC;KAClB,WAAW,CAAC,sCAAsC,CAAC;KACnD,QAAQ,CAAC,QAAQ,EAAE,6BAA6B,CAAC;KACjD,MAAM,CAAC,CAAC,QAAgB,EAAE,EAAE;IAC3B,cAAc,CAAC,QAAQ,CAAC,CAAC;AAC3B,CAAC,CAAC,CAAC;AAEL,OAAO,CAAC,KAAK,EAAE,CAAC"}

package/dist/skills/generic/SKILL.md

@@ -1,114 +0,0 @@
----
-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:
-
-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. **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.
-7. **Look for the newest documentation of the desired public API online.** If using the `browser` auth command, avoid bot-only endpoints.
-8. **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 and force a new login to Discord
-```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.
-
-
-## 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.
-
-
-## 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,
-Linear, Mailchimp, Notion, Sentry, Slack, Stripe, Telegram, 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.

package/dist/skills/openclaw/SKILL.md

@@ -1,106 +0,0 @@
----
-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).
-metadata: {"openclaw":{"emoji":"🔑","requires":{"bins":["latchkey"]},"install":[{"id":"node","kind":"node","package":"latchkey","bins":["latchkey"],"label":"Install Latchkey (npm)"}]}}
----
-
-# 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.
-
-
-## 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,
-Linear, Mailchimp, Notion, Sentry, Slack, Stripe, Telegram, 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.

package/dist/src/browserState.d.ts

@@ -1,8 +0,0 @@
-/**
- * Browser state management utilities.
- */
-/**
- * Get the browser state path from the LATCHKEY_BROWSER_STATE environment variable.
- */
-export declare function getBrowserStatePath(): string | null;
-//# sourceMappingURL=browserState.d.ts.map

package/dist/src/browserState.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"browserState.d.ts","sourceRoot":"","sources":["../../src/browserState.ts"],"names":[],"mappings":"AAAA;;GAEG;AAOH;;GAEG;AACH,wBAAgB,mBAAmB,IAAI,MAAM,GAAG,IAAI,CAUnD"}