update-repo

Update agent submodules, refresh GitHub star counts, and regenerate the README agent table.

4|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/7hinkDifferent/agent-cracker --skill update-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-repo
Source: https://github.com/7hinkDifferent/agent-cracker/tree/main/.claude/skills/update-repo
Command: npx skills add https://github.com/7hinkDifferent/agent-cracker --skill update-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating the repository's agent submodules, refreshing their GitHub star counts, and regenerating the README's agent table, ensuring all project information is current and accurate.

Core Features & Use Cases

  • Submodule Updates: Pulls the latest commits for all agent submodules or a specified agent.
  • Star Count Refresh: Fetches the latest star counts for agents from GitHub.
  • README Regeneration: Automatically updates the agent table in the main README file.
  • Status Check: Provides a current status of all submodules.
  • Use Case: After adding a new agent or updating an existing one, run this skill to ensure the project's documentation and data are synchronized with the latest changes.

Quick Start

Run the update-repo skill to update all agent submodules and refresh the README table.

Frequently Asked Questions about update-repo

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

FAQPage Schema
How do I automatically update git submodules and refresh repository documentation?

To automatically update git submodules and refresh repository documentation, you can use a bash scripting skill that pulls the latest submodule commits, fetches GitHub star counts, and regenerates the README agent table to ensure project information stays synchronized.

How does fetching GitHub star counts work for repository agents?

Fetching GitHub star counts works by using bash scripts with network access to the GitHub API, retrieving the latest repository metrics for your agents and automatically injecting those updated counts into the README agent table.

Can I use bash scripts to regenerate a README agent table for specific submodules?

Yes, you can use bash scripts to regenerate a README agent table by either pulling the latest commits for all agent submodules or targeting a specified agent, updating the documentation table to reflect the specific changes.

What is the best way to synchronize agent repository data after adding a new submodule?

The best way to synchronize agent repository data after adding a new submodule is running an automation skill that manages submodule commits, fetches external star data via the GitHub API, and regenerates the README table.

Do I need network access to the GitHub API for updating repository star counts?

Yes, you need network access to the GitHub API for updating repository star counts, because the automation script must actively fetch external star data from GitHub to ensure your documentation metrics are accurate and current.

Why is my README agent table not reflecting the latest submodule commits?

Your README agent table may not reflect the latest submodule commits because the repository documentation requires explicit regeneration after pulling updates, a process that synchronizes the agent table with the latest changes.