publish-readme

Update public README content with latest skills, commands, and screenshots.

15|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/vzco/arc-probe --skill publish-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-readme
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/publish-readme
Command: npx skills add https://github.com/vzco/arc-probe --skill publish-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a public README that accurately reflects the current features, skills, and screenshots, ensuring users see up-to-date information.

Core Features & Use Cases

  • Automatic README synchronization: Detects new skills and commands from the repository and updates the public README accordingly.
  • Visual consistency: Ensures the README includes the latest screenshots and tutorials.
  • Review-ready changes: Prepares clean, commit-ready diffs that comply with the project's style guidelines.

Quick Start

Synchronize the public README with the latest repository content.

Frequently Asked Questions about publish-readme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update a public README to reflect new skills and commands?

To update a public README, use this Skill to detect new skills and commands from the repository, synchronize the content, and generate commit-ready diffs that comply with your project's style guidelines.

What is the best way to keep repository documentation screenshots and tutorials consistent?

Keeping repository documentation consistent involves automatically synchronizing the public README with the latest screenshots and tutorials, ensuring visual assets match the current features without manual intervention.

How does this Skill prepare README changes for commit?

This Skill prepares README changes for commit by applying updates across skills, commands, and documentation assets, then generating clean, review-ready diffs with a clear commit message.

Can I use this Skill to avoid exposing internal paths in public repository documentation?

Yes, you can use this Skill to avoid exposing internal paths in public repository documentation, as it automatically follows a style guide designed to list all skills safely while updating the README.

What are the limitations of this Skill for updating a public repository README?

The primary limitation is that this Skill focuses strictly on updating the public README and associated documentation assets, meaning it does not manage other repository files or complex external documentation sites.