AB investor-update
Drafts a founder's periodic update to investors and LPs for review, then hands it back to the founder to send. This skill is the drafting engine, it does NOT connect to any source or send anything. It pulls the period's raw material from whatever is reachable in the session (a Slack MCP on the founder's updates, metrics, and team channels; a Gmail/Google Workspace MCP for customer-win, hire, partnership, and fundraise threads; an analytics or billing MCP like Stripe or Amplitude for numbers) or from material the founder pastes, and produces a complete email draft in the Elad Gil long or short format. Built for founders sending monthly or quarterly updates to investors and LPs. Use whenever the founder says "draft my investor update", "investor update", "write my monthly update to investors", "LP update", "write my investor email", "monthly investor email", "update to our investors", or "/investor-update".
Drafts a founder's periodic update to investors and LPs for review, then hands it back to the founder to send.
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2311 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 918: 120–800 characters recommended
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.