Skill

publish-readme

Updates public-repo README with latest skills, commands, features, screenshots, and tutorials. Use after adding new content to keep public docs current via git commit/push.

Git

Github

npx claudepluginhub vzco/arc-probe --plugin arc-probe

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Update the public-facing README on github.com/vzco/arc-probe with the latest information.

SKILL.md

Similar Skills

update-readme

129

Updates existing README.md using codebase scans, git history since last edit, changelog refresh, and audits for stale/missing sections.

8 tools

claude-coding

readme-generator

136

Generates human-focused README.md files for projects like CLI tools, libraries, and web apps. Triggers on 'write README', 'create README', 'update README'. Researches best practices and analyzes project files.

2 files

ris-claude-code

update-readme

242

Refreshes README structure and content using git-workspace-review repo context: audits languages, researches exemplars via web search, aligns outlines, applies edits. Use for structural updates.

2 files

sanctum

Stats

Parent Repo Stars10

Parent Repo Forks3

Last CommitMar 8, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

ARC Probe — Publish README

Update the public-facing README on github.com/vzco/arc-probe with the latest information.

When to use

After adding new skills, commands, features, or screenshots that should be reflected in the public README.

Steps

1. Read the current public README

cat public-repo/README.md

2. Check for new content to add

New skills in plugin/skills/ that aren't in the README skill table

New commands added to the probe DLL

New screenshots in public-repo/docs/images/

Updated tutorials

3. Update the README

Key sections to keep current:

Quick start code examples

Installation section with skill table (must list ALL skills)

Command reference tables

Screenshots (add new ones if available)

Status line (update if moving from early access to stable, etc.)

4. Do NOT add

Source code paths or architecture details that reveal private repo structure

Build instructions (binaries are pre-built)

Internal implementation details

Developer-only information

5. Commit and push

cd public-repo git add README.md git commit -m "docs: update README" git push origin main

Style guide

The public README uses:

Lowercase headings

No emoji

Short, direct sentences

Code blocks for all commands

Tables for structured data

> blockquotes for status/notes

ARC Probe — Publish README

Update the public-facing README on github.com/vzco/arc-probe with the latest information.

When to use

After adding new skills, commands, features, or screenshots that should be reflected in the public README.

Steps

1. Read the current public README

cat public-repo/README.md

2. Check for new content to add

New skills in plugin/skills/ that aren't in the README skill table
New commands added to the probe DLL
New screenshots in public-repo/docs/images/
Updated tutorials

3. Update the README

Key sections to keep current:

Quick start code examples
Installation section with skill table (must list ALL skills)
Command reference tables
Screenshots (add new ones if available)
Status line (update if moving from early access to stable, etc.)

4. Do NOT add

Source code paths or architecture details that reveal private repo structure
Build instructions (binaries are pre-built)
Internal implementation details
Developer-only information

5. Commit and push

cd public-repo
git add README.md
git commit -m "docs: update README"
git push origin main

Style guide

The public README uses:

Lowercase headings
No emoji
Short, direct sentences
Code blocks for all commands
Tables for structured data
> blockquotes for status/notes