recallloom
Use when a task involves continuing a project, restoring project context, maintaining file-based project memory, updating current-state summaries, or recording meaningful progress across sessions. Works best for long-horizon, file-based projects and supports research writing, product document collaboration, software project coordination, and broader cross-functional project continuity.
Frappucc1no · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Frappucc1no/recall-loom --skill recallloom技能说明
name: recallloom description: Use when a task involves continuing a project, restoring project context, maintaining file-based project memory, updating current-state summaries, or recording meaningful progress across sessions. Works best for long-horizon, file-based projects and supports research writing, product document collaboration, software project coordination, and broader cross-functional project continuity.
RecallLoom
RecallLoom is a portable context harness for session-based agents.
It provides a lightweight file model for project continuity across sessions without requiring heavy infrastructure.
The goal is not to remember everything. The goal is to keep the right project state durable, readable, and recoverable across sessions.
Package Scope
This file is the agent-facing entrypoint for the installable recallloom/ skill package.
Install and trigger this package through your host agent's normal skill discovery flow. RecallLoom itself does not require a custom host-specific launcher inside the package. The package may still ship optional native wrapper templates for supported hosts.
This installable package is intentionally kept lean. Human-facing repository landing pages and marketing docs may exist upstream, but they are not bundled into the installed skill directory.
In the source repository, README.md and README.en.md are concise public
front doors, README.zh-CN.md is the compatibility entry, INDEX.md is the
full map, and USAGE.md is the operator guide.
Those files describe the same helper contract as this installed package
entrypoint rather than defining a second logic set.
For package inventory, protocol details, and helper-script behavior, rely on the files that ship inside the package itself:
managed-assets.jsonpackage-metadata.jsonreferences/file-contracts.mdreferences/operation-playbooks.mdreferences/package-support-policy.mdreferences/recording-workflow.mdreferences/protocol.md
Package Facts
- package version:
0.5.0 - protocol version:
1.0 - supported protocol versions:
1.0
Runtime Assumptions
- Python 3.10 or newer
- supported workspace languages:
enzh-CN
- supported bridge targets:
AGENTS.mdCLAUDE.mdGEMINI.md.github/copilot-instructions.md
Package Support Gate
RecallLoom package support is separate from project sidecar protocol compatibility.
- Helpers MUST perform the package-support check and MUST NOT write support state into project
.recallloom/. - If support is
readonly_only, mutating helpers MUST block while diagnostic and read-only helpers MAY continue. - If support is
diagnostic_only, only diagnostic helpers SHOULD continue. - If support is
unknown_offlinebecause no local support cache exists, local diagnostic, read-only, and mutating actions MAY continue; network access is not a prerequisite for local RecallLoom use. - A structurally invalid or uninterpretable local support cache permits diagnostic actions only while offline. A structurally valid stale cache is re-evaluated against the current package version and keeps its
supported,upgrade_recommended,readonly_only, ordiagnostic_onlyrestriction. - Invalid-cache diagnostics MUST identify the cache condition with a public-safe reason and direct recovery toward read-only diagnosis, online refresh and atomic cache replacement, or removal of the invalid package-scoped local cache. They MUST NOT present a package upgrade as the cache repair or describe the cache as tampered.
invalid_support_advisoryremains distinct from an invalid local cache: correct or refresh the advisory rather than treating it as cache damage.- Blocked actions MUST return the shared failure contract with
blocked_reason: package_support_blockedand apackage_supportobject. Seereferences/package-support-policy.md.
Public Surface And Required Checks
- Public package and release surfaces MUST stay limited to files a user needs to install, understand, and operate the package.
- Public surfaces MUST NOT include copied project memory, generated runtime output, machine-local data, maintainer-only working files, or material that is not required by the installable package.
- Public CI and required checks MAY validate repository contents and metadata.
- Required-check wording MUST NOT present repository checks as proof of a user's local workspace state, host behavior, or sidecar trust status.
Non-Invasive Defaults And UX Gates
- Core install and daily use MUST NOT require or auto-install hooks, daemons, watchers, MCP/plugin enforcement, host adapters, telemetry/metrics, or remote payload transmission.
- Native command wrappers are opt-in convenience entrypoints over the same dispatcher, not a required enforcement layer.
- Ordinary docs/source/planning edits outside the managed sidecar stay silent allow or low-friction unless they affect provenance-sensitive RecallLoom state.
- Managed sidecar or provenance-impacting actions surface one of
allow,warn,ask, orblockin helper readiness output when provenance state is relevant. warnis for low-risk structural-only or readable legacy states and should stay brief; repeated same-session low-risk warnings should be cooldown-friendly.askis for legacy review / repair import or reviewed imported baseline actions and requires explicit operator confirmation before higher-risk writes.blockis non-waivable for forged markers, detected receipt/store inconsistency, directstate.json/config.jsonedits, privacy violations, and any general, legacy, or unbound state classified asinconsistent_or_tampered_evidence.- D5 is the sole narrow recovery transition: only helper-path target-on