Founders bring up things they need, an intro, help hiring, a quick gut check, on calls and in update submissions, and those asks are easy to lose between check-ins.
This skill pulls the last 30 days of both, Visible update responses and Granola call notes, builds a running list grouped by company, and DMs it to you in Slack.
Setup
1. Download this Skill file: company-ask-tracker.skill
2. Upload it in Claude under Settings > Capabilities > Skills.
3. You'll need an "Asks" custom property in Visible first. This a custom property that will need to be created and can be added to your update request template, something like "Asks" or "How can we help?" If it doesn't exist yet, create it, or the skill has nothing to pull from on the Visible side, it can still surface asks from Granola calls without it.
4. On first run, Claude confirms the name of that field if it can't find an obvious match. That's remembered so future runs skip the lookup.
Running it
Tell Claude something like:
"Check company asks"
"Run the ask tracker"
Type the / command and find the skill
Default window is the last 30 days across your whole active portfolio. Name a specific company and it'll scope to just that one.
What it actually does
The instructions below are packaged into the skill file. You don't need them to use it, but here's what's happening under the hood.
Pulling from two places. From Visible, it reads submitted update responses and looks specifically at the Asks field, not the whole response, so it doesn't misread an unrelated comment as a request. From Granola, it matches the last 30 days of calls to portfolio companies and asks specifically what the founder requested, intros, hiring help, advice, that kind of thing, not routine check-in chatter. If a call's summary is ambiguous about whether something was a real ask, it checks the transcript before including it.
Handling multi-company calls. If a single call plausibly touches more than one portfolio company, a syndicate call, say, Claude asks you once which company it should count toward, rather than guessing or dropping it.
Not repeating itself. Since this runs on a rolling 30-day window, the same still-open ask would otherwise show up in every digest until it aged out. Instead, once an ask has been surfaced, it's suppressed for good, it won't come back in a future digest even if it's still unresolved. If you want to check what's already been flagged for a company, just ask, "what's already been surfaced for Acme" pulls up the history directly in chat without re-running the scan or posting to Slack.
Grouping and sorting. Everything lands grouped by company, oldest ask first within each one, categorized as Intro, Hiring, Advice, or Other.
What lands in Slack
Company names as bold headers, each ask underneath with its category, a plain-language description, where it came from (a Visible submission or a specific call, with date), and how long it's been open. Reminders are marked so they read differently from something genuinely new. If nothing turned up, you still get a short message confirming the check ran clean, not silence.
What lands in Visible
Every ask that actually gets included in a digest also gets logged as a note on that company, tagged "Company Asks" so it's easy to filter from real call notes in the same feed. That log is what powers the no-repeat behavior above, and it also means the ask's history is visible to anyone looking at that company's record, not just whoever got the Slack message.
Worth knowing
Reading from Visible and Granola is read-only. Posting to Slack and logging the note are the two actions that write anything, they're the point of the skill, so Claude does both without asking per run.
By default, this goes to you as a DM. If you ask for it to go to a channel or another person instead, Claude will confirm that destination first, since that's sending on your behalf to someone else.
Claude won't invent an ask that isn't clearly supported by the source data. If something's ambiguous, it checks before including it rather than guessing.