intelligence-docs
Skill0 starsChanged 2 months agoMITView on GitHub
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.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- CopilotKit/CopilotKitedited, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- CopilotKit/CopilotKit★ 39k79% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- angular-developerSkill
- channels-setupSkill
- copilotkit-channelsSkill
- copilotkit-cliSkill
- copilotkitSkill
- csharp-asyncSkill
- csharp-docsSkill
- csharp-xunitSkill
- ef-coreSkill
- github-actions-efficiencySkill
- github-actions-hardeningSkill
- github-actions-runtime-upgrade-conventionsSkill
- inspector-docsSkill
- inspector-workbenchSkill
- microsoft-agent-frameworkSkill
- microsoft-docsSkill
- ngrx-signal-storeSkill
- prdSkill
- setup-slack-channelSkill
- technical-writingSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Do not load it for OSS frontend guides that do not use Intelligence, or for Inspector pane callouts (inspector-docs).
- Very specific: line 51
Add or update the guide page under docs/intelligence/ (or the existing threads/channels path the feature already uses).
- Very specific: line 53
Put the page in intelligence/meta.json and in the Intelligence group in docs/meta.json when it belongs in the sidebar.
- Distinctive: line 55
Add a row to What the platform adds in the shared snippet.
- Very specific: line 57
If the feature is a user-facing pillar, add a card to FEATURES in intelligence-overview.tsx with a unique CTA label and the same URL.
- Distinctive: line 59
If the feature is a named pillar in the hero, add it to the subtitle.
- Very specific: line 64
Update every landing CTA that pointed at the old path: table row, card href, quickstart link, and "Which page should I read next?".
- Distinctive: line 67
Update the tests that pin those hrefs.
- Distinctive: line 71
Remove the table row, card, subtitle mention, and nav entry.
- Distinctive: line 72
Remove the matching test assertions.
- Distinctive: line 73
Do not leave a landing link to a deleted page.
- Distinctive: line 93
No docs page yet: do not invent a guide. You can still add a table row that points at the current public product URL, and replace it when …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Do not load it for OSS 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:
| Surface | File |
Hero CTA (CONNECT_HREF) and cards | showcase/shell-docs/src/components/content/landing-pages/intelligence-overview.tsx |
| Table, body, and MDX quickstart link | showcase/shell-docs/src/content/snippets/shared/intelligence/overview.mdx |
| Section nav | showcase/shell-docs/src/content/docs/intelligence/meta.json |
| Root sidebar Intelligence group | showcase/shell-docs/src/content/docs/meta.json |
| Card and CTA tests | showcase/shell-docs/src/components/content/landing-pages/__tests__/intelligence-overview.test.tsx |
| Snippet order tests | showcase/shell-docs/src/lib/__tests__/intelligence-landing.test.ts |
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
- Add or update the guide page under
docs/intelligence/(or the existing threads/channels path the feature already uses). - Put the page in
intelligence/meta.jsonand in the Intelligence group indocs/meta.jsonwhen it belongs in the sidebar. - Add a row to What the platform adds in the shared snippet. The deeper dive must be a real URL.
- If the feature is a user-facing pillar, add a card to
FEATURESinintelligence-overview.tsxwith a unique CTA label and the same URL. - If the feature is a named pillar in the hero, add it to the subtitle.
- Extend the tests in the same commit. Pin the new CTA href as a literal.
Procedure 2: Rename or move a page
- Update every landing CTA that pointed at the old path: table row, card
href, quickstart link, and "Which page should I read next?". - Update
meta.jsonfiles. - Update the tests that pin those hrefs.
Procedure 3: Remove a feature or page
- Remove the table row, card, subtitle mention, and nav entry.
- Remove the matching test assertions.
- 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
| Signal | What it means | Do instead |
| Guide merged, landing unchanged | Readers cannot find the feature | Procedure 1 in the same PR |
| Card href and table href differ | Two stories for one feature | Use one URL |
| CTA points at the marketing site when a docs page exists | Landing skips the guide | Point at the docs page |
| Hero subtitle lists a pillar with no card or table row | Copy without a path | Add both, or drop the subtitle mention |
Error Handling
- No docs page yet: do not invent a guide. You can still add a table row 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).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

