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".
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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/.
Pull together a tight pre-meeting brief on a subject — a person, company, or project the owner is about to engage. Read-only: gather and synthesize, never file.
query_crm — contacts, notes, projects, and any reminders/meetings tagged
to the subject (name, company, tags, meeting attendees). This is our
relationship + history.query_knowledge — knowledge-base prose about the subject (runbooks, summaries,
"what I know about X").query_slack (when connected) — recent threads mentioning the subject;
the latest exchanges are often the freshest context in the brief.calendar source is connected, check query_calendar for the real
event (time, attendees); when gmail is connected and there's an email
thread with the subject, pull the latest exchange with query_gmail — the
most recent thing they said is often the most useful line in the brief.query_web for public background — role,
current company, recent news. Skip the web when we already have a solid
internal picture, and for internal/private topics. Don't pad a brief with
generic results, and keep the web query to public identity terms (name +
company), not the owner's private notes about them.A short brief — only the sections that have content:
(on file) or
(from web) so the owner knows the source.crm / knowledge / slack).crm, knowledge, slack, or web).
Keep on-file facts and web background visibly separate; never blend an
unverified web claim into our known record.まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Process the day into filed context — sweep today's activity (the inbound queue, CRM meetings and reminders, plus calendar, slack, and gmail when connected), extract what's worth keeping, and file it into the CRM and knowledge base. Use for "process today", "log today", "file today", "end-of-day wrap".
日本語の概要は準備中です。原文の説明を表示しています。