Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

memory-promote

Estrelas3

Forks0

Atualizado26 de maio de 2026 às 21:00

Move a specific memory entry to a durable destination. Validates against routing rules in memory/README.md.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

danielcopper

danielcopper/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	memory-promote
description	Move a specific memory entry to a durable destination. Validates against routing rules in memory/README.md.
argument-hint	<from-description> <to-destination> (e.g. 'sqlcmd quoting trick' tools/sql-server)

/memory-promote - Single-item promotion

You are running the /memory-promote command. The user wants to move one specific memory entry to one specific destination. Granular alternative to /memory-dream.

Read the routing rules at ~/.claude/memory/README.md first if not already in context.

Argument shape

Expected form: /memory-promote <from-description> <to-destination>

<from-description>: a phrase identifying the source entry. Could be a quote, a topic name, or a date+timestamp (e.g. "today's 14:30 sql-server bullet"). If unclear, ask for clarification.
<to-destination>: one of:
- <rule-name> → ~/.claude/memory/<rule-name>.md (top-level rule file; one rule per file, kebab-case)
- tools/<X> → ~/.claude/memory/tools/<X>.md
- domain/<X> → ~/.claude/memory/domain/<X>.md
- repo/<rule-name>, repo/tools/<X>, repo/domain/<X> → expands to <git-root>/.claude/memory/.... Requires cwd inside a git repo.
- A literal path (advanced) → use as-is.

If $ARGUMENTS is empty, ask for both source and destination.

Steps

Identify the source entry: search dailies first (~/.claude/memory/daily/*.md), then global durables, then repo durables. If multiple matches, list them and ask which.
Identify the target destination from the second argument. If the destination is repo/... and cwd isn't in a git repo, abort with a clear message.
Validate against the routing rules:
- "Would this fact still be true in a different project tomorrow?" → if yes but destination is repo, warn.
- "Would teammates benefit?" → if no but destination is repo, warn.
- If the entry contains anything sensitive (secrets, in-flight personal observations, "I'm confused"), warn before promoting to a committed location.
Show the proposed move:
- Source content (verbatim).
- Destination path (and whether the file is being created or appended to).
- Final shape of the destination file (or the relevant section).
Wait for approval.
Apply:
- Write to destination (create file if missing, append/merge if existing).
- Remove the source entry:
  - If source is a daily: remove the whole ## HH:MM — topic section from the daily file. Content now lives in the destination; keeping it in the daily is duplication.
  - If source is a durable topic file: remove the entry from the source file.
- Update MEMORY.md index in the destination store: bump the last-updated date for the destination file. If a new file was created, also add a new descriptive index entry.

Constraints

Do not modify ~/.claude/projects/<mapped-cwd>/memory/.
Single-item operation — if the user wants to move many things, suggest /memory-dream instead.

Mais deste repositório

mesmo repositório

diagnose

danielcopper/dotfiles

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

2026-06-163

grill-with-docs

danielcopper/dotfiles

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

2026-06-163

write-a-skill

danielcopper/dotfiles

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

2026-06-163

to-issues

danielcopper/dotfiles

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices, and publish them to the repo's GitHub Project board. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

2026-05-283

to-prd

danielcopper/dotfiles

Turn the current conversation context into a PRD and publish it to the repo's GitHub Project board. Use when user wants to create a PRD from the current context.

2026-05-283

handoff

danielcopper/dotfiles

Compact the current conversation into a handoff document for another agent to pick up.

2026-05-263

/memory-promote - Single-item promotion

You are running the /memory-promote command. The user wants to move one specific memory entry to one specific destination. Granular alternative to /memory-dream.

Read the routing rules at ~/.claude/memory/README.md first if not already in context.

Argument shape

Expected form: /memory-promote <from-description> <to-destination>

<from-description>: a phrase identifying the source entry. Could be a quote, a topic name, or a date+timestamp (e.g. "today's 14:30 sql-server bullet"). If unclear, ask for clarification.

<to-destination>: one of:

<rule-name> → ~/.claude/memory/<rule-name>.md (top-level rule file; one rule per file, kebab-case)
tools/<X> → ~/.claude/memory/tools/<X>.md
domain/<X> → ~/.claude/memory/domain/<X>.md
repo/<rule-name>, repo/tools/<X>, repo/domain/<X> → expands to <git-root>/.claude/memory/.... Requires cwd inside a git repo.
A literal path (advanced) → use as-is.

If $ARGUMENTS is empty, ask for both source and destination.

Steps

Identify the source entry: search dailies first (~/.claude/memory/daily/*.md), then global durables, then repo durables. If multiple matches, list them and ask which.

Identify the target destination from the second argument. If the destination is repo/... and cwd isn't in a git repo, abort with a clear message.

Validate against the routing rules:

"Would this fact still be true in a different project tomorrow?" → if yes but destination is repo, warn.
"Would teammates benefit?" → if no but destination is repo, warn.
If the entry contains anything sensitive (secrets, in-flight personal observations, "I'm confused"), warn before promoting to a committed location.

Show the proposed move:

Source content (verbatim).
Destination path (and whether the file is being created or appended to).
Final shape of the destination file (or the relevant section).

Wait for approval.

Apply:

Write to destination (create file if missing, append/merge if existing).
Remove the source entry:
- If source is a daily: remove the whole ## HH:MM — topic section from the daily file. Content now lives in the destination; keeping it in the daily is duplication.
- If source is a durable topic file: remove the entry from the source file.
Update MEMORY.md index in the destination store: bump the last-updated date for the destination file. If a new file was created, also add a new descriptive index entry.

Constraints

Do not modify ~/.claude/projects/<mapped-cwd>/memory/.

Single-item operation — if the user wants to move many things, suggest /memory-dream instead.