agentleFS
vekzz-devvekzz-dev/opencode-skills/skills/create-readme/SKILL.md

create-readme

Skill4 starsChanged 41 days agoMITView on GitHub

Create comprehensive, well-structured README.md files adapted to the project type. Trigger: When user asks to create README, generate documentation, or initialize project docs.

  • Installs packages

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use readme-i18n, design-md and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • klauswgSkill

    readme-i18n

    Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.

    Also in 4 projects that use this

  • klauswgSkill

    design-md

    Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files

    Also in 4 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 5 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 5 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 4 projects that use this

  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the appropriate reference based on project type:

    line 44
  2. Distinctive:

    Be concise: - Don't write lengthy prose, use structure

    line 63
  3. Distinctive:

    Working code: - All examples must work, no pseudocode

    line 64
  4. Very specific:

    GFM + Admonitions: - Use GitHub Flavored Markdown and > [!NOTE], > [!WARNING], etc.

    line 65
  5. Distinctive:

    Minimal emojis: - Use sparingly for visual hierarchy

    line 66
  6. Distinctive:

    Table of Contents: - If > 50 lines

    line 132
  7. Distinctive:

    Should I trust it?

    line 250
  8. Distinctive:

    Show working code first: - Don't explain before showing

    line 252

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to Use

  • Creating a new README.md file
  • User asks to "create README" or "generate documentation"
  • Initializing project documentation
  • Need help structuring project docs

Instructions

Step 1: Analyze the Project

First, explore the project to understand:

  1. Technology Stack: Detect package manager and language
    • package.json → Node.js/npm library or app
    • pom.xml / build.gradle → Java/Maven/Gradle
    • requirements.txt / setup.py / pyproject.toml → Python
    • go.mod → Go
    • Cargo.toml → Rust
    • composer.json → PHP
  2. Framework: Detect specific frameworks
    • spring-boot in pom.xml → Spring Boot
    • react, vue, angular in package.json → Frontend framework
    • fastapi, django, flask in requirements.txt → Python web
    • express in package.json → Express.js
    • next, nuxt, astro in package.json → Meta-frameworks
  3. Project Purpose: Quick Start, library, CLI tool, web app, etc.

Step 2: Select Template

Use the appropriate reference based on project type:

Project TypeReference
npm/pip/maven libraryreferences/sections/library.md
CLI toolreferences/sections/cli-tool.md
Web applicationreferences/sections/webapp.md
Python projectreferences/sections/python.md
Java projectreferences/sections/java.md
Go projectreferences/sections/go.md
Rust projectreferences/sections/rust.md
Ruby / Rails projectreferences/sections/ruby.md
.NET / C# projectreferences/sections/dotnet.md
Docker projectreferences/sections/docker.md

Step 3: Generate README

Follow these rules:

  1. Be concise - Don't write lengthy prose, use structure
  2. Working code - All examples must work, no pseudocode
  3. GFM + Admonitions - Use GitHub Flavored Markdown and > [!NOTE], > [!WARNING], etc.
  4. Minimal emojis - Use sparingly for visual hierarchy
  5. Table of Contents - For READMEs longer than ~50 lines
  6. No redundant sections - Skip LICENSE, CONTRIBUTING, CHANGELOG (separate files)

Step 4: Add Badges

Include relevant badges from references/badges.md:

  • Package version
  • Build/CI status
  • License
  • Language stats
  • Downloads

Step 5: Include Examples

Reference references/examples/ for working examples:

  • library_example.md - npm/pip libraries
  • cli_example.md - CLI tools
  • webapp_example.md - Web applications

Commands

# Detect project type
ls -la | grep -E "package.json|pom.xml|build.gradle|requirements.txt|go.mod|Cargo.toml"

# Check package.json for Node.js project
cat package.json | grep -E '"name"|"version"|"description"|"main"|"bin"'

# Check pom.xml for Java project
cat pom.xml | grep -E '<artifactId>|<version>|<description>'

# Check go.mod for Go project
cat go.mod | head -5

# Check Cargo.toml for Rust project
cat Cargo.toml | grep -E '\[package\]|name|version|description'

README Structure

Required Sections

# <project-name>

One-line description of what the project does.

## Installation

Quick installation command

## Usage

Minimal working example

## License

One line

Optional Sections (include as needed)

  • Badges - At top, below title
  • Table of Contents - If > 50 lines
  • Features - Key capabilities
  • Requirements - Prerequisites
  • Configuration - Setup options
  • API Reference - For libraries
  • Contributing - Short reference (link to CONTRIBUTING.md)
  • Acknowledgments - Third-party credits

Examples Template

Library

# my-lib

A brief description of what this library does.

[![npm version][npm-badge]][npm-url]

## Installation

```bash
npm install my-lib

Usage

import { myFunction } from 'my-lib';

const result = myFunction('input');
console.log(result);

API

FunctionDescriptionReturns
myFunction(input)Does somethingstring

License

MIT - see LICENSE


### CLI Tool

```markdown
# my-cli

A brief description of what this CLI tool does.

[![npm version][npm-badge]][npm-url]

## Installation

```bash
npm install -g my-cli

Usage

my-cli --help
my-cli command --option value

Commands

CommandDescription
my-cli initInitialize project
my-cli buildBuild the project

License

MIT - see LICENSE


### Web Application

```markdown
# my-app

A brief description of this web application.

[![Build status][build-badge]][build-url]

## Features

- Feature 1
- Feature 2
- Feature 3

## Quick Start

```bash
npm install
npm run dev

Open http://localhost:3000

Deployment

Deployment instructions...

License

MIT - see LICENSE


## Key Principles

1. **Answer the 4 questions in 60 seconds:**
   - What does this do?
   - How do I install it?
   - How do I use it?
   - Should I trust it?

2. **Show working code first** - Don't explain before showing

3. **Use tables** - For API, options, commands

4. **Keep it updated** - Outdated READMEs lose trust

5. **Be helpful** - Think like a new user, not the maintainer

## Resources

- [Project Types Detection](references/project-types.md)
- [Section Templates](references/sections/)
- [Examples](references/examples/)
- [Badges](references/badges.md)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.