MCP工具

Install globally

npm install -g sdkck

Use any integration — it auto-installs on first run

sdkck jira issue create --project MYPROJ --summary "Fix login bug"

`sdkck plugins install PLUGIN`

Installs a plugin into sdkck.

USAGE
  $ sdkck plugins install PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into sdkck.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the SDKCK_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the SDKCK_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ sdkck plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ sdkck plugins install myplugin

  Install a plugin from a github url.

    $ sdkck plugins install https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ sdkck plugins install someuser/someplugin

_See code: @oclif/plugin-plugins

`sdkck plugins uninstall [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ sdkck plugins uninstall [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sdkck plugins unlink
  $ sdkck plugins remove

EXAMPLES
  $ sdkck plugins uninstall myplugin

_See code: @oclif/plugin-plugins

Quick Start

```bash

Permissions for Safe Agent Usage

• Lock down what your agent can and can't do:

  # Allow only Jira read commands
  sdkck permission allow "jira issue list"
  sdkck permission allow "jira issue view"
  sdkck permission disallow "jira *"

  # Export your permission config for team sharing
  sdkck permission export permissions.json

  # View current rules
  sdkck permission list
  

Usage

$ npm install -g sdkck
$ sdkck COMMAND
running command...
$ sdkck (--version)
sdkck/0.26.1 linux-x64 node-v22.22.3
$ sdkck --help [COMMAND]
USAGE
  $ sdkck COMMAND
...

`sdkck api config NAME`

Update configuration for an imported API spec

USAGE
  $ sdkck api config NAME [--base-url <value>] [--description <value>] [--insecure] [--rename <value>] [--title
    <value>]

ARGUMENTS
  NAME  API name (as shown in `api list`)

FLAGS
  --base-url=<value>     New base URL for API calls
  --description=<value>  New description for the spec
  --[no-]insecure        Skip TLS certificate verification (--no-insecure to disable)
  --rename=<value>       New short identifier for this API
  --title=<value>        New display title for the spec

DESCRIPTION
  Update configuration for an imported API spec

EXAMPLES
  $ sdkck api config petstore --base-url https://api.example.com

  $ sdkck api config petstore --rename mystore

  $ sdkck api config petstore --title "My Petstore" --description "A pet store API"

_See code: src/commands/api/config.ts

Sidekick (sdkck)

Instant Commands from OpenAPI/Postman

• Point Sidekick at any OpenAPI/Swagger spec or Postman collection — local file or URL — and every endpoint becomes a CLI command instantly.

  # Import an OpenAPI spec from a URL or local file
  sdkck openapi import https://petstore3.swagger.io/api/v3/openapi.json --name petstore

  # Import a Postman collection the same way
  sdkck openapi import ./postman_collection.json --name myapi

  # Every operation is now a real command
  sdkck petstore listPets
  sdkck petstore getPetById --param petId=42
  sdkck petstore createPet --body name=Fido --body tag=dog

  # Searchable like any built-in command
  sdkck search "list pets"
  

• Auth is built in — configure bearer tokens, API keys, or basic auth once and every generated command uses it automatically:

  sdkck openapi auth petstore --type bearer --token sk-...
  sdkck openapi auth myapi --type apikey --api-key mykey --api-key-header X-API-Key
  

Turn any OpenAPI spec into CLI commands instantly

sdkck openapi import https://petstore3.swagger.io/api/v3/openapi.json --name petstore sdkck petstore listPets

AI-powered search (set your API key for semantic matching)

export OPENAI_API_KEY=sk-... sdkck search "find recent errors in production" ```

`sdkck api auth NAME`

Update the authentication settings for an imported API spec

USAGE
  $ sdkck api auth NAME [--api-key <value>] [--api-key-header <value>] [--base-url <value>] [--header
    <value>...] [--password <value>] [-p <value>] [--token <value>] [--type none|bearer|apikey|basic|custom] [--username
    <value>]

ARGUMENTS
  NAME  API name to update authentication for

FLAGS
  -p, --profile=<value>         Named profile to save
      --api-key=<value>         API key value (used with --type apikey)
      --api-key-header=<value>  [default: X-API-Key] Header name for the API key
      --base-url=<value>        Base URL for this profile
      --header=<value>...       Custom header in Key=Value format (used with --type custom, repeatable)
      --password=<value>        Password for basic auth
      --token=<value>           Bearer token
      --type=<option>           Authentication type to configure
                                <options: none|bearer|apikey|basic|custom>
      --username=<value>        Username for basic auth

DESCRIPTION
  Update the authentication settings for an imported API spec

EXAMPLES
  $ sdkck api auth petstore --type bearer --token sk-...

  $ sdkck api auth petstore --type apikey --api-key mykey

  $ sdkck api auth petstore --type apikey --api-key mykey --api-key-header Authorization

  $ sdkck api auth petstore --type basic --username user --password secret

  $ sdkck api auth petstore --type custom --header X-Tenant-ID=acme --header X-App-Key=secret

  $ sdkck api auth petstore --type none

  $ sdkck api auth petstore --type bearer --token sk-prod -p prod --base-url https://api.prod.example.com

_See code: src/commands/api/auth.ts

`sdkck api call NAME OPERATIONID`

Call an imported API operation

USAGE
  $ sdkck api call NAME OPERATIONID [--base-url <value>] [--body <value>...] [--header <value>...] [--param
    <value>...] [--raw] [--toon]

ARGUMENTS
  NAME         API name (as shown in `api list`)
  OPERATIONID  Operation ID to call (as shown in `api list <name>`)

FLAGS
  --base-url=<value>   Override the base URL for this request
  --body=<value>...    Request body field as key=value (repeatable)
  --header=<value>...  Extra request header as Key=Value (repeatable)
  --param=<value>...   Path or query parameter as key=value (repeatable)
  --raw                Print the raw response body without JSON formatting
  --toon               Encode JSON output with TOON for token-efficient LLM consumption

DESCRIPTION
  Call an imported API operation

EXAMPLES
  $ sdkck api call petstore listPets

  $ sdkck api call petstore getPetById --param petId=42

  $ sdkck api call petstore createPet --body name=Fido --body tag=dog

  $ sdkck api call petstore listPets --query limit=10 --header X-Trace=abc

_See code: src/commands/api/call.ts

`sdkck api import SOURCE`

Import an OpenAPI spec, Postman collection, or GraphQL schema (SDL/introspection/endpoint) and register its operations as commands

USAGE
  $ sdkck api import SOURCE [--api-key <value>] [--api-key-header <value>] [--auth-type
    none|bearer|apikey|basic] [--base-url <value>] [--graphql] [--insecure] [--name <value>] [--password <value>]
    [--selection-depth <value>] [--token <value>] [--username <value>]

ARGUMENTS
  SOURCE  Path to a local OpenAPI/Postman/GraphQL spec or URL (REST or GraphQL endpoint)

FLAGS
  --api-key=<value>          API key value (used with --auth-type apikey)
  --api-key-header=<value>   [default: X-API-Key] Header name for the API key
  --auth-type=<option>       Authentication type
                             <options: none|bearer|apikey|basic>
  --base-url=<value>         Override the base URL for API calls (GraphQL endpoint URL for GraphQL imports)
  --graphql                  Treat the source as a GraphQL schema (SDL, introspection JSON, or live endpoint)
  --insecure                 Skip TLS certificate verification (useful for self-signed certs)
  --name=<value>             Short identifier for this API (defaults to the spec title slug)
  --password=<value>         Password for basic auth
  --selection-depth=<value>  [default: 3] Max depth of auto-generated GraphQL selection sets (GraphQL imports only)
  --token=<value>            Bearer token (used with --auth-type bearer)
  --username=<value>         Username for basic auth

DESCRIPTION
  Import an OpenAPI spec, Postman collection, or GraphQL schema (SDL/introspection/endpoint) and register its operations
  as commands

EXAMPLES
  $ sdkck api import ./petstore.json  --name petstore

  $ sdkck api import ./postman_collection.json --name myapi

  $ sdkck api import https://petstore3.swagger.io/api/v3/openapi.json

  $ sdkck api import ./schema.graphql --base-url https://api.example.com/graphql

  $ sdkck api import https://api.example.com/graphql --name github

  $ sdkck api import ./api.yaml --auth-type bearer --token sk-...

  $ sdkck api import ./api.yaml --auth-type apikey --api-key mykey --api-key-header X-API-Key

  $ sdkck api import ./api.yaml --auth-type basic --username user --password pass

_See code: src/commands/api/import.ts

`sdkck api list [NAME]`

List imported API specs and their available operations

USAGE
  $ sdkck api list [NAME]

ARGUMENTS
  [NAME]  API name to list operations for (omit to list all imported APIs)

DESCRIPTION
  List imported API specs and their available operations

EXAMPLES
  $ sdkck api list

  $ sdkck api list petstore

_See code: src/commands/api/list.ts

`sdkck api profile NAME`

Manage auth profiles for an imported API spec

USAGE
  $ sdkck api profile NAME [--delete <value>] [--show <value>] [--use <value>]

ARGUMENTS
  NAME  API name

FLAGS
  --delete=<value>  Delete a named profile
  --show=<value>    Show auth details for a named profile
  --use=<value>     Activate a named profile

DESCRIPTION
  Manage auth profiles for an imported API spec

EXAMPLES
  $ sdkck api profile petstore

  $ sdkck api profile petstore --show dev

  $ sdkck api profile petstore --use prod

  $ sdkck api profile petstore --delete dev

_See code: src/commands/api/profile.ts

`sdkck api remove NAME`

Remove an imported API spec

USAGE
  $ sdkck api remove NAME

ARGUMENTS
  NAME  API name to remove

DESCRIPTION
  Remove an imported API spec

EXAMPLES
  $ sdkck api remove petstore

_See code: src/commands/api/remove.ts

`sdkck commands`

List all sdkck commands.

USAGE
  $ sdkck commands [--json] [-c id|plugin|summary|type... | --tree] [--deprecated] [-x | ] [--hidden]
    [--no-truncate | ] [--sort id|plugin|summary|type | ]

FLAGS
  -c, --columns=<option>...  Only show provided columns (comma-separated).
                             <options: id|plugin|summary|type>
  -x, --extended             Show extra columns.
      --deprecated           Show deprecated commands.
      --hidden               Show hidden commands.
      --no-truncate          Do not truncate output.
      --sort=<option>        [default: id] Property to sort by.
                             <options: id|plugin|summary|type>
      --tree                 Show tree of commands.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List all sdkck commands.

_See code: @oclif/plugin-commands

`sdkck help [COMMAND]`

Display help for sdkck.

USAGE
  $ sdkck help [COMMAND...] [-n]

ARGUMENTS
  [COMMAND...]  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for sdkck.

_See code: @oclif/plugin-help

`sdkck mcp client add NAME`

Add an MCP server and register its tools as native CLI commands

USAGE
  $ sdkck mcp client add NAME [--args <value>...] [-c <value>] [--env <value>...] [--header <value>...] [-u <value>]

ARGUMENTS
  NAME  Name for the MCP server

FLAGS
  -c, --command=<value>    Command to run the MCP server (stdio transport)
  -u, --url=<value>        URL of the MCP server (http transport)
      --args=<value>...    Argument to pass to the server command (repeatable)
      --env=<value>...     Environment variable for the server process as KEY=VALUE (repeatable)
      --header=<value>...  HTTP header for the MCP server as Key=Value (repeatable)

DESCRIPTION
  Add an MCP server and register its tools as native CLI commands

EXAMPLES
  $ sdkck mcp client add github --command npx --args @modelcontextprotocol/server-github

  $ sdkck mcp client add myserver --command ./bin/server.js --args start --env API_KEY=abc123

  $ sdkck mcp client add remote --url http://localhost:3000/mcp

  $ sdkck mcp client add remote --url https://api.example.com/mcp --header Authorization="Bearer token"

_See code: src/commands/mcp/client/add.ts

`sdkck mcp client auth NAME`

Re-authenticate an HTTP MCP server via OAuth browser flow

USAGE
  $ sdkck mcp client auth NAME

ARGUMENTS
  NAME  Name of the MCP server to re-authenticate

DESCRIPTION
  Re-authenticate an HTTP MCP server via OAuth browser flow

EXAMPLES
  $ sdkck mcp client auth browserstack-remote

_See code: src/commands/mcp/client/auth.ts

`sdkck mcp client list`

List configured MCP servers and their cached tools

USAGE
  $ sdkck mcp client list [-t]

FLAGS
  -t, --tools  Show individual tools for each server

DESCRIPTION
  List configured MCP servers and their cached tools

EXAMPLES
  $ sdkck mcp client list

  $ sdkck mcp client list --tools

_See code: src/commands/mcp/client/list.ts

`sdkck mcp client refresh [NAME]`

Refresh the cached tool list for one or all MCP servers

USAGE
  $ sdkck mcp client refresh [NAME]

ARGUMENTS
  [NAME]  Name of the MCP server to refresh (refreshes all if omitted)

DESCRIPTION
  Refresh the cached tool list for one or all MCP servers

EXAMPLES
  $ sdkck mcp client refresh

  $ sdkck mcp client refresh github

_See code: src/commands/mcp/client/refresh.ts

`sdkck mcp client remove NAME`

Remove a configured MCP server and its cached tools

USAGE
  $ sdkck mcp client remove NAME

ARGUMENTS
  NAME  Name of the MCP server to remove

DESCRIPTION
  Remove a configured MCP server and its cached tools

EXAMPLES
  $ sdkck mcp client remove github

_See code: src/commands/mcp/client/remove.ts

`sdkck mcp start`

Start an MCP server exposing all CLI commands as tools

USAGE
  $ sdkck mcp start [--host <value>] [--port <value>] [--transport stdio|http]

FLAGS
  --host=<value>        [default: 127.0.0.1] IP address to listen on (HTTP transport only)
  --port=<value>        [default: 3000] Port to listen on (HTTP transport only)
  --transport=<option>  [default: stdio] Transport to use
                        <options: stdio|http>

DESCRIPTION
  Start an MCP server exposing all CLI commands as tools

EXAMPLES
  $ sdkck mcp start

  $ sdkck mcp start --transport http

  $ sdkck mcp start --transport http --port 3001

  $ sdkck mcp start --transport http --host 0.0.0.0

_See code: src/commands/mcp/start.ts

`sdkck mcp token delete`

Remove the MCP server Bearer token, disabling HTTP authentication

USAGE
  $ sdkck mcp token delete

DESCRIPTION
  Remove the MCP server Bearer token, disabling HTTP authentication

EXAMPLES
  $ sdkck mcp token delete

_See code: src/commands/mcp/token/delete.ts

`sdkck mcp token generate`

Generate a Bearer token for MCP server HTTP authentication

USAGE
  $ sdkck mcp token generate

DESCRIPTION
  Generate a Bearer token for MCP server HTTP authentication

EXAMPLES
  $ sdkck mcp token generate

_See code: src/commands/mcp/token/generate.ts

`sdkck mcp token show`

Show the current MCP server Bearer token

USAGE
  $ sdkck mcp token show

DESCRIPTION
  Show the current MCP server Bearer token

EXAMPLES
  $ sdkck mcp token show

_See code: src/commands/mcp/token/show.ts

`sdkck permission disallow PATTERN`

Disallow a command pattern in the plugin command permission list

USAGE
  $ sdkck permission disallow PATTERN

ARGUMENTS
  PATTERN  Command pattern to disallow. Use a full command ID ("jira issue create"), a topic ("jira"), a topic wildcard
           ("jira *"), or "*" for everything.

DESCRIPTION
  Disallow a command pattern in the plugin command permission list

EXAMPLES
  $ sdkck permission disallow "*"

  $ sdkck permission disallow jira

  $ sdkck permission disallow "jira *"

  $ sdkck permission disallow "jira issue create"

_See code: src/commands/permission/disallow.ts

`sdkck permission export FILE`

Export the plugin command permission configuration to a JSON file

USAGE
  $ sdkck permission export FILE

ARGUMENTS
  FILE  Path to the JSON file to export the permission configuration to

DESCRIPTION
  Export the plugin command permission configuration to a JSON file

EXAMPLES
  $ sdkck permission export permission.json

_See code: src/commands/permission/export.ts

`sdkck permission import FILE`

Import the plugin command permission configuration from a JSON file

USAGE
  $ sdkck permission import FILE

ARGUMENTS
  FILE  Path to the JSON file to import the permission configuration from

DESCRIPTION
  Import the plugin command permission configuration from a JSON file

EXAMPLES
  $ sdkck permission import permission.json

_See code: src/commands/permission/import.ts

`sdkck permission list`

List all rules in the plugin command permission list

USAGE
  $ sdkck permission list

DESCRIPTION
  List all rules in the plugin command permission list

EXAMPLES
  $ sdkck permission list

_See code: src/commands/permission/list.ts

`sdkck permission reset`

Reset all plugin command permission rules

USAGE
  $ sdkck permission reset [--confirm]

FLAGS
  --confirm  Skip the confirmation prompt

DESCRIPTION
  Reset all plugin command permission rules

EXAMPLES
  $ sdkck permission reset

  $ sdkck permission reset --confirm

_See code: src/commands/permission/reset.ts

`sdkck plugins`

List installed plugins.

USAGE
  $ sdkck plugins [--json] [--core]

FLAGS
  --core  Show core plugins.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ sdkck plugins

_See code: @oclif/plugin-plugins

`sdkck plugins add PLUGIN`

Installs a plugin into sdkck.

USAGE
  $ sdkck plugins add PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into sdkck.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the SDKCK_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the SDKCK_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ sdkck plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ sdkck plugins add myplugin

  Install a plugin from a github url.

    $ sdkck plugins add https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ sdkck plugins add someuser/someplugin

`sdkck plugins:inspect PLUGIN...`

Displays installation properties of a plugin.

USAGE
  $ sdkck plugins inspect PLUGIN...

ARGUMENTS
  PLUGIN...  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ sdkck plugins inspect myplugin

_See code: @oclif/plugin-plugins

`sdkck plugins link PATH`

Links a plugin into the CLI for development.

USAGE
  $ sdkck plugins link PATH [-h] [--install] [-v]

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help          Show CLI help.
  -v, --verbose
      --[no-]install  Install dependencies after linking the plugin.

DESCRIPTION
  Links a plugin into the CLI for development.

  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ sdkck plugins link myplugin

_See code: @oclif/plugin-plugins

`sdkck plugins remove [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ sdkck plugins remove [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sdkck plugins unlink
  $ sdkck plugins remove

EXAMPLES
  $ sdkck plugins remove myplugin

`sdkck plugins reset`

Remove all user-installed and linked plugins.

USAGE
  $ sdkck plugins reset [--hard] [--reinstall]

FLAGS
  --hard       Delete node_modules and package manager related files in addition to uninstalling plugins.
  --reinstall  Reinstall all plugins after uninstalling.

_See code: @oclif/plugin-plugins

`sdkck plugins unlink [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ sdkck plugins unlink [PLUGIN...] [-h] [-v]

ARGUMENTS
  [PLUGIN...]  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sdkck plugins unlink
  $ sdkck plugins remove

EXAMPLES
  $ sdkck plugins unlink myplugin

`sdkck plugins update`

Update installed plugins.

USAGE
  $ sdkck plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

_See code: @oclif/plugin-plugins

`sdkck search QUERY`

Search for available commands

USAGE
  $ sdkck search QUERY [--json] [-d] [-n <value>]

ARGUMENTS
  QUERY  Search term to filter commands by

FLAGS
  -d, --details        Show full help for each matched command
  -n, --limit=<value>  [default: 5] Maximum number of results to return

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Search for available commands

EXAMPLES
  $ sdkck search "create pr"

  $ sdkck search jira -d

  $ sdkck search "update jira" --details

_See code: src/commands/search.ts

`sdkck update [CHANNEL]`

update the sdkck CLI

USAGE
  $ sdkck update [CHANNEL] [--force |  | [-a | -v <value> | -i]] [-b ]

FLAGS
  -a, --available        See available versions.
  -b, --verbose          Show more details about the available versions.
  -i, --interactive      Interactively select version to install. This is ignored if a channel is provided.
  -v, --version=<value>  Install a specific version.
      --force            Force a re-download of the requested version.

DESCRIPTION
  update the sdkck CLI

EXAMPLES
  Update to the stable channel:

    $ sdkck update stable

  Update to a specific version:

    $ sdkck update --version 1.0.0

  Interactively select version:

    $ sdkck update --interactive

  See available versions:

    $ sdkck update --available

_See code: @oclif/plugin-update

`sdkck version`

USAGE
  $ sdkck version [--json] [--verbose]

FLAGS
  --verbose  Show additional information about the CLI.

GLOBAL FLAGS
  --json  Format output as json.

FLAG DESCRIPTIONS
  --verbose  Show additional information about the CLI.

    Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.

_See code: @oclif/plugin-version

Plugins

- Official plugins install automatically on first use. No upfront configuration, no bloated installs. - | Plugin | What It Does | | ----------------- | --------------------------------------------- | | @hesed/jira | Create, search, and manage Jira issues | | @hesed/bb | Bitbucket pull requests, repos, and pipelines | | @hesed/sentry | Error tracking and issue management | | @hesed/mysql | Query and manage MySQL databases | | @hesed/psql | Query and manage PostgreSQL databases | | @hesed/supabase | Supabase project and database operations | | @hesed/conni | Confluence page management |

• Build your own plugin. Sidekick is built on oclif, so any oclif plugin works as a Sidekick plugin. Create a package that exports oclif commands and install it with:

  # Install any oclif-compatible plugin directly
  sdkck plugins install my-custom-plugin

  # Or from a GitHub repo
  sdkck plugins install myorg/my-custom-plugin
  

Agent Workflow Recipes

• Pre-built command chains for common agent workflows (triage Sentry errors to Jira, sync Confluence docs with code changes, automated PR reviews with database checks).