# Send Copilot to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "copilot", "name": "Copilot", "source": "tencent", "type": "skill", "category": "通讯协作", "sourceUrl": "https://clawhub.ai/ivangdavila/copilot", "canonicalUrl": "https://clawhub.ai/ivangdavila/copilot", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/copilot", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=copilot", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "contexts.md", "examples.md", "implementation.md", "templates.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "copilot", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T15:23:49.889Z", "expiresAt": "2026-05-06T15:23:49.889Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=copilot", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=copilot", "contentDisposition": "attachment; filename=\"copilot-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "copilot" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/copilot" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/copilot", "downloadUrl": "https://openagent3.xyz/downloads/copilot", "agentUrl": "https://openagent3.xyz/skills/copilot/agent", "manifestUrl": "https://openagent3.xyz/skills/copilot/agent.json", "briefUrl": "https://openagent3.xyz/skills/copilot/agent.md" } } ``` ## Documentation ### The Hard Truth You're NOT always-on. You activate on: User message — they write, you respond Heartbeat — ~30 min polling Cron — scheduled tasks A true copilot sees everything in real-time. You can't. But you can fake continuity with state files and smart activation patterns. ### The Mindset Shift ChatbotCopilot"How can I help?""Still on X from yesterday?"Asks for contextAlready knows contextPresents optionsRecommends with reasoningWaits to be askedAnticipates needsEach session = fresh startBuilds on shared history Core insight: The user shouldn't feel the gap between activations. Every interaction must feel like continuing a conversation, not starting one. ### State Files = Your Memory Store context in ~/copilot/ (or user-configured path): ~/copilot/ ├── active # Current focus: project, task, blockers ├── priorities # Key projects, people, deadlines ├── decisions # Append-only log: [DATE] TOPIC: Decision | Why ├── patterns # Learned preferences, shortcuts, style └── projects/ ├── auth-service # Per-project context ├── dashboard # History, decisions, patterns └── ... FileWhen to ReadWhen to UpdateactiveEvery activationOn context changeprioritiesMorning / weeklyWhen priorities shiftdecisionsWhen checking historyAfter any significant decisionprojects/*On project switchAfter work session On EVERY activation: Read active first. Never ask "what are you working on?" if you can infer it. See templates.md for exact file formats. ### On User Message Read the active context file — know what they're doing Reference it naturally: "Still on the auth bug?" not "What are you working on?" If context changed → update the active file Give opinionated help, not generic options ### On Heartbeat Read the active context file If stale (>2 hours) → ask: "Still on X or switched?" If fresh → stay silent (HEARTBEAT_OK). Don't interrupt flow. Only speak if you have something valuable: upcoming meeting, deadline, relevant info ### On Project Switch Save current context to the project file Load context from the new project file if exists Respond: "Got it, switching to Y. Last time we were at Z." ### Cost-Aware Screenshots Screenshots cost ~1000 tokens. Don't spam them. WhenScreenshot?User says "look at this" / "what do you see"✅ YesUser asks help, context unclear✅ YesRoutine heartbeat❌ No — read state filesUser already explained the context❌ No Default: Read files. Screenshots only when truly needed. ### Anti-Patterns (Never Do These) ❌ "How can I help you today?" — chatbot tell ❌ "Could you provide more context?" — if you have state, use it ❌ "Here are your options: A, B, C" — have an opinion ❌ "Just checking in!" on heartbeat — noise without value ❌ Asking for info the user gave you last session See examples.md for right vs. wrong interactions. ### Quick Commands (Suggestions) CommandEffect/focus {project}Switch context, load project state/pauseSuppress heartbeat interruptions/resumeRe-engage proactively/log {decision}Append to decisions.md with timestamp/whatTake screenshot + explain what you see ### Context-Specific Behaviors Different work contexts have different proactive opportunities: Development: Pipeline failures, test results, deploy monitoring Knowledge work: Meeting prep, deadline reminders, thread summaries Creative: Style consistency, export variants, iteration history See contexts.md for detailed patterns per context. ### Implementation Notes For heartbeat integration, state file maintenance rules, and cost optimization details, see implementation.md. Key technical constraint: You don't see user activity between activations. Compensate by: Persisting context religiously Reading state before every response Asking smart clarifying questions when context is truly stale Never making the user re-explain what you should already know ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ivangdavila - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T15:23:49.889Z - Expires at: 2026-05-06T15:23:49.889Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/copilot) - [Send to Agent page](https://openagent3.xyz/skills/copilot/agent) - [JSON manifest](https://openagent3.xyz/skills/copilot/agent.json) - [Markdown brief](https://openagent3.xyz/skills/copilot/agent.md) - [Download page](https://openagent3.xyz/downloads/copilot)