YouSpot

What this user should deal with right now, computed from their sent mail, their calendar and their LinkedIn export: people who went quiet after real correspondence, people they are meeting this week, who they write to most, invitations nobody answered, and the shape of their network. Each item carries the reason and where the numbers came from. Call this for 'what needs my attention', 'who am I forgetting', 'who should I follow up with', 'what should I do today' and anything else that asks who to deal with without naming one person. Then show an attention_list card and never write the items out yourself. `readiness` says whether the mailbox has finished being read: when it is 'pending' or 'partial', say so rather than presenting a short list as the whole picture.

The Linear issues completed in one Monday-to-Sunday week (Eastern time), last week by default, that have not been announced in a changelog and do not carry the no-changelog label. Each comes with its identifier, title, url, labels, project, completion time and the start of its description. Pass week_start as YYYY-MM-DD (a Monday) to pick another week.

Save the week's changelog draft for an editor to review and publish. title is the post's headline; body_markdown is the post (sections New, Improved, Fixed; one sentence per item in the customer's words; keep each item's Linear identifier in an HTML comment like <!-- YOU-142 --> so editors can trace it; no em or en dashes; never a provider or model name); sources is the list of identifiers the post covers. One draft per week; the tool refuses a second. Returns the admin link where the draft is edited and published.

Research one specific company in depth — the same engine behind the CompanyResearch.ai app. Takes a website domain (preferred) or a company name, and returns a profile: description, industry, size, revenue, funding history, founders, competitors, recent news, and answers to the user's saved research questions. Use this when the user asks to research, analyze, or get a briefing on a specific company. For discovering many companies by criteria, use find_companies instead; for a quick identity card, company_card markup is enough. The first run on an uncached company can take a while — that is normal.

Recent news and hiring movement for companies the user already knows, several at once, split into what is new since the last check and what was already reported. Use for watching companies over time: what has happened at my clients, is anyone hiring, anything I should know before I reach out. When running on a schedule, report only the new items and stay silent when there are none. For one company in depth use research_company; for the open web use web_search.

Look up the public registration (WHOIS) record for a website domain: who registered it, which registrar holds it, when it was created and last updated, when it expires, its nameservers, and its registry status codes. Use this ONLY when the user explicitly asks about the domain/WHOIS/DNS itself: 'who owns stripe.com?', 'when does our domain expire?', 'how old is this domain?', 'is this domain registered?'. Never call it for general questions about a company — this is public registrar data about a domain on the internet; it is not the user's own account data, and it says nothing about the company behind the domain. Registrant details are often masked by a privacy service, in which case the registrant fields name the proxy rather than the real owner; say so instead of presenting the proxy as

Estimate what a domain name is worth (the /domainvalue appraisal): an estimated market value in dollars with the signals behind it — comparable sales, marketplace listings, an appraisal model, SEO data. Use when the user asks what a domain is worth, whether one is a good buy, or to compare domain values. A fresh appraisal can take up to a minute; repeat lookups within 48 hours are cached and instant. Include the report_url in your reply so the user can open the full report.

Send an email to the signed-in user at their own account email address. Use this when the user asks to be sent something — 'email me this', 'send myself a reminder', 'send me that summary as an email'. The recipient is fixed to their own address and cannot be changed. To write an email to anyone else, use create_gmail_draft instead — it drafts in their Gmail without sending. Compose a short, specific subject line yourself if the user didn't give one. The body is Markdown, rendered into the YouSpot email template before sending: '## ' subheadings, '- ' bullets, **bold**, > quotes and tables all work. Do not write HTML, and do not add a sign-off or a footer — the template supplies both. LINKS. Never write an absolute youspot.com URL; you do not reliably know them, and a wrong one reaches t

Read the content of a file the user uploaded — use this when the answer may live in a document in their Second Brain: schedules, itineraries, contracts, exports, scans. PDFs and images are returned as the actual document, so tables and scanned pages read correctly. Find the file first with search_graph_objects (type 'file') and pass its object_id, or pass part of the filename as name.

Download a file from a public http(s) URL and store it in the user's Second Brain as a file object — use when the user shares a direct link to a PDF, image, spreadsheet, or other file and asks to save, download, or keep it. The saved file shows up with their uploads and can be read afterwards with read_file. Not for web pages (that is read_web_page with save=true) and not for files behind a sign-in. Files over 50MB are refused.

Import every contact or company from a file the user uploaded — a CSV or spreadsheet export, a .vcf of contacts, or a zip. Use this whenever they want more than a couple of records created from a file: it reads the whole file at once, so never read a contact list with read_file and create the records one at a time. Find the file first with search_graph_objects (type 'file') and pass its object_id, or pass part of the filename as name. Pass a description of what the file holds when the user gave one — it is what tells the column mapper that 'Ref' is a phone number.

Search the user's connected Gmail mailboxes and return matching messages, newest first — from, to, subject, date, and a short snippet of the body. `query` uses Gmail search syntax: 'in:sent to:jane@acme.com' for messages the user sent to someone, 'from:jane@acme.com' for messages they received, plus operators like subject:, newer_than:7d, and has:attachment. So 'show me the last 5 messages I sent to jane@acme.com' is query 'in:sent to:jane@acme.com' with max_results 5. Each result carries a `starred` flag — a message the user starred matters to them, so weight it accordingly; 'is:starred' finds starred mail directly. For 'how many' questions, use total_matches_estimate in the result — it is Gmail's estimate of ALL matches, beyond the messages returned. If it reports no Gmail account connec