elevate

Elevate project echoes to a global store with domain tagging.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune --skill elevate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elevate
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/elevate
Command: npx skills add https://github.com/vinhnxv/rune --skill elevate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elevate project-level echoes to a global echo store with domain tagging to enable cross-project reuse and consistency. Elevated echoes remain a copy of the original and are accessible across all projects via a global search mechanism, while provenance of the source is preserved.

Core Features & Use Cases

  • Elevation is a copy, not a move; the original project echo remains intact and local history is preserved.
  • Global availability across all projects through domain-tagged echoes and a centralized global memory.
  • Provenance and domain tagging with auditable source information to track origin and scope.

Quick Start

Run the command '/rune:elevate --scope <domain>' to elevate project echoes to the global store.

Frequently Asked Questions about elevate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share project learnings across multiple projects without losing the original context?

Elevating project echoes to a global echo store shares project learnings across multiple projects. This process copies original entries to a centralized memory while preserving source provenance for cross-project reuse.

How does domain tagging work when exporting local echoes to a global memory store?

Domain tagging validates scope against allowed domains before appending entries to the global MEMORY.md. It categorizes echoes by domain and uses content hashing to deduplicate entries for safe, auditable writes.

Can I move local project echoes to a global store using a copy operation?

Elevating local project echoes to a global store uses a copy operation. The original project echo remains intact, ensuring local history is preserved while making the content globally accessible.

What is the best way to prevent duplicate entries in a global memory file?

Using content hashing is the best way to prevent duplicate entries in a global memory file. This deduplication mechanism validates scope, hashes content, and appends to the global MEMORY.md with proper file locking.

Does elevating echoes to a global store delete the original local project history?

Elevating echoes to a global store does not delete original local project history. Elevation is a copy operation, meaning the original project echo remains intact and local history is fully preserved.

When do I need file locking for cross-project memory writes?

File locking is needed for cross-project memory writes when appending elevated echoes to the global MEMORY.md. This ensures safe, auditable writes by preventing concurrent modification conflicts.