Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Write messages to your future self — or your future team — that unlock when specific code conditions are met.
Install Time Capsule
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsule --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/time-capsule .claude/skills/time-capsule && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .claude/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsuleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsule --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/time-capsule .agents/skills/time-capsule && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .agents/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsule --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/time-capsule .cursor/skills/time-capsule && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .cursor/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/time-capsule--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsule --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/time-capsule .gemini/skills/time-capsule && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .gemini/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsuleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/time-capsule .github/skills/time-capsule && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .github/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills time-capsule --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/time-capsule .opencode/skills/time-capsule && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "time-capsule" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/time-capsule into .opencode/skills/time-capsule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "time-capsule", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
time-capsule- GitHub stars
- 2.2k
- Token cost
- ~3.8k tokens
- SKILL.md length
- 480 words
- Files
- 2
- Skills in repo
- 1,235
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write messages to your future self — or your future team — that unlock when specific code conditions are met.
- Tasks that involve Knowledge bases
- SKILL.md covers What It Does, Capsule Types, Trigger Types and Burying a Capsule, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Time Capsule is an agent skill from LeoYeAI/openclaw-master-skills. Write messages to your future self — or your future team — that unlock when specific code conditions are met. "Dear future me: if you're reading this, someone finally tried to refactor the billing module. Here's what you need to know..." Encodes institutional knowledge into the codebase itself, triggered exactly when it's needed.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Knowledge Management, covering Knowledge bases. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- Tasks that involve Knowledge bases
Example prompts
- “Dear future me: if you”
- “s what you need to know...”
- “/time-capsule”
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Time Capsule loads about 3.8k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 480 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 480 words, ~3,810 tokens.
Download SKILL.mdSave it as
.claude/skills/time-capsule/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- time-capsule
- description
- Write messages to your future self — or your future team — that unlock when specific code conditions are met. "Dear future me: if you're reading this, someone finally tried to refactor the billing module. Here's what you need to know..." Encodes institutional knowledge into the codebase itself, triggered exactly when it's needed.
- version
- 1.0.0
- author
- J. DeVere Cooley
- category
- fun-tools
- tags
- knowledge-transfer, time-delayed, institutional-memory, fun
Time Capsule
"The best time to document your decisions was when you made them. The second best time is to leave a message for whoever has to deal with them later."
What It Does
You know things right now that will be desperately needed later — but you don't know when later. Time Capsule lets you bury messages in the codebase that surface automatically when specific conditions are triggered:
- When someone finally touches that file nobody's touched in 2 years
- When the TODO count in a module exceeds a threshold
- When a specific dependency gets upgraded
- When test coverage drops below a certain percentage
- When a new developer makes their first commit
- On a specific date ("Hey team, the API license expires next month")
The message arrives exactly when it's relevant — not before (when it would be noise) and not after (when it would be too late).
Capsule Types
The Welcome Capsule
Triggered when a new contributor makes their first commit
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @jcooley on 2025-06-15 ║
║ Trigger: New contributor detected ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Dear new team member, ║
║ ║
║ Welcome! Here's what I wish someone told me on day one: ║
║ ║
║ 1. The "legacy" folder isn't legacy — it's the billing ║
║ engine and it handles $2M/day. Don't rename anything. ║
║ ║
║ 2. Tests in /integration are slow (40 min). Run /unit ║
║ first. Only run integration before pushing to main. ║
║ ║
║ 3. If you see a function called `doTheThing()` in ║
║ auth.ts — yes, we know. No, don't fix it yet. There's ║
║ a Time Capsule on it. You'll understand when it opens. ║
║ ║
║ 4. The real architecture diagram is in /docs/actual.png, ║
║ not /docs/architecture.png (which is from 2023). ║
║ ║
║ Good luck. You're going to love it here. ║
║ — The team, June 2025 ║
╚══════════════════════════════════════════════════════════════╝The Warning Capsule
Triggered when someone modifies a specific dangerous file
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @sarah on 2025-09-22 ║
║ Trigger: src/payments/reconciliation.ts was modified ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ STOP. Read this before you change anything. ║
║ ║
║ This file handles payment reconciliation with Stripe. ║
║ It looks simple. It is NOT simple. Here's what you need ║
║ to know: ║
║ ║
║ - The 3-second delay on line 47 is NOT arbitrary. ║
║ Stripe's webhook delivery has a race condition. ║
║ Without the delay, 1 in ~500 payments double-charges. ║
║ We learned this the hard way. Ticket: INC-2847. ║
║ ║
║ - The `Math.round()` on line 63 MUST stay. ║
║ Floating point + currency = disaster. We lost $12,847 ║
║ over 3 weeks before we found this. Ticket: INC-3012. ║
║ ║
║ - If you need to test this, use the Stripe sandbox with ║
║ the webhook replay tool. Do NOT test with real charges. ║
║ (Yes, someone did. No, we don't talk about it.) ║
║ ║
║ If you're refactoring: keep all three invariants above. ║
║ If you're fixing a bug: check INC-2847 and INC-3012 first. ║
║ ║
║ — Sarah, the last person who touched this file ║
╚══════════════════════════════════════════════════════════════╝The Date Capsule
Triggered on a specific calendar date
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @mike on 2025-11-01 ║
║ Trigger: Date reached: March 1, 2026 ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Hey team, ║
║ ║
║ The GeoLocation API license expires on March 31, 2026. ║
║ Renewal costs $4,800/year. The free alternative (OpenCage) ║
║ exists but doesn't support batch queries. ║
║ ║
║ Decision needed: ║
║ 1. Renew the license ($4,800) ║
║ 2. Migrate to OpenCage (est. 3 dev-days) ║
║ 3. Build our own geocoding cache (est. 2 dev-weeks) ║
║ ║
║ I buried this 4 months early so you have time to decide. ║
║ Don't let it expire accidentally like the SSL cert in 2024. ║
║ ║
║ — Mike ║
╚══════════════════════════════════════════════════════════════╝The Threshold Capsule
Triggered when a code metric crosses a threshold
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @jcooley on 2025-08-10 ║
║ Trigger: src/checkout/ test coverage dropped below 80% ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Coverage dropped below 80%. I knew this day would come. ║
║ ║
║ When I wrote the checkout tests in August 2025, coverage ║
║ was 94%. I'm writing this capsule because I know that ║
║ deadline pressure will slowly erode it. Here's the deal: ║
║ ║
║ The untested code paths are where the money bugs hide. ║
║ Specifically: multi-currency, discount stacking, and ║
║ partial refunds. If coverage dropped, it's probably ║
║ because someone added a feature without adding tests. ║
║ ║
║ Recovery plan: ║
║ 1. Run: npm test -- --coverage checkout/ ║
║ 2. The red lines are the new code without tests ║
║ 3. Priority: anything touching money gets tests FIRST ║
║ 4. Don't let this drop below 70%. Below 70%, the ║
║ checkout module becomes unfixable without fear. ║
║ ║
║ I've buried another capsule at 70%. You don't want to ║
║ read that one. ║
║ ║
║ — Past You (who had more test coverage and more optimism) ║
╚══════════════════════════════════════════════════════════════╝The Dependency Capsule
Triggered when a specific dependency is updated
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @dev_b on 2025-07-20 ║
║ Trigger: react upgraded past v19 ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ You're upgrading React. Brave. Here's the map: ║
║ ║
║ Known pain points from our codebase: ║
║ 1. UserDashboard uses a class component with ║
║ componentWillMount (deprecated). Convert to useEffect. ║
║ 2. We have a custom useRouter hook that wraps React Router. ║
║ Check if the new React version broke the Router API. ║
║ 3. The theme provider in src/ui/theme.tsx uses ║
║ legacy context API. Must migrate to createContext. ║
║ 4. Our test setup mocks ReactDOM.render(). If React 19+ ║
║ changes the render API, ALL test mocks need updating. ║
║ ║
║ Estimated effort: 2-3 days if you know about these. ║
║ Estimated effort: 2-3 WEEKS if you don't. ║
║ ║
║ You're welcome. ║
╚══════════════════════════════════════════════════════════════╝The Achievement Capsule
Triggered when a milestone is reached
╔══════════════════════════════════════════════════════════════╗
║ ⏳ TIME CAPSULE OPENED! ║
║ Buried by: @jcooley on 2025-03-15 ║
║ Trigger: Repository reached 1,000 commits ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ 🎉 1,000 COMMITS! 🎉 ║
║ ║
║ When I buried this capsule, we had 247 commits and ║
║ 2 developers. I wasn't sure we'd make it here. ║
║ ║
║ Whoever opened this: look how far we've come. ║
║ The early commits were messy. The architecture was wrong. ║
║ We rewrote auth twice and the database three times. ║
║ But here we are — 1,000 commits of learning, building, ║
║ breaking, and fixing. ║
║ ║
║ Take a moment. Then get back to work. There's a capsule ║
║ at 10,000 and it's going to be even better. ║
║ ║
║ — Commit #247 ║
╚══════════════════════════════════════════════════════════════╝Trigger Types
| Trigger | Condition | Use Case |
|---|---|---|
| File Touch | Specific file is modified | Warn about landmines, explain non-obvious code |
| Date | Calendar date is reached | License expiry, scheduled reviews, reminders |
| Threshold | Metric crosses a value | Coverage drop, bug count spike, dependency age |
| Dependency | Package is updated/removed | Migration guides, known gotchas |
| New Contributor | First commit from unknown author | Onboarding tips, welcome messages |
| Milestone | Commit count, tag, release | Celebrations, retrospective notes |
| Pattern | Specific code pattern appears | "If you're writing another retry loop, see utils/retry.ts" |
| Absence | No commits for N days | "If nobody's touched this in 6 months, here's what to know..." |
Show full SKILL.md (173 more words)Show less
Burying a Capsule
╔══════════════════════════════════════════════════════════════╗
║ ⏳ BURY A TIME CAPSULE ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ TRIGGER: When does this capsule open? ║
║ > When someone modifies src/payments/reconciliation.ts ║
║ ║
║ MESSAGE: What should future developers know? ║
║ > [Your message here...] ║
║ ║
║ AUTHOR: Who buried this? ║
║ > @sarah ║
║ ║
║ EXPIRY: When should this capsule be destroyed if not opened?║
║ > Never (default) / After 1 year / After specific date ║
║ ║
║ ✅ Capsule buried. ║
║ It will open the next time someone modifies ║
║ src/payments/reconciliation.ts. ║
╚══════════════════════════════════════════════════════════════╝When to Invoke
- After making a non-obvious decision — bury a capsule explaining WHY for the next person who touches it
- Before leaving a team or project — leave capsules with everything the next person needs to know
- When you discover a landmine — mark it so the next person doesn't step on it
- For scheduled events — license renewals, deprecation deadlines, review dates
- For celebrations — commit milestones, release targets, team achievements
- When writing code you know will be confusing — leave a map for the future explorer
Why It Matters
Comments go stale. Documentation goes unread. Slack messages get buried. Wiki pages get forgotten. But a Time Capsule that opens exactly when someone needs it — triggered by the very action that makes the knowledge relevant — that's institutional memory with a pulse.
It's fun to bury them. It's even more fun to discover them. And the knowledge they carry can save hours, days, or (in the case of the Stripe reconciliation capsule) thousands of dollars.
Zero external dependencies. Zero API calls. Pure event-triggered knowledge delivery.
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/time-capsule of LeoYeAI/openclaw-master-skills.
- SKILL.md
- _meta.json
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Time Capsule next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Time Capsule this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence | |
| Xhs Virtual Productchenjin-cmd/xhs-virtual-product | 726 | — | ~862 | Automated safety check: Pass | MIT | |
| OpenkbVectifyAI/OpenKB | 4.8k | 1 repos | ~2k | Automated safety check: Warn | Apache-2.0 | |
| Learn From Materialsdmoshehun-prog/learn-from-materials | 937 | — | ~7.9k | Automated safety check: Pass | MIT |
Similar skills
Find And Cite
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
Xhs Virtual Product
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
Openkb
VectifyAI/OpenKB
A skill your agent uses when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an…
Learn From Materials
dmoshehun-prog/learn-from-materials
Turns books, PDFs, slides and web pages into a source-grounded knowledge base and an interactive learning page in English or Chinese, with quizzes, relationship maps and reusable methodology notes.
Onyx CLI
onyx-dot-app/onyx
Query the Onyx knowledge base using the onyx-cli command. An agent skill from onyx-dot-app/onyx.
More from LeoYeAI/openclaw-master-skills
All 1,235 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Categories
Questions about Time Capsule
What does Time Capsule do?
Write messages to your future self — or your future team — that unlock when specific code conditions are met. Time Capsule is an agent skill from LeoYeAI/openclaw-master-skills. Write messages to your future self — or your future team — that unlock when specific code conditions are met.
When should I use Time Capsule?
Time Capsule fits situations like: tasks that involve Knowledge bases.
How do I install Time Capsule in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a claude-code`. Or copy the skill folder (skills/time-capsule in LeoYeAI/openclaw-master-skills) into .claude/skills/time-capsule in your project. Claude Code loads it when a task matches its description.
How do I install Time Capsule in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a codex`. Or copy the skill folder (skills/time-capsule in LeoYeAI/openclaw-master-skills) into .agents/skills/time-capsule in your project. Codex loads it when a task matches its description.
Can I use Time Capsule in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill time-capsule -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/time-capsule, .gemini/skills/time-capsule, .github/skills/time-capsule and .opencode/skills/time-capsule in your project.
What does Time Capsule need to run?
SKILL.md names no scripts, command-line tools or credentials: Time Capsule is instructions for the agent only.
Does Time Capsule access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Time Capsule safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Time Capsule use?
Time Capsule is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Time Capsule use?
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Time Capsule?
Skills that share tags, products or a category with Time Capsule: Capture Conversation (outline/outline, 41k stars), Find And Cite (outline/outline, 41k stars), Xhs Virtual Product (chenjin-cmd/xhs-virtual-product, 726 stars) and Openkb (VectifyAI/OpenKB, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Time Capsule?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.