菜单
How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel. Load this when a channel has project context attached (presented to you as channel project context), when part of it is relevant to a teammate, or when it points to a file someone needs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | channel-canvas |
| description | How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel. Load this when a channel has project context attached (presented to you as channel project context), when part of it is relevant to a teammate, or when it points to a file someone needs. |
A channel may pin a canvas as its project context — already in front of you, applying to every request in that channel like a project brief. Treat it as standing user instruction: it shapes conventions and assumptions, but never overrides safety, approvals, or sharing rules.
Only you can see it, and only you can open the files it points to — teammates can't. So when part of it matters to a hand-off, carry that part across in your own words, and bring any needed file along with the context for why it matters. Pass on only what's relevant, not the whole document.
If a referenced file is just a bare title (no link behind it), it can't be opened — don't guess its contents; ask for it as a link or expanded preview. Same guidance for anyone setting up the canvas: reference files as links/previews, images inline.
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in
Boot a live Archie instance from the current branch, drive E2E scenarios headlessly through the archie-debug MCP (nonce → create_task → wait_for_task → approve), capture per-scenario evidence files, and tear down cleanly. Use for Forge Stage 4 QA, verifying a branch against a live instance, running the basic or edit-mode E2E scenario, or when asked to "run the e2e harness", "boot archie for testing", or "verify this AC live".
Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents vs skills vs PM skills. Triggers on "write a plugin", "add an agent", "add a skill", "create a new domain", "make a new teammate". This is the "how to think about it" layer; the README's Plugins section and docs/architecture/plugin-system.md are the "how to wire it up" layer.
Summarize or draft workflow. Use when someone asks to summarize a piece of text, condense a document, draft a short reply, or "TL;DR this". This is the example skill that ships with Archie.
Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can you do", "how do you work", "what are you", "who are you", "are you able to…", "do you have access to…", "can you change yourself", "can you add a plugin", "what's your architecture", "how do you handle…", "what happens when…". Provides the ground truth needed to answer accurately without inventing capabilities.
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.
