本文へ移動
cccskills
無料GitHub で公開

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.

CopilotKit/CopilotKit
インストール方法を見る

含まれるファイル（1）

  • SKILL.md5.0 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Intelligence Landing Page

/intelligence/overview is the product landing for CopilotKit Intelligence. New Intelligence features and new Intelligence docs pages must land on that page in the same change. Do not ship a guide that the landing does not name.

When To Use

Load this skill when:

  • A new Intelligence feature ships (threads, analytics, learning, channels, hosting, inspection, or a later pillar)
  • A page is added, renamed, or removed under showcase/shell-docs/src/content/docs/intelligence/
  • The shared Intelligence overview snippet or feature cards change

Before writing customer-facing words on those pages, also follow skills/intelligence-vocabulary/SKILL.md.

Do not load it for open-source frontend guides that do not use Intelligence, or for Inspector pane callouts (inspector-docs).

Landing sources

Edit these in the same change as the feature or docs page:

SurfaceFile
Hero CTA (CONNECT_HREF) and cardsshowcase/shell-docs/src/components/content/landing-pages/intelligence-overview.tsx
Body, quickstart link, hosting linksshowcase/shell-docs/src/content/snippets/shared/intelligence/overview.mdx
Section navshowcase/shell-docs/src/content/docs/intelligence/meta.json
Root sidebar Intelligence groupshowcase/shell-docs/src/content/docs/meta.json
Card and CTA testsshowcase/shell-docs/src/components/content/landing-pages/__tests__/intelligence-overview.test.tsx

The root overview page only wraps the snippet. Do not duplicate landing copy in docs/intelligence/overview.mdx.

Procedures

Procedure 1: Add a feature or docs page

  1. Add or update the guide page under docs/intelligence/ (or the existing threads/channels path the feature already uses).
  2. Put the page in intelligence/meta.json and in the Intelligence group in docs/meta.json when it belongs in the sidebar.
  3. Link the page from the shared snippet. A user-facing pillar gets a card in FEATURES in intelligence-overview.tsx with a unique CTA label. A hosting or account page gets a link under Choose where Intelligence runs. Every link must be a real URL.
  4. Do not add a second link for the same page. One page, one landing entry.
  5. If the feature is a named pillar in the hero, add it to the subtitle.
  6. Extend the tests in the same commit. Pin the new CTA href as a literal.

Procedure 2: Rename or move a page

  1. Update every landing CTA that pointed at the old path: card href, quickstart link, and the links under Choose where Intelligence runs.
  2. Update meta.json files.
  3. Update the tests that pin those hrefs.

Procedure 3: Remove a feature or page

  1. Remove the card or snippet link, subtitle mention, and nav entry.
  2. Remove the matching test assertions.
  3. Do not leave a landing link to a deleted page.

Decision Tree

  • New Intelligence feature or new Intelligence docs page: Procedure 1
  • Rename or move: Procedure 2
  • Remove: Procedure 3
  • Docs exist but landing does not name them: stop and run Procedure 1

Red Flags

SignalWhat it meansDo instead
Guide merged, landing unchangedReaders cannot find the featureProcedure 1 in the same PR
Card href and snippet link differTwo stories for one featureUse one URL
CTA points at the marketing site when a docs page existsLanding skips the guidePoint at the docs page
Hero subtitle lists a pillar with no cardCopy without a pathAdd the card, or drop the mention

Error Handling

  • No docs page yet: do not invent a guide. You can still add a snippet link that points at the current public product URL, and replace it when the guide ships.
  • Feature is Intelligence-only but lives outside docs/intelligence/: still add the landing CTA. Use the real path (/threads, /channels, and similar).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

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 end to end. Covers the whole path: inspecting or scaffolding the project, building the AG-UI agent, creating and reconciling the managed Channel with the public CopilotKit CLI, running the long-running host, and proving a real provider mention gets a reply. The workflow is not in this file. Run `npx --yes copilotkit@latest onboard start` and follow the graph it prints.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

chatgpt-app-builder

無料

DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK. Use when creating ChatGPT apps, building MCP servers with widgets, defining React widgets, working with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

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 you can read.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

copilotkit-channels

無料

Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope, because the CLI or dashboard wizard performs it. Creating a Slack app for the first time is not: if no Slack app exists yet, use setup-slack-channel for the provider half and return here for the code.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

copilotkit-cli

無料

Use for the CopilotKit CLI — `npx copilotkit@latest`. Covers proving a project's wiring with `verify` before debugging anything by hand, scaffolding with `create`, signing in and selecting a hosted Intelligence project, agent-assisted onboarding of an existing app, generating type-safe agent ids, and importing thread history. Reach for `verify` first whenever a CopilotKit app is not working.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

CopilotKit/CopilotKit3.8万2026年10月10日 更新

CopilotKit のスキルをすべて見る

このスキルの問題を報告する