import-agent-skill
Skill0 starsChanged 22 days agoMITView on GitHub
Use when the user gives a Claude skill, Codex skill, SKILL.md, or a marketplace listing and wants it in the skill index. Map it onto one listing. Do not paste it into a bot profile.
In this repository3 other files it gives its agents.
- find-skillSkill
- set-up-tune-upSkill
- skill-indexSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read the SKILL.md frontmatter and body, or the marketplace listing.
- Distinctive: line 21
Add a location on that listing: store, path or URL, repo or fork parent, license if known, last checked.
- Distinctive: line 32
If two different listings would both match, leave them as two listings.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Import an agent skill
Claude skills, Codex skills, and this index use the same file shape: SKILL.md with a name, a when-to-use line, a body, and optional references. A marketplace listing is the same idea with a URL instead of a local file.
Map
- Read the
SKILL.mdfrontmatter and body, or the marketplace listing. Do not read scripts into the chat. Record the source repo. - Attach to an existing listing only if this is the same skill: the same repo, or a fork of that repo. Same name is not enough. A different repo that is not a fork is a new listing.
- Add a location on that listing: store, path or URL, repo or fork parent, license if known, last checked. Index the place. Do not copy the body into the listing.
- On a new listing, write:
- name = frontmatter name, or the marketplace name
- purpose = when to use (must say when)
- keywords = exact names already in the file, plus any the user adds. Do not invent a pile.
- repo = the source repo
- success check = one line taken from the skill if it states a done bar. If it does not, ask once, or write "worked if the steps completed without a listed veto."
- Edge cases start empty unless the skill already has a clear "do not" section. Lift those as veto rows.
- Lessons start empty.
- Show the listing and the new location before they land.
If two different listings would both match, leave them as two listings. The load rule will refuse both.
Skip
- Secrets, tokens, or private paths
- A license you cannot use
- Identity or standing locks. Those stay in the profile.
An imported skill is a retrieved skill. It does not become a standing instruction.
Tune-Up, by Viaknox™. Code and text MIT licensed; brand art is not. Viaknox and Agent Tune-Up are trademarks of Viaknox Holding LLC; see TRADEMARK.md. Not affiliated with or endorsed by SpaceXAI (xAI).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

