Frappucc1no/recall-loom / skills/recallloom
recallloom
FlaggedUse 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.
profiles/research-writing.md
View on GitHub# Research Writing Profile
Use this profile when the project is driven by:
- literature review
- research drafting
- claim/evidence iteration
- long-form analytical writing
- source-heavy analytical memo writing
## Primary Risks
Research-writing projects drift when:
- claims move faster than evidence verification
- old conclusions remain in active state after contradictory sources arrive
- section progress is remembered loosely rather than explicitly
- source review history gets mixed with current writing goals
- unverified citations or interpretations are treated as settled support
## What to Emphasize
In this profile, emphasize:
- evidence traceability
- claim stability
- explicit verification gaps
- section-level continuity
- source-driven revisions
- unresolved questions that still require verification
## File Emphasis
- `STORAGE_ROOT/context_brief.md`
Keep the research goal, audience, scope, and source-of-truth boundaries clear.
Prefer section keys rather than display headings when reasoning about structure:
- `mission` for the research objective
- `audience_stakeholders` for readers, reviewers, or collaborators
- `scope` for domain, corpus, or question boundaries
- `source_of_truth` for source and evidence boundaries
Display headings may render as localized labels such as `Mission` or `项目使命`.
- `STORAGE_ROOT/rolling_summary.md`
Focus on:
- `current_state` for current thesis direction and section status
- `active_judgments` for the current supported interpretive position
- `risks_open_questions` for unresolved evidence gaps and verification needs
- `next_step` for the next research, reading, or writing move
- `STORAGE_ROOT/daily_logs/`
Record meaningful literature discoveries, key judgment reversals, and milestone drafting progress.
## Common Anti-Pattern
Do not turn literature collection into a running dump in the rolling summary.
Do not promote unverified sources or remembered citations into current truth.
If raw source detail grows, keep the current-state file short and preserve milestone evidence separately.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |