본문으로 건너뛰기
cccskills
무료GitHub에 공개

week-plan

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Slack

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Week Plan

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.

Procedure

  1. Anchor on now. Use the current datetime already in your context. The window is now → now + 7 days.
  2. Pull the two time-bearing tables with query_crm (one retrieval — ask it for both):
    • Meetings whose starts_at falls between now and now + 7 days.
    • Reminders with 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.
  3. If the 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).
  4. Enrich from connected sources. When the 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.
  5. Order meetings and reminders by their time column, ascending.

Format

  • Lead with an Overdue section only if past-due pending reminders exist; note how late each one is.
  • Then one heading per day (today through day 7), in date order. Under each day list its meetings (with start time) and any reminders due that day.
  • Skip days with nothing — don't pad the plan with empty dates.
  • Close with a one-line tally, e.g. 3 meetings, 5 reminders, 1 overdue.

Edge cases

  • Nothing in the window: say so in one line ("Nothing scheduled or due in the next 7 days.") — don't invent items or reach to other sources.
  • Don't widen past the playbook. crm, calendar, slack, and knowledge-base briefs feed this plan; don't pull from web / workspace unless the owner explicitly asks.
  • Cite the sources the plan came from (crm meetings + reminders, plus calendar / slack / knowledge where they contributed), and report empty results honestly rather than guessing.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

prep-for

무료

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

agno-agi/context132026년 7월 10일 업데이트

agno-agi의 스킬 모두 보기

이 스킬의 문제 신고