본문으로 건너뛰기
cccskills
무료GitHub에 공개

remember

Review an agent’s saved memory alongside project and personal instructions. Receive proposed destinations for useful entries and a cleanup report covering duplicates, outdated facts, conflicts, and unclear items, with approval required before changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.

설치 방법 보기

이럴 때 유용합니다

  • Turning saved memory into shared project instructions
  • Separating personal instructions from project conventions
  • Finding duplicate or outdated memory
  • Reviewing conflicts across memory files

포함된 파일(2)

  • SKILL.md3.3 KB
  • .skill_id24 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Memory Review

Goal

Review the user's memory landscape and produce a clear report of proposed changes, grouped by action type. Do not apply changes until the user approves them.

Steps

1. Gather all memory layers

Read OPENSPACE.md and OPENSPACE.local.md from the project root if they exist. Review auto-memory from the memory section and MEMORY.md; use memory_read for topic files when needed. Note team memory only as unavailable unless this deployment explicitly has a team memory backend.

Success criteria: you have the contents of all available memory layers and can compare them.

2. Classify each auto-memory entry

For each substantive auto-memory entry, determine the best destination:

DestinationWhat belongs thereExamples
OPENSPACE.mdProject conventions and instructions for OpenSpace that all contributors should followuse uv not raw pip; API routes use kebab-case; test command is pytest; prefer functional style
OPENSPACE.local.mdPersonal instructions specific to this user or machine, not applicable to other contributorsconcise responses; explain tradeoffs; do not auto-commit; run tests before committing
Auto-memory topicDurable cross-session user, feedback, project, or reference memory that does not belong in static project instructionsuser role, durable feedback, external reference pointers, uncertain but useful context
Stay putWorking notes, temporary context, or entries that do not clearly fit elsewheresession-specific observations, uncertain patterns

Important distinctions:

  • OPENSPACE.md and OPENSPACE.local.md contain instructions for the agent, not arbitrary external-tool preferences.
  • Workflow practices such as PR conventions, merge strategy, and branch naming can be personal or team-wide; ask the user when unclear.
  • When unsure, ask rather than guess.

Success criteria: each entry has a proposed destination or is flagged as ambiguous.

3. Identify cleanup opportunities

Scan across all layers for:

  • Duplicates: auto-memory entries already captured in OPENSPACE.md or OPENSPACE.local.md.
  • Outdated entries: static instructions contradicted by newer auto-memory.
  • Conflicts: contradictions between any two layers; propose a resolution and note which evidence is newer.
  • Overloaded index lines: MEMORY.md entries that contain content that belongs in a topic file.

Success criteria: all cross-layer issues are identified.

4. Present the report

Output a structured report grouped by action type:

  1. Promotions: entries to move, with destination and rationale.
  2. Cleanup: duplicates, outdated entries, conflicts, and index cleanup.
  3. Ambiguous: entries where you need the user's input on destination.
  4. No action needed: brief note on entries that should stay put.

If auto-memory is empty, say so and offer to review OPENSPACE.md for cleanup.

Rules

  • Present all proposals before making changes.
  • Do not modify files without explicit user approval.
  • Do not create new files unless the approved target does not exist yet.
  • Ask about ambiguous entries; do not guess.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

HKUDS의 스킬 모두 보기

이 스킬의 문제 신고