SkillCheatSheet
run-dev-instance
An AI agent skill from amir20/dozzle, scored 55 out of 100 by code.
Code score by group
It loses the most points in Procedure (15), the group that checks whether the steps are numbered, read the context first and say what to do when something fails.
What the author says it does
Use when Dozzle needs to be running in a browser to test a change by hand (clicking the UI, screenshots, driving it with Chrome or Playwright). Starts an instance on a free port derived from this worktree, so several worktrees can each have one at the same time, and never disturbs an instance someone else started.
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- amir20/dozzle
- Folder
- .claude/skills/run-dev-instance
- License
- MIT
- GitHub stars
- 14,916
- SKILL.md lines
- 78
- Other files
- 0
Add run-dev-instance to your agent
npx skills add amir20/dozzle --skill run-dev-instanceThe command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
More skills from amir20/dozzle
-
update-int-snapshots
Use when Playwright visual snapshots in e2e/visual.spec.ts-snapshots/ need to be regenerated after a UI change (logo, theme, layout, anything that affects rendered pixels) and the…
71B -
verify
Prove a change works before opening a PR for Dozzle. Runs the checks CI runs for what the diff touches, shows the new behaviour actually working, and has a fresh-context subagent…
67C -
add-app-icon
Use when adding a bundled app icon to Dozzle for a container image that shows no logo, or when an image resolves to the wrong icon
60C
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.