agentleFS
OneByJorahOneByJorah/offivo/.agents/skills/readme-writer/SKILL.md

readme-writer

Skill24 starsChanged 28 days agoMITView on GitHub

Write or rewrite a repository README to a high standard with hero banner, badges, real screenshot, quick start, config table, and architecture diagram. Use for any README task.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-audit.

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.
  • CloudflareSkill

    security-audit

    Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run every command in the README on a clean clone.

    line 27
  2. Distinctive:

    Check every link and image path.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 17 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

readme-writer

Structure (in this order)

  1. Hero banner (docs/assets/banner.svg) and one-line pitch
  2. Badges: CI, release, license, GHCR image, stars
  3. A real screenshot directly under the pitch
  4. Why this exists: 3 to 4 sentences
  5. Features: specific, each with its outcome
  6. Quick start: copy-paste block that works in under two minutes
  7. Configuration: table of environment variables with defaults
  8. Architecture: a Mermaid diagram of the real components
  9. Roadmap, Contributing, Security, License

Voice

Calm, direct, specific. First person plural or neutral. No hype words ("blazing", "revolutionary"), no filler, no emoji spam.

Rules

  • Describe only what the code actually does. Read it first. Never invent features.
  • Run every command in the README on a clean clone. Fix the README or the code if it fails.
  • Check every link and image path.
  • Replace every placeholder from the template (VirtOffice, Project Name, "One-line pitch").
  • Design colors for banners and diagrams: background #0a0a09, accent #FFB300, font JetBrains Mono.
  • Lint with markdownlint-cli2.

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.