Model or dataset
slavingia/skills avatar
slavingia/skills

slavingia/skills: ten slash commands that arrive as one bundle

Based on The Minimalist Entrepreneur by Sahil Lavingia

11,178 stars1,126 forksUnknownLicense varies

At a glance

What is it?
Sahil Lavingia's The Minimalist Entrepreneur has been repackaged as a Claude Code plugin exposing ten slash commands, installed either from a marketplace entry or from a local clone dropped into the plugins directory. The repository is three entries deep, carries no LICENSE, and has no release to pin.
Who is it for?
Install this if you want the book's ten-step business workflow available as slash commands inside Claude Code, and treat the book rather than the repository as the actual specification. Do not expect versioning, updates or reuse terms: there are no releases, the last commit was 2026-04-14, and no LICENSE is present.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Activity is slowing. The repository last received commits 7 months ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • slavingia/skills11,178 ★ · +707
Star history
Repository2026-09-222026-11-15
slavingia/skills10.5k11.2k

707 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

All ten skills register at once and there is no subset install

The installation is two lines typed into Claude Code:

code
/plugin marketplace add slavingia/skills
/plugin install minimalist-entrepreneur

After that, Claude Code fetches the repository and registers all 10 skills automatically. The unit of installation is the plugin, not the command. Nobody is offered a list of ten checkboxes, and the README documents no way to install a single skill, so if all you want is a pricing prompt you still take the whole set.

What lands is a fixed command surface: /find-community, /validate-idea, /mvp, /processize, /first-customers, /pricing, /marketing-plan, /grow-sustainably, /company-values and /minimalist-review. The consequence is that your command namespace now holds ten generic names you did not choose individually, and the README gives no removal procedure for the ones you will not use.

The repository has no LICENSE and no release to pin

The top level of the repository contains three things: a .claude-plugin directory, README.md and a skills directory. There is no LICENSE file, no changelog, no test directory, and no package manifest beyond the .claude-plugin directory, and the project records no language at all. The GitHub Releases page is empty, so there is no tag, no version number and no dated artifact to point at.

Two consequences follow. First, reuse is undefined: without a license file there are no stated terms telling you what you may fork, redistribute or build on, and the absence is easy to miss because the README says nothing about it either. Second, nothing is pinnable. The README pins no version; the default branch is main, and there is no tagged earlier version to return to if a command changes shape.

Two install paths, and only one of them looks after itself

The marketplace route asks Claude Code to fetch the repository, which leaves the updating question to the tool. The alternative route makes you own the directory yourself:

bash
git clone https://github.com/slavingia/skills.git ~/.claude/plugins/skills

and then points Claude Code at the local copy rather than at GitHub:

code
/plugin marketplace add ~/.claude/plugins/skills
/plugin install minimalist-entrepreneur

That path is useful when you want to read or edit the skill files, and it moves the maintenance burden onto the clone. The README documents no upgrade command for it, so refreshing a local install means dealing with the git checkout yourself, and a directory you have edited is a directory where a pull can conflict. Pick the clone path when you intend to change the skills, not when you just want the commands.

The last commit is 2026-04-14 and no changelog explains it

The most recent push to the repository is dated 2026-04-14. Between that commit and the ten commands described in the README there is no record of what changed, because no changelog file exists in the tree, and the README itself contains no version history and no dated notes.

This matters more for a plugin than for an ordinary library. A library user pins a version and reads release notes. A plugin user re-runs the same install command and gets whatever is current, so the only question that matters is whether the behaviour moved, and this repository offers no way to answer it after the fact. If a command starts producing different output, there is no earlier copy of the skill files to compare against unless you made one yourself before installing.

MVP and Processize split one idea into two commands

The skill table gives these two near-identical triggers. MVP is for when you are ready to build your first product and struggling with scope. Processize is for when you have a product idea and want to deliver value by hand before writing code. The journey list overlaps them further, numbering Build as ship a manual process then productize it, and numbering Processize as turn your product idea into a manual process you can deliver today.

So the same state, an idea you could deliver manually, is described by both commands, and the README gives no rule for which one to reach for. The cost of that ambiguity is concrete: running the wrong one gets you advice aimed at a stage you have not reached, and the README describes nothing that would notice the mismatch or tell you that you skipped a step. Read both descriptions before you pick.

Ten commands cover the book's path and nothing beside it

The command list follows the book's progression one to one: Community, Validate, Build, Processize, Sell, Price, Market, Grow, Culture, Review. Each stage has a matching slash command with a stated trigger, from finding your people through applying minimalist principles to every decision.

That coverage is also the boundary. Everything outside the ten-stage path has no command: no command addresses incorporation, contracts, tax, hiring paperwork, or raising money, and none of them is scoped to a particular industry. Two of them also collide at the same moment, since Grow Sustainably covers decisions about spending, hiring or scaling while Company Values covers defining culture and preparing to hire.

There is no code, no runtime, and nothing that can be tested

This repository contains no program. The tree is a plugin manifest directory, a README and a skills directory, which is also why the project records no primary language. There is no build step, no dependency to resolve, no lockfile, and no test directory, so there is nothing for a continuous integration run to execute and nothing for you to pin versions against.

The practical effect is that the output is whatever the model writes in a conversation, and nothing in the repository records it. The README documents no session state to carry a pricing decision into a later gut-check. That also means the plugin cannot fail loudly: a wrong answer arrives as prose rather than as an error you can catch in a log.

Generic command names are the interface you inherit

The commands are short and domain-neutral: /pricing, /mvp, /first-customers, /marketing-plan. Once the plugin is installed those names live in your Claude Code session alongside anything else you have added, and the README says nothing about namespacing or collision behaviour with other plugins.

The plugin identifier, minimalist-entrepreneur, is what /plugin install expects and what the local clone path registers. If another marketplace entry ever ships a /pricing of its own, the resolution is outside what this repository documents.

Editorial conclusion

Install this if you want the book's ten-step business workflow available as slash commands inside Claude Code, and treat the book rather than the repository as the actual specification. Do not expect versioning, updates or reuse terms: there are no releases, the last commit was 2026-04-14, and no LICENSE is present. Before building on it, confirm you are happy for all ten commands to land at once.

Frequently asked questions

how to install skills in claude code

For this repository, two commands inside Claude Code do it: /plugin marketplace add slavingia/skills, then /plugin install minimalist-entrepreneur. Claude Code fetches the repository and registers all 10 skills automatically, so there is no step where individual skills are selected.

how to install skills from github to claude

The marketplace route points Claude Code at the GitHub repository slavingia/skills and installs the plugin named minimalist-entrepreneur. The alternative clones the repository to disk with git clone https://github.com/slavingia/skills.git ~/.claude/plugins/skills and then adds that local directory as the marketplace instead.

how to use skills in claude code

Each skill is invoked as its own slash command after installation, for example /validate-idea when testing whether a business idea is worth pursuing, /pricing when setting prices or considering a change, and /minimalist-review for gut-checking any business decision.

how to use skills in claude

These skills are published as a Claude Code plugin rather than as a library, so they are added with the plugin marketplace commands and then run as slash commands. The set covers finding a community, validating an idea, building an MVP, processizing, finding first customers, pricing, a marketing plan, sustainable growth, company values, and a minimalist review.

Official sources

  1. Issues
  2. Project website
  3. README
  4. slavingia/skills on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/slavingia-skills.svg)](https://hysenlabs.com/projects/slavingia-skills)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/slavingia-skills.svg)](https://hysenlabs.com/projects/slavingia-skills)

Was this useful?