agentleFS
victordelrosalvictordelrosal/chairman/.claude/skills/pulse/SKILL.md

pulse

Skill0 starsChanged 8 months agoMITView on GitHub

Financial weekly pulse. Revenue vs forecast, expenses vs budget, cash position, outstanding invoices, variances. Friday morning routine. Octopus colors: Yellow (data pull) + Purple (synthesis).

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ant, artistic and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bergsideSkill

    ant

    Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

    Also in 3 projects that use this

  • bergsideSkill

    artistic

    High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

    Also in 3 projects that use this

  • +10 more from bergside

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read departments/finance/knowledge/ for financial data, budgets, forecasts

    line 14
  2. Distinctive:

    Only report data that exists in the knowledge base.

    line 61
  3. Distinctive:

    If no finance department exists, work with whatever financial data is available.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 18 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

/pulse: Financial Weekly Pulse

Octopus Colors: Yellow (Researcher) + Purple (Manager)

Process

  1. Read departments/finance/knowledge/ for financial data, budgets, forecasts
  2. Pull current data (Yellow):
    • Revenue: actual vs. forecast for the period
    • Expenses: actual vs. budget by category
    • Cash position: current balance, upcoming obligations
    • Outstanding: invoices sent but unpaid, aging
    • Key ratios: margins by product/service line
  3. Synthesize (Purple):
    • Are we on track? Above or below plan?
    • Any variance > 10% from forecast? Flag with explanation.
    • Cash flow concerns in the next 30 days?
    • One-line summary: healthy/caution/concern
  4. Present to Chairman

Output Format

# Financial Pulse: [Date]
**Overall:** [Healthy / Caution / Concern]

## Revenue
- This period: [amount] ([+/-]% vs forecast)
- Month-to-date: [amount] ([+/-]% vs plan)

## Expenses
- This period: [amount] ([+/-]% vs budget)
- Flagged: [any category > 10% over budget]

## Cash Position
- Current: [amount]
- Next 30 days: [net inflow/outflow expected]
- Concern: [any cash flow risk, or "None"]

## Outstanding
- Invoices unpaid: [count] totaling [amount]
- Aging > 30 days: [count] totaling [amount]

## Variance Alerts
- [Item]: [amount] [over/under], reason: [explanation]

## Chairman Action
[ ] No action needed
[ ] Follow up on: ___
[ ] Adjust forecast

Rules

  • Only report data that exists in the knowledge base. Do not invent numbers.
  • If no finance department exists, work with whatever financial data is available.
  • Flag concerns proactively. Better to flag a non-issue than miss a real one.
  • Save to .chairman/reports/pulse-YYYY-MM-DD.md

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.