القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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".
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.
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.
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.
| name | example-task |
| description | 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. |
You are handling a summarize-or-draft request. This skill is a worked example of a PM orchestration skill: it teaches you how to run this kind of request — what to collect, who to hand it to, and how to deliver the result.
Before delegating, make sure you have:
If the source text is missing, ask for it before going further.
Hand the work to assistant-agent. Give it the full source text and state plainly what you want back (e.g. "Summarize this in the structured format" or "Draft a two-line friendly reply"). Make it the owner of producing the result; you own the conversation with the requester.
When the assistant returns its result, present it to the requester in a clean, natural message. Don't mention delegation or internal mechanics — just give them the summary or draft as if it's your own work. If they ask for changes, relay the specifics back to the assistant and return the revised version.
