graft-skill

Synchronize grafted GitHub skills and update README metadata.

1|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/TMYTiMidlY/skills --skill graft-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graft-skill
Source: https://github.com/TMYTiMidlY/skills/tree/main/.agents/skills/graft-skill
Command: npx skills add https://github.com/TMYTiMidlY/skills --skill graft-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill keeps grafted external GitHub skills organized, synchronizes their metadata, and prevents stale README entries by documenting the lifecycle of imported repositories.

Core Features & Use Cases

  • Lifecycle playbook guiding importing, experimental testing, stabilization, modification, synchronization, and removal of upstream skills.
  • Metadata automation that updates grafted-skills.json, records repository, branch, and sync timestamps, and keeps the README table accurate via update-readme.py.
  • Use Case: When an upstream repository adds fixes, the skill helps compare commits, choose which changes to merge, and refresh the table without breaking local adaptations.

Quick Start

After editing grafted-skills.json, ask the skill to rerun scripts/update-readme.py to refresh the table.

Frequently Asked Questions about graft-skill

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

FAQPage Schema
How do I sync external GitHub skills with my local repository?

Sync external GitHub skills by updating grafted-skills.json metadata and running scripts/update-readme.py to refresh README entries. You compare downstream files to each upstream diff prior to merging to audit new commits.

What is the best way to manage experimental and stable skill namespaces?

Manage experimental and stable namespaces by following a lifecycle playbook that guides importing, testing, stabilizing, modifying, and removing upstream skills. Metadata automation records repository, branch, and sync timestamps to track status.

How do I prevent stale README entries when importing upstream repositories?

Prevent stale README entries by running scripts/update-readme.py after editing grafted-skills.json. This metadata automation keeps the README table accurate and documents the lifecycle of imported external repositories.

Can I audit upstream commits before merging changes into local skills?

You can audit upstream commits by comparing downstream files to each upstream diff prior to syncing. This allows you to choose which changes to merge and refresh metadata without breaking local adaptations.

Does this skill management workflow require specific configuration files?

The workflow requires updating grafted-skills.json metadata to record repository, branch, and sync timestamps. After editing this JSON config, you ask the skill to rerun scripts/update-readme.py to refresh the documentation table.

What to do when an upstream repository adds fixes to imported skills?

When an upstream repository adds fixes, compare the new commits against your downstream files, choose which changes to merge, and rerun scripts/update-readme.py to refresh the README table without breaking local adaptations.