90/100
Grade Aflisk-sh/flisk at f9ba78c (main) · README.md
23 checks pass, 5 fail · 90.1 of 100 points
Scored as CLI tool ·Library ·Full-stack app ·Backend API
Type chosen on this page.
Fix first
- FailCommands in the quickstart0/3
Fix: Cut 1 of the 7: fold setup into one command (a script, a create command, a Makefile target) or move optional steps below.
- line 23: npm install -g @flisk-sh/flisk → mkdir my-shop → cd my-shop → flisk project --yes → flisk resource orders-api --type backend --stack shop --yes → flisk resource shop-web --type frontend --stack shop --yes → flisk up shop
- FailWebsite headline matches the README0/3
Fix: Use one headline: the README H1 says "Flisk: your whole app, running on your computer with one command", the website says "Flisk CLI — start services on your machine". Change one to the other's wording (the website's <title> and og:title, or the H1).
- <title>: "Flisk CLI — start services on your machine"
- <h1>: "Your docker-compose.yml , running locally and updating as you save."
- FailWebsite leads with the README's command0/2
Fix: Lead with one command in both places: the README's quickstart starts with flisk project, the website's first command is flisk import. Put the same first step first on both, or say on each why there are two ways in.
- FailOne tagline everywhere1.5/3
Fix: Use one wording everywhere. The most used is "Flisk: your whole app, running on your computer with one command"; change GitHub About description (the GitHub About box is edited from the gear next to About).
- line 5: A: README.md H1: "Flisk: your whole app, running on your computer with one command"
- package.json:5: A: package.json description: "Flisk: your whole app, running on your computer with one command."
- cli/package.json:5: A: cli/package.json description: "Flisk: your whole app, running on your computer with one command."
- docs/agents/llms-full.txt:3: A: docs/agents/llms-full.txt: "Flisk: your whole app, running on your computer with one command."
- docs/agents/llms.txt:3: A: docs/agents/llms.txt: "Flisk: your whole app, running on your computer with one command."
- B: GitHub About description: "Generate and Run your whole Tech Stack without the setup pain. 💚 AI. 💚https://github.com/flisk-sh/flisk 💚 🫧https://demo.flisk.sh ⚡️https://flisk.sh"
- FailWebsite description matches the README pitch2.6/3
Fix: Say the same thing in both places: use the website description's words in the README's opening paragraph, or change the description to the README's.
- Website description: "Have a docker-compose.yml? flisk import, then flisk up, runs it locally with routes, rebuilds on save and an MCP server for your AI agent. Not a deploy tool."
- Only on the website: docker, yml, import, locally, route, rebuild, mcp, server
- line 5: Only in the README pitch: whole, app, running, computer, command, line, local, development, part, api, website, worker, database, behind, addres
Sections
- PassOverview3.1/3.1
- PassKey features3.1/3.1
- PassPrerequisites3/3
- PassInstallation4.6/4.6
- PassUsage or commands4.6/4.6
- PassConfiguration3/3
- PassExamples3/3
- PassTroubleshooting1.5/1.5
- PassRoadmap1.5/1.5
- PassContributing3/3
- PassLicense4.6/4.6
First screen
- PassTitle near the top4/4
- PassInstall command4/4
- PassPicture of it working4/4
- PassBadges before the first code block4/4
- PassWords before the first code block4/4
Readability
- PassFlesch reading ease10/10
- line 186: 48 words: "adds the Flisk skills (build a stack, recipes for a shop, a SaaS, an AI agent and a blog, doctor, up, resource, status, troubleshoot; sou…"
- line 605: 38 words: "For the next 12 months Flisk plans to keep 1.x stable ( , scaffolding, generated files and stay backward compatible), keep the core free,…"
- line 77: 33 words: "**No Kubernetes; no Docker for small apps.** Docker and Tilt run the stack without a local cluster such as kind or minikube, and services…"
- line 31: "tilt" 24× (infrastructure word; say what it is the first time)
- line 31: "docker" 19× (infrastructure word; say what it is the first time)
- line 20: "compose" 15× (infrastructure word; say what it is the first time)
- line 476: "helm" 6× (infrastructure word; say what it is the first time)
- line 70: "traefik" 5× (infrastructure word; say what it is the first time)
- line 359: "containers" 4× (infrastructure word; say what it is the first time)
- line 77: "kubernetes" 4× (infrastructure word; say what it is the first time)
- line 72: "container" 3× (infrastructure word; say what it is the first time)
- line 77: "cluster" 2× (infrastructure word; say what it is the first time)
- line 558: "yaml" 1× (infrastructure word; say what it is the first time)
Quickstart
- PassQuickstart block2/2
- FailCommands in the quickstart0/3
Fix: Cut 1 of the 7: fold setup into one command (a script, a create command, a Makefile target) or move optional steps below.
- line 23: npm install -g @flisk-sh/flisk → mkdir my-shop → cd my-shop → flisk project --yes → flisk resource orders-api --type backend --stack shop --yes → flisk resource shop-web --type frontend --stack shop --yes → flisk up shop
- PassTranslations give the same commands5/5
Links
- PassRelative links resolve5/5
- Pass#anchors match a heading5/5
Tagline
- FailOne tagline everywhere1.5/3
Fix: Use one wording everywhere. The most used is "Flisk: your whole app, running on your computer with one command"; change GitHub About description (the GitHub About box is edited from the gear next to About).
- line 5: A: README.md H1: "Flisk: your whole app, running on your computer with one command"
- package.json:5: A: package.json description: "Flisk: your whole app, running on your computer with one command."
- cli/package.json:5: A: cli/package.json description: "Flisk: your whole app, running on your computer with one command."
- docs/agents/llms-full.txt:3: A: docs/agents/llms-full.txt: "Flisk: your whole app, running on your computer with one command."
- docs/agents/llms.txt:3: A: docs/agents/llms.txt: "Flisk: your whole app, running on your computer with one command."
- B: GitHub About description: "Generate and Run your whole Tech Stack without the setup pain. 💚 AI. 💚https://github.com/flisk-sh/flisk 💚 🫧https://demo.flisk.sh ⚡️https://flisk.sh"
- PassOne spelling of the name2/2
Website: https://flisk.sh/
- FailWebsite headline matches the README0/3
Fix: Use one headline: the README H1 says "Flisk: your whole app, running on your computer with one command", the website says "Flisk CLI — start services on your machine". Change one to the other's wording (the website's <title> and og:title, or the H1).
- <title>: "Flisk CLI — start services on your machine"
- <h1>: "Your docker-compose.yml , running locally and updating as you save."
- FailWebsite description matches the README pitch2.6/3
Fix: Say the same thing in both places: use the website description's words in the README's opening paragraph, or change the description to the README's.
- Website description: "Have a docker-compose.yml? flisk import, then flisk up, runs it locally with routes, rebuilds on save and an MCP server for your AI agent. Not a deploy tool."
- Only on the website: docker, yml, import, locally, route, rebuild, mcp, server
- line 5: Only in the README pitch: whole, app, running, computer, command, line, local, development, part, api, website, worker, database, behind, addres
- FailWebsite leads with the README's command0/2
Fix: Lead with one command in both places: the README's quickstart starts with flisk project, the website's first command is flisk import. Put the same first step first on both, or say on each why there are two ways in.
- PassWebsite shows the README's install command2/2
Badge, API and MCP
[](https://readme.flisk.si/flisk-sh/flisk) curl 'https://readme.flisk.si/api/score?repo=flisk-sh/flisk' claude mcp add --transport http readme-score https://readme.flisk.si/mcp
