copilotkit-demo-parity
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Python · Docker
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: copilotkit-demo-parity
description: Keeps examples/integrations/* demos aligned to the north-star (langgraph-python). Use when the u…
category: devops
runtime: Python / Docker
---
# copilotkit-demo-parity output preview
## PART A: Task fit
- Use case: Keeps examples/integrations/* demos aligned to the north-star (langgraph-python). Use when the user says "sync demos", "sync integrations", "port to north-star", "align integration demos", "parity check", or when working inside examples/integrations/ and tracked files diverge. Drives the pnpm parity:sync / parity:verify commands and handles the manual-merge zones (agent code, api route, Dockerfile). Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When this skill fires / Ground truth / Procedure: sync from north-star to instance(s)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Keeps examples/integrations/* demos aligned to the north-star (langgraph-python). Use when the user says "sync demos", "sync integrations", "port to north-star", "align integration demos", "parity check", or when working inside examples/integrations/ and tracked files diverge. Drives the pnpm parity:sync / parity:verify commands and handles the manual-merge zones (agent code, api route, Dockerfile). Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “When this skill fires / Ground truth / Procedure: sync from north-star to instance(s)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When this skill fires / Ground truth / Procedure: sync from north-star to instance(s)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: copilotkit-demo-parity
description: Keeps examples/integrations/* demos aligned to the north-star (langgraph-python). Use when the u…
category: devops
source: tomevault-io/skills-registry
---
# copilotkit-demo-parity
## When to use
- Keeps examples/integrations/* demos aligned to the north-star (langgraph-python). Use when the user says "sync demos"…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When this skill fires / Ground truth / Procedure: sync from north-star to instance(s)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "copilotkit-demo-parity" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When this skill fires / Ground truth / Procedure: sync from north-star to instance(s)
rules -> SKILL.md triggers / order / output contract
runtime -> Python / Docker | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} CopilotKit demo parity
Keeps the three (soon more) integration demos under examples/integrations/
aligned. langgraph-python is north-star; every other entry is an instance
that tracks it via examples/integrations/_parity/manifest.json.
When this skill fires
- User says "sync demos", "align integrations", "port to north-star", "parity check", "run parity sync".
- User edits a file under
examples/integrations/langgraph-python/**that is listed inmanifest.json→ tracked.verbatimFiles. - User is about to add a new integration under
examples/integrations/. pnpm parity:verifyis failing locally or in CI.
Ground truth
Read these first before making any parity decision — they override anything memorized:
examples/integrations/_parity/manifest.json— what is tracked, what is allowed to diverge, per-instance overrides.examples/integrations/_parity/canonical/PROMPT.md— the canonical system prompt. Every agent inlines this as a string literal in source. The verifier greps the canonical first line against each agent's source.examples/integrations/_parity/README.md— human-facing how-to.
Procedure: sync from north-star to instance(s)
Use when north-star changed and instances need to catch up, OR when a new instance is being bootstrapped.
- Confirm the north-star change is intentional. If the user changed
a file under
langgraph-python/, ask whether it should propagate. Changes toagent/are never auto-propagated. - Dry-run first.
Read the report: file count, rewritten package.json keys, prompt update.pnpm parity:sync --target=<instance> --dry-run - Apply.
pnpm parity:sync --target=<instance> # or --all to sync every instance - Resolve manual-merge zones. Sync does NOT touch:
agent/**— port agent code by hand. Seetracked.agentSurface.toolNamesandstateKeysinmanifest.jsonfor what must be present.src/app/api/copilotkit/**— api route differs across instances (north-star=LangGraphAgent, Docker instances=HttpAgent).Dockerfile,docker/Dockerfile.agent,serve.py,scripts/**— language-specific. Each instance keeps its own.
- Verify.
Exit 0 = green. Exit 1 = unresolved drift; fix until green.pnpm parity:verify --target=<instance>
Procedure: verify (CI-equivalent)
pnpm parity:verify # all instances
pnpm parity:verify --target=<instance>
pnpm parity:verify --json # machine-readable
Output kinds:
verbatim-file— byte-compare against north-star.package-json— tracked key mismatch vs expected value.prompt— canonical prompt first line not found in instance agent source. Instance agent needs the prompt inlined as a string literal.agent-tool— tool name from manifest not found in instance agent source. Usually means a tool was renamed or dropped; update manifest OR port the tool.agent-state— state key from manifest not found (warn only).
Procedure: add a new instance
- Create the demo dir under
examples/integrations/<name>/with the usual Next.js frontend root and anagent/subdir. - Add an entry to
manifest.json→instances:"<name>": { "role": "instance", "agent": { "language": "...", "runtime": "..." }, "allowedDivergence": [ "agent/**", "src/app/api/copilotkit/**", "Dockerfile", "docker/Dockerfile.agent", "serve.py", "scripts/**" ], "packageJsonOverrides": { "scripts.dev:agent": "<invocation>", "scripts.install:agent": "<install>" } } pnpm parity:sync --target=<name>- Port agent code (tool implementations, state schema, prompt loading).
Agent must read prompt from
agent/PROMPT.mdat startup. pnpm parity:verify --target=<name>until green.
Procedure: change the canonical prompt
- Edit
examples/integrations/_parity/canonical/PROMPT.md. pnpm parity:sync --all— writes the new prompt to every instance'sagent/PROMPT.md.- If the prompt change requires new tools or state keys, update
manifest.json→tracked.agentSurfaceto match, then port each instance's agent.
Procedure: change the tracked surface
To track a new file or key:
- Edit
manifest.json→tracked.verbatimFilesortracked.packageJsonPaths. - Run
pnpm parity:verify— instances will flag as drifted until synced. pnpm parity:sync --allto apply.
To stop tracking something, remove it from manifest.json. The verifier
and sync stop touching it. Any drift that already exists stays.
Red flags
| Signal | What it means | Do instead |
|---|---|---|
| "Just copy the file manually" | Bypasses the manifest | Add to tracked.verbatimFiles then sync |
| "Add a try/catch so verify doesn't fail" | Silencing drift | Resolve the drift or declare divergence |
"Move this into allowedDivergence to unblock" |
Scope creep | Only add to divergence with explicit reason |
pnpm parity:sync on north-star directly |
Overwrites canonical | Sync is instance-only; script refuses |
| Agent code copied between languages | Doesn't work | Port by hand; tracked.agentSurface names what |
Related skills
copilotkit-integrations— framework-specific wiring (LangGraph, CrewAI, Mastra, etc.) when bootstrapping a new instance.copilotkit-dev-workflow— monorepo conventions, Nx, commit format.docker-ci-safety— Dockerfile safety when editing per-instance container builds.
Source: CopilotKit/CopilotKit — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review