Draft from the vault: outline from concept pages, keep citations to the user's own sources, and surface where their material disagrees. Use this skill when the user wants to write an article, post, essay or newsletter based on what they have collected, or asks what they could write about a topic. Do NOT use for research reports, for writing with no grounding in the vault, or for editing text the user wrote themselves unless asked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
The research is already done, cited and connected. What is left is the argument, and that is the part the user should keep.
Assemble structure and evidence. Do not hand back finished prose as if it were theirs.
Angle: <what this piece argues that the sources do not individually>
Outline:
1. <point> - [[page]], [[page]]
Weak points: <claims with thin support>
Missing: <what would strengthen it>
If every point in the outline comes from one page, this is a summary of that page, not an article. Say so.
Never introduce a specific number or quote that has no source page behind it. That is the failure mode of writing with a model, and in a cited piece it is the one that costs the most.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.