원클릭으로 Manus에서 모든 스킬 실행

시작하기

readme-builder

스타3

포크0

업데이트2026년 2월 26일 08:13

Generates readmes for humans

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

floscr

floscr/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

README Generator

When asked to create a README file, follow these guidelines:

Style

Keep it short and scannable for humans
Use plain, direct language
No marketing speak or hype
No emojis
No badges unless explicitly requested
No claims about test coverage or code quality

Structure

Start with a one-line description of what it does
Include installation instructions if applicable
Show basic usage with a minimal example
List dependencies only if they're not obvious
Skip sections that would be empty or filler

Tone

Write like documentation, not advertising
State facts, not promises
If something is limited or experimental, say so
Assume the reader is technical

이 저장소의 다른 Skills

같은 저장소

bb-server

floscr/dotfiles

Build Babashka HTTP API servers using httpkit, ruuter, and hiccup. Scaffolds server projects with routing, handlers, rendering, WebSocket support, and HTMX integration.

Create changelog

Build CLI tools using Babashka and babashka.cli. Scaffolds new CLIs as standalone bins or multi-command tools following project conventions.

Create docs

Build fullstack apps with Squint + Eucalypt frontend and Babashka + Ruuter backend. Scaffolds projects with reactive UI, JSON API, CORS, dev server, and Vite single-file builds.

2026-02-263

pr-description

floscr/dotfiles

create a pr description

2026-02-263

name	readme-builder
description	Generates readmes for humans

README Generator

When asked to create a README file, follow these guidelines:

Style

Keep it short and scannable for humans
Use plain, direct language
No marketing speak or hype
No emojis
No badges unless explicitly requested
No claims about test coverage or code quality

Structure

Start with a one-line description of what it does
Include installation instructions if applicable
Show basic usage with a minimal example
List dependencies only if they're not obvious
Skip sections that would be empty or filler

Tone

Write like documentation, not advertising
State facts, not promises
If something is limited or experimental, say so
Assume the reader is technical