Skip to content
Skillett Docs
Get Started

Quickstart

This guide walks you through the complete flow: install, authenticate, connect GitHub, and create your first issue — all from the terminal.

Prerequisites

Section titled “Prerequisites”
  • Node.js 18+ installed (required to run the CLI via npx)

Setup

Section titled “Setup”

  1. Run the CLI

    Terminal window
    npx skillett login

    This starts the device authorization flow. The CLI opens your browser and displays a code like ABCD-1234.

  2. Authorize in browser

    Sign in (or create an account) on the Skillett dashboard. Enter the code displayed in your terminal. Once confirmed, you’re redirected to the API Keys page.

  3. Copy your API key

    Create an API key on the dashboard (format: sk_...). Paste it into the CLI when prompted.

    Terminal window
    ? Paste your API key: sk_a1b2c3d4e5f6...
    ✓ Logged in as david@example.com
    ✓ Core skill installed

    The CLI saves your key and installs the core Skillett skill pointer for your agent platform.

  4. Connect GitHub

    Terminal window
    skillett connect github

    This opens an OAuth consent screen. Authorize the requested scopes, then return to your terminal.

    { "status": "connected", "integration": "github" }

  5. Browse available skills

    Terminal window
    skillett skills github

    Returns all available endpoint categories (issues, pull requests, repositories, search, etc.) with their actions.

  6. Run your first skill

    Terminal window
    skillett run github create_issue --repo acme/webapp --title "First issue from Skillett"
    {
      "status": 200,
      "data": {
        "id": 42,
        "number": 1,
        "title": "First issue from Skillett",
        "html_url": "https://github.com/acme/webapp/issues/1"
      }
    }

What just happened?

Section titled “What just happened?”
  1. The CLI authenticated you via device authorization (RFC 8628)
  2. Your API key was saved locally and the core skill pointer was installed
  3. GitHub was connected via OAuth — tokens are stored server-side, encrypted
  4. The CLI called POST /v1/github/create_issue which proxied to the GitHub API
  5. GitHub’s response was returned as structured JSON

Next steps

Section titled “Next steps”