agentleFS
the-abraham-brandthe-abraham-brand/my-business-brain/skills/analyze/SKILL.md

analyze

Skill0 starsChanged 51 days agoMITView on GitHub

My Business Brain analysis. Runs consulting-grade business analysis on the user's own data: frames the decision, builds hypotheses and a MECE issue tree, computes with code, finds the 80/20, and delivers an answer-first recommendation with impact, owner, timing and risk. Covers health checks, revenue bridges, customer concentration, unit economics, retention, pricing, cost and break-even, cash, funnel, root cause, opportunity sizing, scenarios and competitive position. Use when the user runs /my-business-brain:analyze, or asks how the business is doing, why a number changed, what to do about something, or for a strategic recommendation.

74 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, revise 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.
  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • stormlightlabsSkill

    revise

    Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.

    Also in 3 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 6 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 projects that use this

  • H-mmerSkill

    submit

    Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

Files
SKILL.md

/my-business-brain:analyze

Analyse the business like a top-tier strategy consultant, from the business's own data.

  1. Load the my-business-brain skill from this plugin (via the Skill tool). If it cannot be loaded, read ../my-business-brain/SKILL.md and ../my-business-brain/references/analytics-playbook.md directly.
  2. Frame the decision in one sentence. With a vague request, run the Business Health Check.
  3. State hypotheses and the issue tree; pick the modules from the analysis library.
  4. Gather data from the brain first (search with scripts/brain_search.py), then the user's files; ask for anything missing in one batch. Vet any external benchmark. For outside research, use what the research toolkit lists (scripts/toolkit.py <brain> show: a research skill, Agent Reach, connectors) and install nothing. Customer and market chatter from social sources is sentiment: report it as such (scripts/signals.py), never as a finding's evidence.
  5. Compute with code, reconcile totals, and find the 80/20.
  6. Deliver answer first: conclusion, 2–4 findings with action titles, exhibits, recommendations (impact, effort, owner, timing, risk), assumptions and gaps, next steps. Offer it as a document and, when the data will be reused, a spreadsheet.
  7. For a recommendation that changes pricing, spend, headcount or a contract, have the brain-checker agent re-derive the key numbers and conclusion without seeing yours (references/orchestration.md); show the user any disagreement.
  8. Save to analytics/<date>-<topic>.md, store new metrics and decisions as entries, and log follow-up dates.

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.