readme
README Writer
Write clear, concise, well-targeted READMEs for open-source projects. The goal is a README that helps a stranger understand what the project is, try it in under 2 minutes, and know where to go next — nothing more.
Philosophy
A good open-source README is short enough to read and long enough to be useful. Avoid walls of text, badge spam, and sections that repeat what the code already says. Every section must earn its place by answering a question a newcomer actually has.
The three questions every README must answer fast:
- What is this? — one or two sentences.
- How do I use it? — install + minimal working example.
- Where do I go from here? — links to docs, issues, contributing guide.
More from nathan13888/nice-skills
init-repo
Scaffolds a new project repository for agentic development from a problem description, or sets up ops tooling (git, precommits, gitignore, licensing, CI) for an existing project. Guides the user through naming, runtime, package manager, devops, licensing, and project structure. Use when the user says "init project", "new project", "start a project", "scaffold repo", "create repo", or describes a problem they want to build a solution for.
23doc-n-fix
Processes PR review feedback into a prioritized checklist, documents it to a
7wtf
Quick situational awareness for the current git branch. Summarizes what a
6send-it
Push feature branch and create a GitHub PR with structured title and
6explore
Strategic discovery of a project's capabilities from a solutions architect
6check
Verifies the agent's current work against a specific question by analyzing
6