recallloom

Name: recallloom
Author: Frappucc1no

152installs4forks

How to install recallloom?

frappucc1no/recall-loom/recallloom

$npx -y skills add Frappucc1no/recall-loom --skill recallloom

Installs into the current project.

Summary

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, pro

Files · 1

View on GitHub

SKILL.md

1	# RecallLoom
2
3	RecallLoom is a portable context harness for session-based agents.
4
5	It provides a lightweight file model for project continuity across sessions without requiring heavy infrastructure.
6
7	The goal is not to remember everything. The goal is to keep the right project state durable, readable, and recoverable across sessions.
8
9	## Package Scope
10
11	This file is the agent-facing entrypoint for the installable `recallloom/` skill package.
12
13	Install and trigger this package through your host agent's normal skill discovery flow.
14	RecallLoom itself does not require a custom host-specific launcher inside the package.
15	The package may still ship optional native wrapper templates for supported hosts.
16
17	This installable package is intentionally kept lean.
18	Human-facing repository landing pages and marketing docs may exist upstream, but they are not bundled into the installed skill directory.
19
20	In the source repository, `README.md` and `README.en.md` are concise public
21	front doors, `README.zh-CN.md` is the compatibility entry, `INDEX.md` is the
22	full map, and `USAGE.md` is the operator guide.
23	Those files describe the same helper contract as this installed package
24	entrypoint rather than defining a second logic set.
25
26	For package inventory, protocol details, and helper-script behavior, rely on the files that ship inside the package itself:
27
28	- `managed-assets.json`
29	- `package-metadata.json`
30	- `references/file-contracts.md`
31	- `references/operation-playbooks.md`
32	- `references/package-support-policy.md`
33	- `references/recording-workflow.md`
34	- `references/protocol.md`
35
36	## Package Facts
37
38	<!-- RecallLoom metadata sync start: package-metadata -->
39	- package version: `0.4.7`
40	- protocol version: `1.0`
41	- supported protocol versions:
42	- `1.0`
43	<!-- RecallLoom metadata sync end: package-metadata -->
44
45	## Runtime Assumptions
46
47	<!-- RecallLoom metadata sync start: runtime-assumptions -->
48	- Python 3.10 or newer
49	- supported workspace languages:
50	- `en`
51	- `zh-CN`
52	- supported bridge targets:
53	- `AGENTS.md`
54	- `CLAUDE.md`
55	- `GEMINI.md`
56	- `.github/copilot-instructions.md`
57	<!-- RecallLoom metadata sync end: runtime-assumptions -->
58
59	## Package Support Gate
60
61	RecallLoom package support is separate from project sidecar protocol compatibility.
62
63	- Helpers MUST perform the package-support check and MUST NOT write support state into project `.recallloom/`.
64	- If support is `readonly_only`, mutating helpers MUST block while diagnostic and read-only helpers MAY continue.
65	- If support is `diagnostic_only`, only diagnostic helpers SHOULD continue.
66	- If support is `unknown_offline`, diagnostic and read-only actions MAY continue, but mutating actions MUST block until support can be verified.
67	- Blocked actions MUST return the shared failure contract with `blocked_reason: package_support_blocked` and a `package_support` object. See `references/package-support-policy.md`.
68
69	## Public Surface And Required Checks
70
71	- Public package and release surfaces MUST stay limited to files a user needs to install, understand, and operate the package.
72	- 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.
73	- Public CI and required checks MAY validate repository contents and metadata.
74	- Required-check wording MUST NOT present repository checks as proof of a user's local workspace state, host behavior, or sidecar trust status.
75
76	## Non-Invasive Defaults And UX Gates
77
78	- 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.
79	- Native command wrappers are opt-in convenience entrypoints over the same dispatcher, not a required enforcement layer.
80	- Ordinary docs/source/planning edits outside the managed sidecar stay silent allow or low-friction unless they affect provenance-sensitive RecallLoom state.
81	- Managed sidecar or provenance-impacting actions surface one of `allow`, `warn`, `ask`, or `block` in helper readiness output when provenance state is relevant.
82	- `warn` is for low-risk structural-only or readable legacy states and should stay brief; repeated same-session low-risk warnings should be cooldown-friendly.
83	- `ask` is for legacy review / repair import or reviewed imported baseline actions and requires explicit operator confirmation before higher-risk writes.
84	- `block` is non-waivable for forged markers, detected receipt/store inconsistency, direct `state.json` / `config.json` edits, privacy violat

People who liked this also viewed

6 picks

Type

recallloom

152installs4forks

View on GitHub

How to install recallloom?

frappucc1no/recall-loom/recallloom

$npx -y skills add Frappucc1no/recall-loom --skill recallloom

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# RecallLoom
2
3	RecallLoom is a portable context harness for session-based agents.
4
5	It provides a lightweight file model for project continuity across sessions without requiring heavy infrastructure.
6
7	The goal is not to remember everything. The goal is to keep the right project state durable, readable, and recoverable across sessions.
8
9	## Package Scope
10
11	This file is the agent-facing entrypoint for the installable `recallloom/` skill package.
12
13	Install and trigger this package through your host agent's normal skill discovery flow.
14	RecallLoom itself does not require a custom host-specific launcher inside the package.
15	The package may still ship optional native wrapper templates for supported hosts.
16
17	This installable package is intentionally kept lean.
18	Human-facing repository landing pages and marketing docs may exist upstream, but they are not bundled into the installed skill directory.
19
20	In the source repository, `README.md` and `README.en.md` are concise public
21	front doors, `README.zh-CN.md` is the compatibility entry, `INDEX.md` is the
22	full map, and `USAGE.md` is the operator guide.
23	Those files describe the same helper contract as this installed package
24	entrypoint rather than defining a second logic set.
25
26	For package inventory, protocol details, and helper-script behavior, rely on the files that ship inside the package itself:
27
28	- `managed-assets.json`
29	- `package-metadata.json`
30	- `references/file-contracts.md`
31	- `references/operation-playbooks.md`
32	- `references/package-support-policy.md`
33	- `references/recording-workflow.md`
34	- `references/protocol.md`
35
36	## Package Facts
37
38	<!-- RecallLoom metadata sync start: package-metadata -->
39	- package version: `0.4.7`
40	- protocol version: `1.0`
41	- supported protocol versions:
42	- `1.0`
43	<!-- RecallLoom metadata sync end: package-metadata -->
44
45	## Runtime Assumptions
46
47	<!-- RecallLoom metadata sync start: runtime-assumptions -->
48	- Python 3.10 or newer
49	- supported workspace languages:
50	- `en`
51	- `zh-CN`
52	- supported bridge targets:
53	- `AGENTS.md`
54	- `CLAUDE.md`
55	- `GEMINI.md`
56	- `.github/copilot-instructions.md`
57	<!-- RecallLoom metadata sync end: runtime-assumptions -->
58
59	## Package Support Gate
60
61	RecallLoom package support is separate from project sidecar protocol compatibility.
62
63	- Helpers MUST perform the package-support check and MUST NOT write support state into project `.recallloom/`.
64	- If support is `readonly_only`, mutating helpers MUST block while diagnostic and read-only helpers MAY continue.
65	- If support is `diagnostic_only`, only diagnostic helpers SHOULD continue.
66	- If support is `unknown_offline`, diagnostic and read-only actions MAY continue, but mutating actions MUST block until support can be verified.
67	- Blocked actions MUST return the shared failure contract with `blocked_reason: package_support_blocked` and a `package_support` object. See `references/package-support-policy.md`.
68
69	## Public Surface And Required Checks
70
71	- Public package and release surfaces MUST stay limited to files a user needs to install, understand, and operate the package.
72	- 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.
73	- Public CI and required checks MAY validate repository contents and metadata.
74	- Required-check wording MUST NOT present repository checks as proof of a user's local workspace state, host behavior, or sidecar trust status.
75
76	## Non-Invasive Defaults And UX Gates
77
78	- 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.
79	- Native command wrappers are opt-in convenience entrypoints over the same dispatcher, not a required enforcement layer.
80	- Ordinary docs/source/planning edits outside the managed sidecar stay silent allow or low-friction unless they affect provenance-sensitive RecallLoom state.
81	- Managed sidecar or provenance-impacting actions surface one of `allow`, `warn`, `ask`, or `block` in helper readiness output when provenance state is relevant.
82	- `warn` is for low-risk structural-only or readable legacy states and should stay brief; repeated same-session low-risk warnings should be cooldown-friendly.
83	- `ask` is for legacy review / repair import or reviewed imported baseline actions and requires explicit operator confirmation before higher-risk writes.
84	- `block` is non-waivable for forged markers, detected receipt/store inconsistency, direct `state.json` / `config.json` edits, privacy violat

People who liked this also viewed

6 picks

Type