How do I install the Github To Skills skill?

Run npx skillmds add tools-only/github-to-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github To Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github To Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github To Skills free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Github To Skills?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github To Skills by tools-only — Agent Skill

Name: Github To Skills
Rating: 4.2 (5 reviews)
Author: tools-only

Github To Skills

Automated factory for converting GitHub repositories into specialized AI skills. Use this skill when the user provides a GitHub URL and wants to "package", "wrap", or "create a skill" from it. It automatically fetches repository details, latest commit hashes, and generates a standardized skill structure with enhanced metadata suitable for lifecycle management.

tools-only 89ee9af 3 files · 6.6 KB Updated Sep 9, 2026 7 repo stars

File contents

GitHub to Skills Factory

This skill automates the conversion of GitHub repositories into fully functional AI skills.

Core Functionality

Analysis: Fetches repository metadata (Description, README, Latest Commit Hash).
Scaffolding: Creates a standardized skill directory structure.
Metadata Injection: Generates SKILL.md with extended frontmatter (tracking source, version, hash) for future automated management.
Wrapper Generation: Creates a scripts/wrapper.py (or similar) to interface with the tool.

Usage

Trigger: /GitHub-to-skills <github_url> or "Package this repo into a skill: "

Required Metadata Schema

Every skill created by this factory MUST include the following extended YAML frontmatter in its SKILL.md. This is critical for the skill-manager to function later.

---
name: <kebab-case-repo-name>
description: <concise-description-for-agent-triggering>
# EXTENDED METADATA (MANDATORY)
github_url: <original-repo-url>
github_hash: <latest-commit-hash-at-time-of-creation>
version: <tag-or-0.1.0>
created_at: <ISO-8601-date>
entry_point: scripts/wrapper.py # or main script
dependencies: # List main dependencies if known, e.g., ["yt-dlp", "ffmpeg"]
---

Workflow

Fetch Info: The agent first runs scripts/fetch_github_info.py to get the raw data from the repo.
Plan: The agent analyzes the README to understand how to invoke the tool (CLI args, Python API, etc.).
Generate: The agent uses the skill-creator patterns to write the SKILL.md and wrapper scripts, ensuring the extended metadata is present.
Verify: Checks if the commit hash was correctly captured.

Resources

scripts/fetch_github_info.py: Utility to scrape/API fetch repo details (README, Hash, Tags).
scripts/create_github_skill.py: Orchestrator to scaffold the folder and write the initial files.

Best Practices for Generated Skills

Isolation: The generated skill should install its own dependencies (e.g., in a venv or via uv/pip) if possible, or clearly state them.
Progressive Disclosure: Do not dump the entire repo into the skill. Only include the necessary wrapper code and reference the original repo for deep dives.
Idempotency: The github_hash field allows the future skill-manager to check if remote_hash != local_hash to trigger updates.

---name: github-to-skillsdescription: Automated factory for converting GitHub repositories into specialized AI skills. Use this skill when the user provides a GitHub URL and wants to "package", "wrap", or "create a skill" from it. It automatically fetches repository details, latest commit hashes, and generates a standardized skill structure with enhanced metadata suitable for lifecycle management.license: MIT--- # GitHub to Skills Factory This skill automates the conversion of GitHub repositories into fully functional AI skills. ## Core Functionality 1. **Analysis**: Fetches repository metadata (Description, README, Latest Commit Hash). 2. **Scaffolding**: Creates a standardized skill directory structure. 3. **Metadata Injection**: Generates `SKILL.md` with extended frontmatter (tracking source, version, hash) for future automated management. 4. **Wrapper Generation**: Creates a `scripts/wrapper.py` (or similar) to interface with the tool. ## Usage **Trigger**: `/GitHub-to-skills <github_url>` or "Package this repo into a skill: <url>" ### Required Metadata Schema Every skill created by this factory MUST include the following extended YAML frontmatter in its `SKILL.md`. This is critical for the `skill-manager` to function later. ```yaml --- name: <kebab-case-repo-name> description: <concise-description-for-agent-triggering> # EXTENDED METADATA (MANDATORY) github_url: <original-repo-url> github_hash: <latest-commit-hash-at-time-of-creation> version: <tag-or-0.1.0> created_at: <ISO-8601-date> entry_point: scripts/wrapper.py # or main script dependencies: # List main dependencies if known, e.g., ["yt-dlp", "ffmpeg"] --- ``` ## Workflow 1. **Fetch Info**: The agent first runs `scripts/fetch_github_info.py` to get the raw data from the repo. 2. **Plan**: The agent analyzes the README to understand how to invoke the tool (CLI args, Python API, etc.). 3. **Generate**: The agent uses the `skill-creator` patterns to write the `SKILL.md` and wrapper scripts, ensuring the **extended metadata** is present. 4. **Verify**: Checks if the commit hash was correctly captured. ## Resources - `scripts/fetch_github_info.py`: Utility to scrape/API fetch repo details (README, Hash, Tags). - `scripts/create_github_skill.py`: Orchestrator to scaffold the folder and write the initial files. ## Best Practices for Generated Skills - **Isolation**: The generated skill should install its own dependencies (e.g., in a venv or via `uv`/`pip`) if possible, or clearly state them. - **Progressive Disclosure**: Do not dump the entire repo into the skill. Only include the necessary wrapper code and reference the original repo for deep dives. - **Idempotency**: The `github_hash` field allows the future `skill-manager` to check `if remote_hash != local_hash` to trigger updates.

Frequently asked questions