Produce the owner's week-ahead plan — scheduled meetings and due-or-overdue reminders for the next 7 days, grouped by day, read from the CRM and enriched from the real calendar, Slack, and knowledge-base briefs when connected. Use for "what's my week", "plan the week ahead", "what's coming up".
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Runtime skill — a playbook the deployed @context agent runs for its owner, invoked in natural language. Not a coding-agent workflow; those live in
.agents/skills/.
Assemble a clear plan for the next 7 days from the structured crm
store, enriched from the connected sources. This is a read-only retrieval
workflow: it pulls, merges, and formats — it never writes anything.
now → now + 7 days.query_crm (one retrieval —
ask it for both):
starts_at falls between now and now + 7 days.status = 'pending' and due_at ≤ now + 7 days.
Include anything already overdue (due_at < now, still pending) — a
plan that hides what's late isn't useful.calendar source is connected, pull the real calendar too —
query_calendar for events in the same 7-day window — and merge with the
CRM meetings (dedupe by title + start time; the calendar wins on times).slack source is connected,
query_slack for recent threads that touch this week's meetings,
attendees, or active projects — surface commitments and deadlines that
never made it into the CRM as plan items, flagged (from slack). When a
meeting or reminder ties to a project with a brief in the knowledge base,
pull its status from query_knowledge so the plan reflects where things
actually stand. Enrichment is bounded: it adds context to the week's
items, it doesn't grow the window.3 meetings, 5 reminders, 1 overdue.crm, calendar, slack, and
knowledge-base briefs feed this plan; don't pull from web / workspace unless
the owner explicitly asks.crm meetings + reminders, plus
calendar / slack / knowledge where they contributed), and report empty
results honestly rather than guessing.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
The owner's morning brief — inbound updates awaiting acknowledgment (via the rundown tool), today's meetings and due-or-overdue reminders from the CRM and the real calendar, the emails worth seeing from Gmail, and the Slack threads that need their eyes — each source folded in when connected and stitched into one short digest. Use for "daily rundown", "what's on today", "morning brief", "catch me up".
中文简介正在准备中。当前显示原文说明。
Run this repo's eval suite (python -m evals), diagnose every failing case, and fix in scope (agent instructions, or the eval case when its assertion was wrong) until all cases pass. Use whenever the user wants to run the evals, check for regressions, or fix a red eval suite ("run the evals", "why is a case failing", "make the eval suite green"). Targets the committed cases in evals/cases.py; for ad-hoc probing of one agent's live behavior use improve-agent instead.
中文简介正在准备中。当前显示原文说明。
User-driven loop to change the context agent (or any agent in this repo) — add a source/tool/MCP server, add a capability (knowledge base, memory, sub-agent, scheduled task), refine its instructions, or fix a specific known bug, verifying each change against the live container. Use whenever the user names a concrete change ("add a Google Drive source", "make the daily rundown include the calendar", "the agent keeps doing Y, fix it"). For autonomous hardening with no specific change in mind use improve-agent.
中文简介正在准备中。当前显示原文说明。
Autonomously harden the context agent (or any agent in this repo) — derive probes from the agent's own instructions, run them against the live container, judge the responses and tool calls, and edit the agent until it reliably does what it says it does. Use when the user wants to test, harden, stress-test, or improve an agent's reliability WITHOUT naming a specific change ("make sure context is solid", "harden this agent", "probe it for failure modes"). For a user-directed change use extend-agent; to run the committed eval suite use eval-and-improve.
中文简介正在准备中。当前显示原文说明。
Sweep the knowledge base for what needs attention — stubs with no real content, specs whose status is stale, decisions that were made but never written down, and pages missing from the index — and return a short "what needs attention" list. Read-only, so it reports rather than fixing anything itself. Use for "what in my knowledge base needs attention", "review my knowledge base", "what's stale or unfiled", "knowledge base health check", "tidy up my knowledge".
中文简介正在准备中。当前显示原文说明。
Brief the owner before a meeting or conversation with a person, company, or project — sweep what we already know (crm + knowledge, plus slack, calendar, and gmail when connected), anchor to any upcoming meeting with them, and for people or orgs we don't know, widen to a web search for public background. Use for "prep me for my meeting with X", "brief me on X before the call", "what do we know about X".
中文简介正在准备中。当前显示原文说明。