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

intelligence-vocabulary

Locks customer-facing CopilotKit Intelligence docs to one approved name per concept. Use when writing, editing, or reviewing Intelligence docs, nav labels, signup labels, or image alt text in showcase/shell-docs. Don't use for renaming code identifiers, route slugs, env vars, API fields, or component names, or for docs that do not mention Intelligence.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.0 KB
  • references/words.md10.0 KB

SKILL.md(原文)

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

Intelligence Vocabulary

Customer-facing Intelligence docs use one name per concept. A second name for the same thing is a regression.

When To Use

Load this skill before writing or editing prose a customer reads about CopilotKit Intelligence. That includes pages, snippets, nav titles, button labels, and image alt text under showcase/shell-docs.

Also load skills/intelligence-docs/SKILL.md when the change adds, renames, or removes an Intelligence page. That skill keeps the landing page in sync. This skill owns the words.

Do not load this skill to rename code. Identifiers, route slugs, env vars, API fields, and component names stay as they are, even when a Stop word appears inside them.

Procedures

Procedure 1: Apply the word list

  1. Read references/words.md before writing or editing customer-facing Intelligence prose.
  2. Use the Use column for headings, nav titles, button labels, alt text, and body prose.
  3. Keep plan names as Developer, Team, Team Self-hosted, and Enterprise.
  4. If a fact already has a home in references/words.md, link to that page. Do not explain the fact again under a second name.
  5. Write Inspector click steps with the labels the shipped controls render: Rich Threads and Automatic Learning.

Procedure 2: Check the change

  1. Search the added or edited prose for every phrase in the Stop column of references/words.md.
  2. Keep a hit that the exception list in references/words.md names.
  3. Rewrite every other hit to the Use word for that concept.
  4. Leave identifiers, slugs, env vars, API fields, and component names unchanged.

Decision Tree

  • Customer-facing Intelligence prose, labels, or alt text: Procedure 1, then Procedure 2
  • Page added, renamed, or removed: this skill for the words, and skills/intelligence-docs/SKILL.md for the landing page
  • The only edit is code, a slug, an env var, or an API field: stop. Do not rename it to match the word list
  • The page does not mention Intelligence: stop

Red Flags

SignalWhat it meansDo instead
Two names for one concept on the same pageThe word list was skippedProcedure 2
"managed" or "hosted" as the name of the CopilotKit-operated deploymentThe deployment name driftedWrite cloud-hosted
A Stop word removed by renaming a component, slug, or env varThe skill was applied to codeRestore the identifier. Change only customer prose
Clerk, or a rollout cutoff, added to a customer pageInternal implementation leakedDelete that sentence. Say what the customer does

Error Handling

  • A Stop phrase is inside an identifier: leave the identifier. Change the surrounding prose only when that prose uses the Stop word as a customer-facing name.
  • A hit is on the exception list: keep it. Do not "fix" managed Channel, customer-managed, a hosted zone, a ticket id, or a plan name.
  • The approved word and the visible product label disagree: use the label the shipped control renders for a click step. Record the conflict. Do not invent a third name.
  • No home exists for a new fact: stop and name the missing page. Do not park the fact under a nearby page with a new synonym.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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日 更新

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日 更新

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日 更新

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日 更新

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日 更新

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 のスキルをすべて見る

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