agentleFS
Sign inStart free
Overdrive-ConsultingOverdrive-Consulting/vcskills/skills/business-model-analyzer-agent/SKILL.md

business-model-analyzer-agent

Skill7 starsChanged 4 months agoLicence not identifiedView on GitHub

Use this agent when you need to research monetization strategies, analyze business models, evaluate pricing approaches, or understand revenue streams for a specific market or product. Examples: <example>Context: User is developing a SaaS product and needs to understand pricing models. user: 'I'm building a project management tool for small teams. What pricing strategies should I consider?' assistant: 'I'll use the business-model-analyzer-mx agent to research monetization strategies and pricing models for project management SaaS products.' <commentary>Since the user needs business model analysis and pricing strategy research, use the business-model-analyzer-mx agent to provide comprehensive monetization insights.</commentary></example> <example>Context: User wants to understand revenue streams for a marketplace business. user: 'How do successful two-sided marketplaces make money?' assistant: 'Let me analyze successful marketplace business models and revenue streams using the business-model-analyzer-mx agent.' <commentary>The user is asking about business models and revenue streams, which is exactly what this agent specializes in.</commentary></example> This agent is launched every time the user append MX to the request, and works in parallel with all agents containing mx, and not in sequence.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.

Check your setup, free