Agent Skills
› simplexai-labs/linger
› holistic-context
holistic-context
GitHub用于整合多源信息以回答复杂问题,涵盖个人状态、计划及关系等。通过分层搜索记忆与实时数据,校验事实准确性并处理冲突,最终生成报告或计划。
Trigger Scenarios
需要跨工具和个人信息的综合查询
验证动态变化的事实如日程或联系信息
构建基于约束的计划或推荐
Install
npx skills add simplexai-labs/linger --skill holistic-context -g -y
SKILL.md
Frontmatter
{
"name": "holistic-context",
"description": "Gather and combine what several of the Human's sources and the web say when one answer needs them together, such as the state of a subject across tools, people and relationships, scheduling, open commitments, or a plan built on the Human's constraints. Not for a question one command answers."
}
Holistic context
- Start from what is already here: memory.md if your instructions carry it, this conversation, and the Agent Memory index. If they answer it, answer.
- List the facts still missing. Tag each one:
- the Human's own, or outside;
- stable, or changing (needs a check now). Own and stable: knowledge search. Own and changing: calendar, Tracking Items, Routines, Slack, live mail, Drive, Notion, GitHub. Outside and stable: lev8, web background. Outside and changing: the web, checked now. references/sources.md says what each source answers.
- Search in rounds. First run the knowledge searches the personal knowledge policy calls for. When they return, decide whether the answer still needs anything else: a fact memory does not have, or a changing fact that memory gives only as a lead. If nothing, answer; do not query other sources just to be thorough. Otherwise query only the live or outside sources that settle those facts. Sources that are plainly needed from the start and independent of memory may run alongside the first round. A record of a past event does not by itself prove a changing present status. Where sources disagree, weigh recency and authority; do not assume that newer always means correct. If evidence remains insufficient, state the material uncertainty.
- Anything memory gives that can change after it was recorded (a date or plan, where someone works or lives, their contact details, an amount, a deadline, whether something is done) is a lead. Before the answer states it as current, check the latest source that owns it (the calendar, recent mail or Slack, Tracking Items) once. If they disagree, use the latest and say what changed. Give a live-source query a window that covers the whole period asked about, and check date versus date-time boundaries so the end day is included.
- When the answer chains facts held by different sources (a person found in memory, their current role or contact in recent mail, their time in the calendar), check each link in the source that owns it and for the right person and time. A link supported only by topical overlap is not established. Stop once the links are supported; if one cannot be established, say which.
- Check the answer against what you are delivering:
- a report: the answer first, key facts with where they came from, what was not checked;
- a choice or recommendation: the candidates, the criteria, and the evidence for each;
- a plan or schedule: the constraint list, the plan, and any conflict with the calendar or Tracking Items;
- a draft or action: the draft and the facts it uses; nothing is sent, booked or bought without approval. Carry the constraint list into any later step or handed-off Task.
Version History
- d8ebc34 Current 2026-11-14 00:25


