Skip to article

How Do You Keep an AI Agent's Skills as Files You Can Track?

A Gumloop skill is a folder with a SKILL.md file. Keep that folder where every change is recorded, and restore an AI agent's skill when it got worse.

By Jacqueline V. TwillieNovember 9, 20266 min readGuide
Quick answer

Download each skill from the Skills page in Gumloop and check that SKILL.md is inside. Keep it somewhere that records every change, such as GitHub. Change the file there first, then bring the change into Gumloop by editing or uploading. Compare it with the Edits tab, and restore the older version when a change made the skill worse.

Your skill lives inside Gumloop until you download it as a file.

When a skill gets worse, a correction you gave in chat, a line you tidied or an edit the AI agent made after a long task can be the cause, and you'll want to know what changed, when and why.

Gumloop keeps a timeline of its own for each skill, with what changed and when. A folder you keep yourself adds a second record outside the builder, with your reason beside each change. GitHub is one place people keep such folders, and any place that records every change works the same way.

What is a skill once you hold it as a file?

A skill is a folder with a SKILL.md file in it. The file opens with a short header holding the skill's name and description, then the instructions. Some skills add folders for scripts, references and assets, though most only need SKILL.md. Checked on 2026-11-09 against Gumloop's skills page.

For what a skill does inside an AI agent, read What Is an AI Agent Skill?.

How do you keep a Gumloop skill as a tracked file?

  1. 01

    Download the skill as it stands today.

    Open Gumloop, choose Skills in the sidebar, find the skill, open the three-dot menu at the end of its row and select Download. Open what you get and make sure you can see SKILL.md inside. Checked on 2026-11-09 against Gumloop's skills page.

  2. 02

    Put the folder where every change is recorded.

    Make one folder per skill in a place that stamps each change with a date and a note, and drop the downloaded files in unchanged. Gumloop's page describes repository syncing only as something admins set up for organization skills, so this step is yours, outside Gumloop. Checked on 2026-11-09 against Gumloop's skills page.

  3. 03

    Read the header before you trust the copy.

    Open SKILL.md and check the top. The name uses lowercase letters, digits and hyphens, up to 64 characters, with no hyphen at either end and none doubled. The description runs up to 1,024 characters with no angle brackets, and it says what the skill does and when to use it, because that's how the AI agent decides whether to load it. If a correction made in chat leaves the header broken, Gumloop skips that update and the earlier version stays. Checked on 2026-11-09 against Gumloop's skills page.

  4. 04

    Change the file first, then bring the change back.

    Edit SKILL.md in your tracked folder and write down why. For a small fix, open the skill in Gumloop, select the edit icon on the file, make the same change and select Commit. That saves your edits as one new version with its own entry in Edits. For a larger rewrite, upload the changed files as a .md, .zip or .skill file, then open the Skills page and check that there's one entry for the skill. Checked on 2026-11-09 against Gumloop's skills page.

  5. 05

    Compare the two records, and restore when a change made it worse.

    Open the skill's Edits tab. Each entry shows what changed, when, and who or which AI agent made the change. Download the skill again and compare it with your tracked copy. When a version is worse, open the Files tab, open the version picker above the file tree, hover the older version and select Restore, then confirm with Restore version. The restored text becomes a new latest version. Put the same text in your folder with a note. Checked on 2026-11-09 against Gumloop's skills page.

I am an ambassador for Gumloop. Code VIBE20 takes 20% off your first month.

What do you paste into the SKILL.md for a skill you track?

Adapt this to the skill you keep. The last section asks whoever edits it to leave a dated line.

Copy and fill in
---
name: [skill-name]
description: [What this skill does, in one sentence]. Use when [the situation that should load it].
---

## Overview
[Two sentences on the job this skill does and who reads the result.]

## Steps
1. [First thing to do]
2. [Second thing to do]
3. [Third thing to do]

## Example
Input: [a real request you would send]
Expected output: [what a good answer contains, in the order you want it]

## Rules this skill never breaks
- [A rule that must hold every time]
- Do not state [a fact the skill should never invent].

## Change record
When you edit this skill, add one line at the bottom of this section with today's date, what changed and why. Never delete earlier lines.
- [date]: First version, written by [your name].

Select an Edits entry to open the file and see whether the last section was followed.

Should AI Skill Editing stay on for a skill you track?

The toggle sits in the Skills section of the tab named Agent, and it applies to every skill on that AI agent. With it on, the AI agent can create skills and update the ones you've permission to edit. With it off, Gumloop says the AI agent still reads and uses attached skills but can't create or modify them. Reflections is a separate feature that can also propose skill edits, so set Apply Suggestions to Review Queue if you want to approve each one. Checked on 2026-11-11 against Gumloop's skills page and Gumloop's Reflections page.

Turn AI Skill Editing off on each AI agent that uses the skill when changes should come through your folder first.

What tells you the two records have drifted apart?

Download the skill and compare it with your folder. Lines in one that the other lacks mean someone changed it in between.

Look for Edits entries with no note in your folder. Gumloop saves skill edits at the end of a completed turn, so after a chat that stopped early, check the skill and repeat any correction. Checked on 2026-11-09 against Gumloop's skills page.

Read each SKILL.md again on the schedule in How Often Should You Review an AI Agent's Instructions?. Before you upload a folder someone else wrote, read How Do You Vet an AI Agent Skill Before You Download It?.

Frequently asked questions

Can I keep a copy of a skill someone shared with me?

It depends on your role. A Use Only role can't see the skill's files, so there's nothing to keep. A Viewer can see the files and use the skill, so that's where you'd look for Download in the row's three-dot menu.

What if my skill shows Synced from GitHub?

Gumloop says the skill is synced from a repository and that you change it there. Keep your history in the repository and leave the copy in Gumloop alone.

Why keep a folder when Gumloop already has an Edits tab?

The folder gives you a copy that lives outside the builder, with your reason beside every change, and it's still there if someone deletes the skill. The page lists a Delete skill option and doesn't describe a way to get a deleted skill back.

More on Ownership for Non-Technical Managers