跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

distilly

Build and use evidence-grounded local person profiles with Distilly's exact five-tool workflow. Use when a user asks to research, ingest, distill, update, correct, retrieve, or recall a real or fictional person's profile, voice, boundaries, or evidence.

titanwings · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add titanwings/distilly --skill distilly

技能说明


name: distilly description: Build and use evidence-grounded local person profiles with Distilly's exact five-tool workflow. Use when a user asks to research, ingest, distill, update, correct, retrieve, or recall a real or fictional person's profile, voice, boundaries, or evidence.

Distilly

Keep person memory local, evidence-bound, and reviewable. Use only these model-facing tools:

  • distilly_get
  • distilly_ingest
  • distilly_pending
  • distilly_commit
  • distilly_correct

Do not invent a create, research, flush, capture, or review tool. Do not use shell commands or direct file writes to change Distilly state.

Gate the runtime

The installed host binding completes trusted preflight before it starts the MCP server and binds the verified briefing capacity to the runtime session. That internal result is not model-facing: do not ask the user for it or require a HostPreflight object in the conversation.

Before any source research or distilly_* call, check that all five exact Distilly tools are available in the current session. Their availability is sufficient to begin; the runtime still fails closed if its trusted preflight, capacity binding, or wire handshake is invalid. If the runtime or MCP server is unavailable, any tool is missing, or a call returns a host-capability or handshake failure, report that narrow failure and stop immediately. Do not research, ingest, acquire a lease, simulate tool results, use shell commands as a fallback, or write persona content into global instruction files.

Establish the task

  1. Identify the requested person, space, scope, and whether the user wants retrieval, new research, an update, or a correction.
  2. Call distilly_get with action: resolve before collecting or writing material.
  3. Handle resolution exactly:
    • For resolved, retain the returned subject id.
    • For ambiguous, show the candidates and ask the user to choose. Never guess.
    • For not_found, create the subject only together with the first non-empty material batch through distilly_ingest using subject.kind: create.
  4. For a retrieval-only request, call distilly_get with action: profile, prompt, or status after resolution and stop. Never create an empty subject.

Every tool input includes top-level wireVersion: "3" and a requestId shaped as req_ plus 32 lowercase hexadecimal characters. Use a fresh request id for each logical call. Reuse an id only when retrying the identical request; never reuse it for changed arguments. Do not hand-build variable-length counting sequences. When a safe host-local UUID or 16-byte random-hex facility is available, use it only to generate the suffix, remove UUID hyphens, lowercase it, and verify that the suffix matches ^[0-9a-f]{32}$ before the tool call; this must not read user data or mutate Distilly.

For the required first resolution call, use the exact shape { "wireVersion": "3", "requestId": "req_<32 lowercase hex characters>", "action": "resolve", "subject": { "kind": "query", "query": "<person name or identity query>" } }. query belongs inside subject, never at the top level.

Treat every JSON shape in this Skill as a template: replace each angle-bracket token with a real value before calling a tool. For distilly_get, subject is only { "kind": "query", "query": "<query>" } or { "kind": "id", "subjectId": "subject_<32 lowercase hex characters>" }. For distilly_ingest, it is only { "kind": "create", "input": { ... } } or { "kind": "existing", "subjectId": "subject_<32 lowercase hex characters>" }. distilly_correct instead takes subjectId at the top level. Do not interchange these selectors.

For a profile read by id, use { "wireVersion": "3", "requestId": "req_<32 lowercase hex characters>", "action": "profile", "subject": { "kind": "id", "subjectId": "subject_<32 lowercase hex characters>" } }. Change only action to prompt or status for those reads.

Start from what the user already supplied

When the request already includes pasted text, attached or named local paths, an explicitly selected directory, or public URLs, treat those as the source plan after subject resolution. Do not make the user choose a person type, repeat known metadata, fill an intake form, or choose a connector before using readable sources they already selected. Do not add broader web research unless the user requested it. If the supplied evidence cannot answer the stated objective, explain the gap and ask before expanding the source scope.

  • Read only the selected local files or supported regular files inside the selected directory. Do not follow symlinks or expand into adjacent paths. Skip binaries, credentials, hidden tool state, dependency trees, and unrelated project files; summarize skipped categories instead of silently treating them as evidence. Sort selected files by root-relative path and submit a repeated path only once in the intake.
  • Fetch each supplied public URL with an observable host web capability and preserve the retrieved body and URL as one traceable source. Search-result snippets are discovery hints, not ingestible source bodies. Do not crawl linked pages unless the user requested broader research, and submit a repeated URL only once in the intake.
  • Treat an explicit request to distill pasted or attached private material as authorization for exactly that supplied content. It does not authorize adjacent conversations, accounts, files, contacts, or public identity expansion.
  • Ask a question only when identity is ambiguous, the selected scope is unclear, a source cannot yield traceable text, or private authority is not established. Otherwise proceed directly.

Use observable capabilities safely

The five Distilly tools establish only the Distilly workflow; they do not imply web research, local-file reading, OCR, transcription, private capture, or another optional source capability. Use an optional capability only when the current session actually exposes a sui

阅读完整来源 ↗