update-skills

Fetch and merge newer skill branches into a NanoDex fork.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mbaker95/nanodex --skill update-skills-mbaker95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skills
Source: https://github.com/mbaker95/nanodex/tree/main/.agents/skills/update-skills
Command: npx skills add https://github.com/mbaker95/nanodex --skill update-skills-mbaker95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users update their local NanoDex repository with the latest skill content from the upstream repository or merge specific skill branches without performing a full repository update.

Core Features & Use Cases

  • Selective Skill Updates: Fetch and integrate new or modified skills from the main repository.
  • Branch Merging: Merge specific skill branches from a remote repository into the local fork.
  • Conflict Avoidance: Checks git status to prevent overwriting uncommitted local changes.
  • Use Case: A user wants to incorporate a newly released skill for managing GitHub issues into their NanoDex setup without updating all other parts of the repository.

Quick Start

Use the update-skills skill to fetch the latest changes for the 'github-issues' skill.

Frequently Asked Questions about update-skills

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

FAQPage Schema
How do I update specific skills from a remote git repository without a full fetch?

To update specific skills from a remote repository, fetch and merge individual skill branches into your local fork. This selective update integrates new content without pulling the entire repository history.

Can I merge upstream skill branches without losing uncommitted local changes?

Yes, you can merge upstream skill branches safely because the update process checks git status first. This prevents overwriting uncommitted local changes before integrating remote updates.

What is the best way to integrate a newly released skill into a customized fork?

The best way to integrate a new skill into a customized fork is to fetch the specific skill branch from the main repository and merge it selectively. This preserves your other local customizations.

Does updating skills require rebuilding documentation?

Updating skills may require rebuilding documentation if the merged branches include modified references. The process ensures documentation is rebuilt if necessary to reflect the new content.

When should I avoid merging skill branches into my local repository?

You should avoid merging skill branches when your git status shows uncommitted local changes. Merging with a dirty working tree risks conflicts and potential loss of your local work.