Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Communication & Collaboration
Copilot
Transform your agent from chatbot to copilot with context persistence, proactive anticipation, and opinionated help across sessions.
skill openclawclawhub Free
Transform your agent from chatbot to copilot with context persistence, proactive anticipation, and opinionated help across sessions.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, contexts.md, examples.md, implementation.md, templates.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
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
Category context
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs
- SKILL.md
- contexts.md
- examples.md
- implementation.md
- templates.md