agentsclimarketplace

Writing skills readme first

Skill ceilidhboy/skills/skills/writing-skills-readme-first

Agent skills for Laravel and PHP development. Installable via npx skills@latest add ceilidhboy/skills

Install
npx -y skills add ceilidhboy/skills --skill writing-skills-readme-first

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

Before creating any new skill, check the user's personal skills repo if they have one. Use the write-a-skill skill for the template. This is the mandatory starting point for all skill creation work.

SKILL.md

1.5 KB, as published. Nobody here has run it

Writing Skills — Read Me First

Activate this skill whenever skill creation, writing, or authoring is discussed.

Rule

Before creating or modifying any skill, check whether the user has a personal skills repo configured.

Process

  1. Check for a local config — Look for ~/.config/skills/config.json. If it exists, read the skillsRepo field.

    • If found → you know where their skills repo is.
    • If not found → ask the user: "Do you have a personal skills repo you'd like new skills created in?"

  2. If the user provides a path — Save it for next time:

    • Create ~/.config/skills/config.json (and the skills directory if needed) with: 
      { "skillsRepo": "/path/to/repo" }

  3. Read the repo's conventions — Navigate to the skills repo and read:

    • README.md — for the available skills and overview
    • CONTRIBUTING.md — for the exact process to add or update skills

  4. Use write-a-skill — Follow the write-a-skill skill for the SKILL.md template and structure.

  5. If no repo exists — Skip steps 1-3 and just use write-a-skill directly. The skill will go wherever the project or user context suggests.

Gives 0 of the 12 instructions most readme changelog skills give

Counted across 471 of the 478 authors here whose files we hold, read 2026-08-06

  • follow the Keep a Changelog formatin 31 of 471, across 26 files
  • omit empty sectionsin 21 of 471
  • Run from the git repository rootin 20 of 471, across 7 files
  • save output directly to CHANGELOG.mdin 20 of 471, across 7 files
  • Group commits into logical categoriesin 19 of 471, across 6 files
  • Review the generated changelog before publishingin 19 of 471, across 6 files
  • Apply changelog guidelines and brand voicein 18 of 471, across 5 files
  • Exclude internal commits like refactoring and testsin 18 of 471, across 5 files
  • Specify date ranges for focused changelogsin 17 of 471, across 4 files
  • Convert technical commits into customer languagein 17 of 471, across 4 files
  • group commits by conventional commit typein 14 of 471
  • insert new entry below unreleased sectionin 14 of 471

Said here and by no other author read

  • activate when skill creation is discussed
  • check for a local skills config file
  • ask the user if no config file is found
  • save the provided skills repo path for next time
  • read the repo contributing guide
  • use the write-a-skill template

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.