agentsclimarketplace

Readme

Skill eunai/skills/.agents/skills/readme

Agent skill packs under .agents/skills for README and changelog maintenance, Semantic Versioning, and private/public publish-boundary hygiene. MIT.

Install
npx -y skills add eunai/skills --skill readme

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Maintains README documents using Make a README and Google README guidance for clear project identity, setup, usage, support, status, documentation links, and license coverage. Use when editing README.md, README.public.md, package READMEs, quick starts, install instructions, usage examples, documentation maps, or contributor-facing README sections.

SKILL.md

2.1 KB, as published. Nobody here has run it

README

Quick start

Read the current README and the docs it links to before editing. Keep the README as the first useful page for its audience: explain what the project is, how to start, where to get help, and where deeper docs live.

Workflow

  1. Identify the README's audience: public users, private maintainers, package consumers, or contributors.
  2. Read linked install, usage, support, status, contribution, and license docs before changing summaries.
  3. Keep examples copyable and small; include expected output when it clarifies usage.
  4. Link to deeper docs instead of duplicating long specs.
  5. Remove stale links, obsolete requirements, and hidden agent-only trigger text.
  6. Run the repo's README or docs validation if one exists.

Checklist

  • Name and description: self-explaining project name plus a specific statement of what the project does.
  • Requirements and installation: exact prerequisites, package manager commands, environment variables, and platform limits when relevant.
  • Usage: minimal working examples before advanced workflows.
  • Support: where readers should ask questions or report issues.
  • Contributing: whether contributions are accepted and how to start.
  • Status: deprecation, maintenance, or not-for-general-release notes when relevant.
  • Documentation links: user-facing or team-facing docs that belong outside the README.
  • License: accurate license name and link.

Standards

Source: eunai/skills (MIT).

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.