agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/investor-update/SKILL.md

investor-update

Skill1 starsChanged 25 days agoMITView on GitHub

Drafts a concise investor update when shareholders need regular, honest reporting on performance, progress and asks.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use monthly or quarterly for existing investors, after a significant event, or in the months before a new funding round.

    line 9
  2. Distinctive:

    Keep the update short enough to read in under three minutes.

    line 24
  3. Distinctive:

    Every ask is specific enough to act on

    line 32

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Investor Update

When to use it

Use monthly or quarterly for existing investors, after a significant event, or in the months before a new funding round.

What Claude needs

  • client-context.md for business background
  • Key metrics for the period, with prior period and target
  • Cash balance, monthly burn and runway
  • Wins, setbacks and decisions taken
  • Specific help wanted from investors

Method

  1. Open with a three-line summary: overall status, the headline number and the main ask.
  2. Report the same core metrics every time, with change from last period and against plan.
  3. State cash, monthly burn and runway in months.
  4. Cover two or three wins and the most important problem, with what is being done about it.
  5. Make specific, actionable asks such as introductions, hires or expertise.
  6. Keep the update short enough to read in under three minutes.

Output format

Provide an investor update with summary, metrics table, cash and runway, highlights, challenges, asks and next-period priorities.

Quality checks

  • Bad news is reported as plainly as good news
  • Metrics use the same definitions as previous updates
  • Every ask is specific enough to act on

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.