원클릭으로 Manus에서 모든 스킬 실행

blessing-standard

스타0

포크0

업데이트2026년 6월 14일 21:45

Scaffold the five Blessing Protocol files (soul.md, agent.md, skills.md, palace.md, bless.md) into any repository and fill them from what the repo already is. Use when the user says "adopt bless here", "make this repo blessable", "scaffold the blessing files", "set up the mind palace standard". Reads the repo to draft soul.md first, then derives the rest; never overwrites a filled file without asking.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

frankxai

frankxai/mind-palace-agent-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

blessing-standard

The onboarding step. Make any repo blessable by dropping in the five files — and fill them with the repo's actual essence, not empty boilerplate.

When to use this

When a builder wants to adopt the Blessing Protocol in a new repo. Produces the five lowercase files seeded from what the repo already contains, so the first weekly blessing has real ground to stand on.

Instructions

Read the repo. README, existing CLAUDE.md / AGENTS.md / SOUL.md, package metadata, directory shape. Understand what this repo is before writing its soul.
Draft soul.md first. Everything inherits from it. Name 4–6 invariants (what must not drift) and the drift test. Pull the essence from the repo's own voice — do not impose a generic identity.
Derive the other four from soul.md + the repo:
- agent.md — the operating contract (voice, behavioural rules, refusals, repo-specific hard stops).
- skills.md — index the repo's existing skills/commands; always list weekly-blessing + palace-build.
- palace.md — the room mapping (surface vocabulary, ordering) suited to this repo's domain.
- bless.md — cadence + what's blessable here + an empty ledger table ready for the first blessing.
Reconcile, don't duplicate. If the repo already has SIP-tier files (SOUL.md / AGENTS.md / SKILL.md), make the lowercase file a short public projection that points at the substrate file rather than restating it (Blessing Protocol §6). Note the relationship in the file.
Create the ledger scaffold. palace/blessings.jsonl (empty) and a weekly/ directory. Do not write a weekly entry — that is the first blessing's job, run intentionally.
Respect existing files. Never overwrite a filled soul.md/etc. without showing a diff and asking. Scaffolding is additive.

Output

Report the files created/updated and the one next action: "Run the weekly blessing when you're ready to close this week."

Refusals

Never write generic, soulless boilerplate — if you cannot find the repo's essence, ask the builder rather than inventing one.
Never overwrite filled standard files silently.

References

Templates: github.com/frankxai/bless/templates/.
The contract + reconciliation: Blessing Protocol §2 and §6.

Built on SIP · mind-palace-agent-skills · bless v0.1

이 저장소의 다른 Skills

같은 저장소

agent-memory-palace

frankxai/mind-palace-agent-skills

Give an AI agent persistent, navigable memory across sessions using a memory-palace structure. Use when building agent memory, when the user says "remember this across sessions", "give the agent long-term memory", "persistent context", "knowledge graph for my agent", or for coding agents, Claude cowork, and ChatGPT projects that must retain state. Reads and writes palace.json as a durable spatial knowledge store the agent reloads each session.

2026-07-050

imagination-gym

frankxai/mind-palace-agent-skills

Train mental-imagery vividness and scene construction so memory-palace images are stronger. Use when the user says "my mental pictures are weak/blurry", "I can't visualize", "train my imagination", "help me see images more clearly", or struggles to encode loci. Drills based on imagery research — multisensory detail, manipulation, and scene construction — to make encoding work better.

2026-07-050

loci-encoder

frankxai/mind-palace-agent-skills

Turn each target into a vivid, memorable image and place it at a station. Use when the user says "encode these items", "make images for my palace", "help me remember names and faces", "turn this list into pictures", or after memory-palace-architect lays out the rooms. Applies bizarreness, multisensory, exaggeration, motion, and dual-coding; fills the loci[] of palace.json.

2026-07-050

memory-palace-architect

frankxai/mind-palace-agent-skills

Design a memory palace — choose a real or imagined locus, lay a fixed non-crossing route, and space the stations. Use when the user says "design a memory palace", "pick a place to memorize in", "lay out my palace", "map a route for N items", or needs a structure before encoding. Writes the rooms/stations skeleton of palace.json for loci-encoder to fill.

2026-07-050

number-memory

frankxai/mind-palace-agent-skills

Memorize digits, dates, phone numbers, and playing cards by converting numbers into images. Use when the user says "memorize this number", "remember these dates", "how do I memorize a deck of cards", "PAO system", "Major System", or "Dominic System". Supplies the encoding for numeric targets, then hands the resulting images to loci-encoder for placement.

2026-07-050

palace-foundations

frankxai/mind-palace-agent-skills

Teach the method of loci and route the user to the right memory-palace skill. Use when someone says "teach me the memory palace", "how does the method of loci work", "help me memorize X", "I want to remember a list/speech/deck", or is new to spatial memory. The start-here skill that explains the four-level model then dispatches to architect, encoder, number-memory, walk, or spaced-recall.

2026-07-050

name

blessing-standard

description

blessing-standard

The onboarding step. Make any repo blessable by dropping in the five files — and fill them with the repo's actual essence, not empty boilerplate.

When to use this

Instructions

Read the repo. README, existing CLAUDE.md / AGENTS.md / SOUL.md, package metadata, directory shape. Understand what this repo is before writing its soul.
Draft soul.md first. Everything inherits from it. Name 4–6 invariants (what must not drift) and the drift test. Pull the essence from the repo's own voice — do not impose a generic identity.
Derive the other four from soul.md + the repo:
- agent.md — the operating contract (voice, behavioural rules, refusals, repo-specific hard stops).
- skills.md — index the repo's existing skills/commands; always list weekly-blessing + palace-build.
- palace.md — the room mapping (surface vocabulary, ordering) suited to this repo's domain.
- bless.md — cadence + what's blessable here + an empty ledger table ready for the first blessing.
Reconcile, don't duplicate. If the repo already has SIP-tier files (SOUL.md / AGENTS.md / SKILL.md), make the lowercase file a short public projection that points at the substrate file rather than restating it (Blessing Protocol §6). Note the relationship in the file.
Create the ledger scaffold. palace/blessings.jsonl (empty) and a weekly/ directory. Do not write a weekly entry — that is the first blessing's job, run intentionally.
Respect existing files. Never overwrite a filled soul.md/etc. without showing a diff and asking. Scaffolding is additive.

Output

Report the files created/updated and the one next action: "Run the weekly blessing when you're ready to close this week."

Refusals

Never write generic, soulless boilerplate — if you cannot find the repo's essence, ask the builder rather than inventing one.
Never overwrite filled standard files silently.

References

Templates: github.com/frankxai/bless/templates/.
The contract + reconciliation: Blessing Protocol §2 and §6.

Built on SIP · mind-palace-agent-skills · bless v0.1