Rename a page safely: update the file, fix every inbound wikilink, add the old name as an alias, and log it. Use this skill whenever a page needs a different canonical title, the user says "rename X to Y", asks to fix an inconsistent title, or after a lint run flags naming problems. Do NOT use for merging two pages, for moving a page between folders without a name change, or for renaming files outside the wiki.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
An agent renaming a file directly is the single most common source of broken links in an agent-maintained vault. Obsidian fixes links when you rename inside the app; writing the file directly does not.
A rename is four operations, not one. All four, or none.
title in frontmatter.aliases. This keeps external references, the
user's memory, and any link you miss working.index.md.Renamed: [[old]] -> [[new]]
Inbound links updated: <n> across <n> pages
Alias added: <old>
Remaining references: <none | list>
Do not rename to fix a style preference on a page with many inbound links. The cost is real and the benefit is cosmetic.
If the correct name is genuinely ambiguous, ask rather than picking. A second rename is more disruptive than the first.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).
日本語の概要は準備中です。原文の説明を表示しています。
Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).
日本語の概要は準備中です。原文の説明を表示しています。
Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).
日本語の概要は準備中です。原文の説明を表示しています。
Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.
日本語の概要は準備中です。原文の説明を表示しています。