Skip to content
cccskills
FreePublished on GitHub

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

The English summary is being prepared. Showing the original description.

agno-agi/context
Works withSlackGmail

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prep For

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.

Procedure

  1. Identify the subject. Pin down who/what from the request ("my 3pm with Sarah Lee from Acme" → person Sarah Lee, org Acme). If it's genuinely ambiguous and a wrong guess would waste the brief, ask one clarifying question instead of guessing.
  2. Sweep what we already know — internal first. Run an entity sweep:
    • 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.
  3. Anchor to the meeting. Surface the specific upcoming meeting/reminder with the subject if there is one — the brief should serve that interaction. When the 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.
  4. Widen to the web only for people/orgs we don't know. If the internal sweep turns up little or nothing on an external person or company (no contact on file, just a name), call 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.

Format

A short brief — only the sections that have content:

  • Who — one line on the subject (role, company), tagged (on file) or (from web) so the owner knows the source.
  • Our history — relationship, past touchpoints, what's open with them (from crm / knowledge / slack).
  • This meeting — the anchoring meeting and the open items to raise.
  • Background — public context, only when pulled from the web; mark it external / unverified.

Edge cases

  • Total blank (nothing internal, nothing useful on the web): say so plainly and ask what context to add — don't fabricate a profile.
  • Attribute every line to its source (crm, knowledge, slack, or web). Keep on-file facts and web background visibly separate; never blend an unverified web claim into our known record.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

daily-rundown

Free

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

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

eval-and-improve

Free

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.

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

extend-agent

Free

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.

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

improve-agent

Free

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.

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

knowledge-review

Free

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

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

process-today

Free

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

The English summary is being prepared. Showing the original description.

agno-agi/context13Updated Jul 10, 2026

See all skills by agno-agi

Report a problem with this skill