scope-recall-setup

Agent Skills › 410979729/scope-recall-hermes › scope-recall-setup

scope-recall-setup

GitHub

自动安装、升级或迁移 Scope Recall，区分首次安装与旧版迁移。负责环境检测、路径解析、备份及重启，保留用户配置并报告状态。

maintenance/skills/scope-recall-setup/SKILL.md 410979729/scope-recall-hermes

Trigger Scenarios

用户请求设置 Scope Recall 用户请求更新 Scope Recall 用户请求迁移旧版 Scope Recall 记忆

Install

npx skills add 410979729/scope-recall-hermes --skill scope-recall-setup -g -y

More Options

Non-standard path

npx skills add https://github.com/410979729/scope-recall-hermes/tree/main/maintenance/skills/scope-recall-setup -g -y

Use without installing

npx skills use 410979729/scope-recall-hermes@scope-recall-setup

指定 Agent (Claude Code)

npx skills add 410979729/scope-recall-hermes --skill scope-recall-setup -a claude-code -g -y

安装 repo 全部 skill

npx skills add 410979729/scope-recall-hermes --all -g -y

预览 repo 内 skill

npx skills add 410979729/scope-recall-hermes --list

SKILL.md

Frontmatter

{
    "name": "scope-recall-setup",
    "description": "Install or upgrade Scope Recall when the user asks the agent to set it up, update it, or migrate old Scope Recall memories. Automatically distinguish first-time installation from legacy migration."
}

The user asks for the result; perform the technical work as their agent.

Find the actual host's instance home and Python/plugin environment. Inspect with scope-recall setup --host <hermes-or-codex> --home <instance-home>. Check active host configuration first; pass --database <actual-db> for a custom path. Absence at default paths alone must not hide an old database. If the old package lacks this entry point, inspect the new release in an isolated helper environment before touching the running installation.
Follow its route. fresh_install goes straight to normal installation and host checks. current_upgrade preserves the current database format. legacy_migration uses the bundled workflow printed by scope-recall setup --workflow.
Resolve paths, backups, exact audience mapping and restart commands yourself. Do not ask the user to run commands or review individual memories. Do not replace uncertainty about identity/permissions with an owner-private catchall.
Preserve the user's model choices. Report successful live use separately from package installation, database conversion and pending embedding indexing.

Use the existing migration job and worker rather than generating a second conversion script or repeatedly re-extracting old journals. Preserve failed evidence and stop retrying an unchanged failure.