Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
MagicSkills：Stop copying skills between agents. MagicSkills turns scattered SKILL.md folders into reusable, composable, tool-ready capabilities.
| Date | Stars |
|---|---|
| 2026-07-31 | 310 |
| 2026-08-02 | 310 |
| 2026-08-06 | 310 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<div align="center">
<img src="./image/Logo.png" alt="MagicSkills" width="300" />
<br/>
<br/>
# 🪄 MagicSkills: **Build Skills Once, Reuse Them Across Every Agent**
<br/>
**Local-first** skill infrastructure for multi-agent projects
Turn scattered `SKILL.md` directories into a reusable · composable · syncable · callable shared capability library
<br/>
<table>
<tr>
<td align="center"><b>🤖 Agent Apps</b></td>
<td align="center"><b>🧩 Agent Frameworks</b></td>
</tr>
<tr>
<td align="center">Claude Code · Cursor · Windsurf · Aider · Codex<br/><sub>Any agent app that can read `AGENTS.md`</sub></td>
<td align="center">AutoGen · CrewAI · LangChain · LangGraph · Haystack<br/>Semantic Kernel · smolagents · LlamaIndex<br/><sub>Any agent framework with tool / function integration support</sub></td>
</tr>
</table>
<br/>
<sub>Initiated and maintained by Narwhal-Lab, Peking University</sub>
<p align="center">
<a href="https://www.pku.edu.cn">
<img src="./image/image4.png" alt="Peking University" height="42" />
</a>
<a href="https://github.com/Narwhal-Lab">
<img src="./image/image5.png" alt="Narwhal-Lab" height="42" />
</a>
</p>
<p>
<a href="https://github.com/Narwhal-Lab/MagicSkills"><img src="https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13-blue.svg?style=for-the-badge&logo=python&logoColor=white" alt="Python 3.10‑3.13"/></a>
<a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-green.svg?style=for-the-badge" alt="License: MIT"/></a>
<a href="https://github.com/Narwhal-Lab/MagicSkills"><img src="https://img.shields.io/github/stars/Narwhal-Lab/MagicSkills?style=for-the-badge&logo=github" alt="GitHub stars"/></a>
</p>
<br/>
<br/>
English | [简体中文](./README.zh-CN.md)
[Overview](#overview-en) · [Quick Start](#quick-start-en) · [How It Works](#how-it-works-en) · [CLI](./doc/cli.md) · [Python API](./doc/python-api.md) · [Tips](#tips-en)
</div>
---
## Demo Video
https://github.com/user-attachments/assets/dd04d9bf-00f9-4a00-94d5-9d3de2c74600
## 🧭 Overview
MagicSkills is a local-first skill infrastructure layer for multi-agent projects.
It turns scattered `SKILL.md` directories into something you can:
- install into one shared skill pool
- compose into per-agent `Skills` collections
- sync into `AGENTS.md`
- expose as a tool through one stable API
The core model is simple:
- `Skill`: one concrete skill directory
- `ALL_SKILLS()`: access the current built-in `Allskills` view
- `Skills`: the subset an agent or workflow actually uses
- `REGISTRY`: the global named-collection registry persisted across runs
MagicSkills is most useful when:
- you maintain multiple agents that should reuse one skill library
- you already have `SKILL.md` content but no install, selection, or sync workflow
- some agents read `AGENTS.md`, while others need direct tool integration
A common real-world scenario is: you have one reusable shared skill, and many different agent apps and agent frameworks all need to use it.
For example, the same `c_2_ast` skill may need to be shared across Claude Code, Cursor, Windsurf, Aider, Codex, AutoGen, CrewAI, LangChain, LangGraph, Haystack, Semantic Kernel, smolagents, and LlamaIndex.
In that case, the recommended approach is not to copy that skill into every agent project separately. Instead, keep it in one shared skill pool, build one or more named `Skills` collections from that same underlying skill, and expose those collections differently depending on whether the target runtime reads `AGENTS.md` or integrates through tools / functions.
## 🤔 Why MagicSkills
Without a skill layer, multi-agent projects usually drift into one of these states:
- the same skill is copied into multiple agent folders and quickly diverges
- `SKILL.md` exists, but it is still just a document, not an operational unit
- every agent loads too many irrelevant skills
- `AGENTS.md`, prompt glue, and framework tools evExcerpt of 30,974 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:783d2a8ace678d69, llm:Repository description and topics: 'agent, ai, function, skills, tool, python' and description: 'MagicSkills: Stop copying skills between agents. turns scattered SKILL.md folders into reusable, composable, tool-ready capabilities.'
matched fp:783d2a8ace678d69, llm:Repository description and topics: 'agent, ai, function, skills, tool, python' and description: 'MagicSkills: Stop copying skills between agents. turns scattered SKILL.md folders into reusable, composable, tool-ready capabilities.'
matched fp:783d2a8ace678d69, llm:Repository description and topics: 'agent, ai, function, skills, tool, python' and description: 'MagicSkills: Stop copying skills between agents. turns scattered SKILL.md folders into reusable, composable, tool-ready capabilities.'