bump-mthds-version

Update minimum mthds-agent versions in SKILL.md files and a shared guide.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mthds-ai/skills --skill bump-mthds-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-mthds-version
Source: https://github.com/mthds-ai/skills/tree/main/.claude/skills/bump-mthds-version
Command: npx skills add https://github.com/mthds-ai/skills --skill bump-mthds-version

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating the minimum required mthds-agent version across all skills, ensuring consistency and preventing compatibility issues.

Core Features & Use Cases

  • Centralized Version Management: Update the min_mthds_version in a single operation.
  • Automated File Updates: Modifies both a shared version guide and individual SKILL.md files.
  • Verification: Includes steps to verify changes using grep and make check.

Quick Start

Use the bump-mthds-version skill to update the minimum mthds version to 1.2.3.

Frequently Asked Questions about bump-mthds-version

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

FAQPage Schema
How do I update the minimum mthds-agent version across all skills?

Updating the minimum mthds-agent version requires modifying a shared version guide and all individual SKILL.md files together, ensuring semantic versioning consistency across your skill collection.

What is centralized version management for skill dependencies?

Centralized version management modifies the min_mthds_version in a single coordinated operation, preventing compatibility issues by ensuring every skill references the same required agent version.

How do I verify dependency version updates in SKILL.md files?

Verify dependency version updates by running grep to check the modified SKILL.md files and executing make check, providing robust validation that all version changes applied correctly.

Can I automate semantic versioning updates for multiple skills at once?

You can automate semantic versioning updates by running a single operation that targets both the shared version guide and individual SKILL.md files, coordinating the minimum required version across all skills simultaneously.

Why do my skills have compatibility issues after changing the mthds-agent version?

Compatibility issues occur when skills reference mismatched mthds-agent versions, which is resolved by updating the shared version guide and all SKILL.md files together to enforce semantic versioning consistency.