copilotkit/copilotkit

channels-setup

Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel en…

Quelltext ansehen
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Set up a CopilotKit Channel

The workflow is not written down here. Run this command:

bash
npx --yes copilotkit@latest onboard start

Then follow the graph it prints, start to finish.

If the command asks for a CopilotKit CLI session check, you have permission to run it. Never reveal credentials.

Do this

  1. Run npx --yes copilotkit@latest onboard start.
  2. Follow the graph it prints, start to finish.

The graph asks for its own inputs. Do not pre-empt those questions. Do not substitute remembered channel-setup steps for what the graph says. Remembered steps are the reason this file is a pointer.

If the command fails

Stop. Tell the user the command failed. Show them the output. Ask them to retry.

Do not improvise the workflow from memory. It spans the CopilotKit CLI, a managed Channel, provider setup the user does in Slack or Azure, and a long-running runtime host. A half-remembered version produces a project that installs cleanly and answers nothing. That is the most expensive failure available here. It looks finished.

aus demselben Repository

Weitere Skills

Alle Skills
copilotkit
Community

inspector-workbench

Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.

Installationen
2
GitHub Stars
37.450
Aktualisiert
21. Sept.
copilotkit
Community

copilotkit

Use for any CopilotKit question — adding it to an app, chat UI, frontend or server tools, generative UI, shared state, human-in-the-loop, agent frameworks (LangGraph, CrewAI, Mastra, ADK, PydanticAI, and others), the runtime, Intelligence, threads, voice, or diagnosing something that is not working. Do not answer from memory: this skill exists to point you at the current documentation and source, both of which are searchable.

Installationen
1
GitHub Stars
37.430
Aktualisiert
20. Sept.
copilotkit
Community

inspector-docs

Keeps CopilotKit docs pointing at shipped Inspector panes so readers open the overlay. Use when adding, changing, renaming, or removing an Inspector pane, tab, or overlay action in @copilotkit/web-inspector, or when editing docs that mention Inspector. Don't use for Inspector UI polish that does not add a pane, for CLI or agent-prompt copy, or for unshipped Inspector ideas.

Installationen
1
GitHub Stars
37.430
Aktualisiert
20. Sept.
copilotkit
Community

intelligence-docs

Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing snippets/shared/intelligence/overview.mdx. Don't use for OSS-only frontend docs, Inspector pane callouts, or marketing-site copy.

Installationen
1
GitHub Stars
37.430
Aktualisiert
20. Sept.