Update plugin readme

Skill danielrosehill/Claude-Israel-Agent-Skills-Plugin/skills/update-plugin-readme

Collection of Israel-specific skills for Claude Code and other agentic CLIs

Install

npx -y skills add danielrosehill/Claude-Israel-Agent-Skills-Plugin --skill update-plugin-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

Use when the user wants to refresh the README of this plugin (or any Claude Code skills plugin) so that its "Skills" section reflects the current set of skills under `skills/*/SKILL.md`. Reads each skill's frontmatter (`name`, `description`, optional `category`), groups by category, sorts alphabetically within each group, and rewrites the README's Skills section between the `` and `` markers. Preserves everything else in the README (header, installation, license). A helper script at `scripts/generate-skills-section.py` does the extraction and emits the block on stdout; the skill is responsible for splicing it into the README. Trigger phrases - "update the plugin README", "regenerate the skills table", "refresh skills list on the plugin README", "the plugin README is out of date", "add the new skill to the README".

SKILL.md

4.2 KB, as published. Nobody here has run it

Update Plugin README

Regenerates the "Skills" section of a Claude Code skills plugin README from the actual contents of its skills/ directory.

When to run

A new skill has been added to the plugin's skills/ folder.
A skill's frontmatter description has been edited.
A skill has been removed.
The README drifts from reality (e.g. lists planned skills that already ship).

Procedure

Run python3 scripts/generate-skills-section.py <plugin-repo-path> (default: the current plugin repo).
The script emits a block starting with  and ending with . Capture its stdout.
Open README.md. Replace everything between those two markers with the new block. If the markers don't exist, locate the existing ## Skills heading and replace that section (up to the next ## heading) with the new block wrapped in markers; if there's no ## Skills heading, insert the block after the README's opening paragraph.
Remove any "Planned scope" section that contains items now implemented. Leave genuinely unimplemented items alone but move them into an "Ideas" section if still plausible; drop them otherwise.
Show the user a diff before committing.

Category taxonomy

The helper script uses folder-name inference. Preferred explicit category values (add to a skill's SKILL.md frontmatter if inference gets it wrong):

Category	Scope
`Government & Civic`	Postal service, municipal reports, vehicle licensing, national services
`Healthcare`	HMOs, medicines, medical appointments
`Emergency Preparedness`	Shelters, Home Front Command guidelines, alerts
`Localization`	Hebrew language, fonts, translation
`Media & Information`	News feeds, media lookups
`Meta / Tooling`	Skills that manage the plugin itself

Category ordering in the README is fixed (Government & Civic → Healthcare → Emergency Preparedness → Localization → Media & Information → Meta / Tooling → Other).

Fallback category inference rules

If a SKILL.md lacks a category field, the script infers from folder name:

*-municipality-*, israel-post-*, *-government-* → Government & Civic
maccabi-*, clalit-*, meuhedet-*, leumit-*, *-medicine-*, *-medical-* → Healthcare
*-shelter-*, miklat*, home-front-*, pikud-*, *-alert-* → Emergency Preparedness
hebrew-*, *-translation, *-fonts-* → Localization
*-news-*, *-rss-* → Media & Information
add-skill-*, update-plugin-*, install-*-plugin, *-plugin-* → Meta / Tooling
Otherwise → Other (prompt the user)

Prefer adding the category field to the skill's frontmatter over relying on inference.

Description sanitisation

The full description frontmatter for a skill is discovery-oriented (contains "Use when..." preamble and trigger phrases). The README version is a plain, user-facing sentence. The helper script strips the Use when the user wants to prefix, truncates at the first sentence boundary, cuts everything from Trigger phrases onward, capitalises the first letter, and drops the trailing period.

Out of scope

Regenerating the rest of the README (header, installation, license, related plugins). Those are hand-maintained.
Editing individual SKILL.md files. This skill only reads them.

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

run the skills generation script
capture the generated output
replace content between the skills markers
insert block after opening paragraph if no heading
remove implemented items from planned scope
move unimplemented items to ideas section

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