invoker-setup

Validates the Invoker environment and configures Slack integration and remote SSH machines.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill invoker-setup-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoker-setup
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/invoker-setup
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill invoker-setup-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up Invoker on a new machine requires verifying many tools (git, pnpm, gh, docker, codex, claude, and more), and optionally wiring up a Slack bot and remote SSH machines — a process full of easy-to-miss failure modes like stale Slack scopes or PATH mismatches. This Skill automates environment validation and guides the optional Slack and machine setup end to end. ## Core Features & Use Cases - Environment validation: Runs invoker-cli doctor --json to check the canonical tool set, config, planning tools, and default preset, surfacing remediation for each failing check, with invoker-cli doctor --fix to auto-install missing tools. - Guided Slack integration: Walks through creating a Slack app from a generated manifest, collecting the bot token, app token, and signing secret, then validating credentials against the live Slack API with invoker-cli setup slack --check. - Remote machine setup: Adds SSH machines via invoker-cli setup machines, probing connectivity before writing anything to ~/.invoker/config.json. - Use Case: A developer installs Invoker on a fresh laptop and asks the agent to get them "good to go" — the agent diagnoses a missing gh CLI, installs it, then optionally sets up the Slack bot and confirms every credential check passes. ## Quick Start Ask the agent to set up Invoker and check whether this machine is good to go, then follow its prompts for the optional Slack and remote machine setup.

Frequently Asked Questions about invoker-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Invoker on a new machine?

Run invoker-cli doctor --json to validate the environment, then invoker-cli doctor --fix to auto-install missing tools like git, pnpm, gh, docker, codex, and claude. Slack and remote machines are optional and configured separately with invoker-cli setup slack and invoker-cli setup machines.

How do I set up the Invoker Slack bot integration?

Run invoker-cli setup slack, which writes a ready-to-paste app manifest to ~/.invoker/slack-app-manifest.json. Create the app at api.slack.com from that manifest, install it to your workspace, then provide the bot token, app-level token, signing secret, and lobby channel ID.

Why does Invoker fail with 'spawn cursor ENOENT' on Slack?

This happens when the configured planner command is not on Invoker's own PATH, even if it works in your terminal. Restart Invoker to refresh its shell environment, or install the tool or configure a preset whose command is available.

Why do new Slack bot scopes not take effect after adding them?

Adding scopes after installing the app does not update the existing token. You must click Reinstall to Workspace in the Slack app settings, or the bot keeps its old insufficient scopes and the scope check will fail.

Is the Slack integration required to use Invoker?

No, Slack is optional. A user who declines Slack setup is still good to go for CLI and desktop UI workflows, and invoker-cli setup slack can add the integration at any later time.

Where are Invoker Slack credentials stored?

Credentials are written only to ~/.invoker/.env with 0600 permissions by the setup wizard. They are validated against the live Slack API using auth.test, apps.connections.open, and conversations.info checks.