graft-init â Configure graft behavior in CLAUDE.md
openbooklet.com/s/graft-init-configure-graft-behavior-in-claudemdopenbooklet.com/s/graft-init-configure-graft-behavior-in-claudemd@1.0.0GET /api/v1/skills/graft-init-configure-graft-behavior-in-claudemdThis skill writes a short, opinionated instruction block into a CLAUDE.md so future sessions automatically use the graft skills (`recall`, `memoryze`, `learn`, `memory-audit`) according to the user's preferences. The block is fenced with HTML markers so re-running the skill cleanly replaces it.
You have a long-term memory graph that persists across conversations and across agents. Treat it as your **first stop** for anything non-trivial: another past-you (or another agent on the team) may have already solved it, and the answer lives there.
`/learn` is a **plan-first** ingestion pipeline. It is NOT "scan and dump everything you see". It is: scout, distill, propose a plan, get the user's approval, then execute. This separation matters because uncontrolled ingestion creates duplicates, garbage summaries, and a keyword vocabulary that fra
The graph rots like any knowledge base: people save sloppy summaries, save the same fact with three different keywords, save things that never get reused. This skill produces a single readable report and a punch-list of concrete maintenance actions for the user to approve.
Distill the current conversation (or a specified excerpt) into N high-quality graft nodes and save them. Triggered by `/memoryze`, "save this to memory", "ricorda questo", "memorize this", or whenever the user explicitly wants the agent to commit knowledge to the persistent graph. The user can hint at granularity ("split into 3 atomic nodes", "one comprehensive node"), focus ("save the WHY, not the diff"), and target profile. Auto-classifies keywords. Prefer this over a raw `graft insert` whenever you're saving more than a one-liner.
`graft` exposes three search modes and they have different sweet spots:
Auto-indexed from AEndrix03/Graft
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.