Use GurusupSkills

Skills

Review, edit, approve, archive and import the skills your team's assistants can load from Gurusup, and see which ones get used.

Admins only. A skill a member publishes or you import is available to the rest of the organization only after you approve it.

A skill is a set of instructions in a SKILL.md file that an assistant loads when a task matches it, for example "how we write a renewal proposal from the HubSpot deal and the Notion pricing page". Members meet skills only through their assistant. The page sits in the Brain group of the sidebar.

Before you start

  • You are an admin. Members who open the address are sent back to their home page.
  • Your first memory build has started. Until then the page shows a blurred preview, "What your agent can do with your company's knowledge", with Connect source. See Overview.

How a skill reaches your assistant

When an assistant connects, Gurusup gives it the list of Active skills the person asking may use: name, description, categories, version and identifier. The assistant loads the full skill with skills_get only when the description matches the task. So a skill without a description is never picked. Each load counts as one use, shown on this page as Last used and Usage. Write the description as a statement of when to use the skill.

Gurusup also gives the assistant its own guides for working in Gurusup, called Gurusup skills. They are separate from your organization's skills: they are not on this page, not in the list above, and you cannot edit them. The assistant reads them with learn, which comes with the ?profile=catalog address. See Tools reference.

Every new skill starts as Pending. Until you approve it, only the person who wrote it can use it, in their personal agents and in the agents they own when they chat with them or run a routine now. Once approved, the whole organization can. Whoever publishes or saves it is told so with a pending-approval notice, in their assistant and on this page. A member's notice says "Ask an admin in your organization to approve it." An admin's notice says they can approve it now, and their assistant can do it without opening this page.

SourceHow it arrives
A member's assistantThe member publishes a skill with skills_publish, only for categories they may see.
An adminImport skills, or Edit on an existing skill.
GurusupGurusup can propose a skill or a new version, with a Why this was proposed section, when skill proposals are switched on for the service. Not every organization gets them.

A skill with an identifier that already exists does not replace it. It adds a new Pending version, and the Active one stays in use until you approve the new one.

Publishing a new version of an existing skill needs permission to edit it: only its creator or an organization admin has it. This holds from the app, from an assistant, from a package and from an upload link. A member who can read the skill but did not create it gets "Only this skill's creator or an organization administrator can edit it or publish a new version. To publish your own version, use a different skill name."

Find a skill

The page, titled Skills ("What the agent can do, how much it's used, and what's pending review."), has three tabs, each with a count: Pending, Active and Archived. It opens on Pending when a skill waits for review, and on Active when none does.

ColumnWhat it shows
SkillName and description, or "No description".
AuthorWho created it, "You" if you did.
UsesHow many times it was loaded. A dash when none.
Last usedHow long ago an agent, Claude or ChatGPT last loaded the skill, such as 5m ago, 3h ago or 2d ago. Never when it has not been used.
UpdatedWhen it last changed. Hidden on narrow windows.
TagsThe tags. Shown only when a skill has some. Hidden on narrow windows.

Pending and Archived list the most recently updated first; Active the most recently used. Click a heading, or use Sort and pick Name, Usage, Last used or Updated, and repeat to reverse it. A skill that was never used always stays at the bottom.

A use is one load of the skill's SKILL.md, or one download of its package, by an assistant or an agent, whether through MCP, Claude, ChatGPT or an agent in Gurusup. Opening a skill on this page, listing skills and reading its other files do not count. The history starts on 17 November 2026: "Usage history starts Nov 17, 2026." appears on the Usage tab of a skill.

Search skills also matches description, identifier, version and knowledge access.

Review a pending skill

Open the skill

Click a row in Pending. The skill opens as its own page, with a back link, its name, status and actions. On Pending, arrows move to the previous or next skill, with your position, for example "3 of 34".

Read what it does

The Content tab shows who created it ("You" if you did), its version, when it was updated, the description and the full instructions of SKILL.md. A skill with no description will never be picked: add one with Edit.

See what changed

For a new version of an existing skill, SKILL.md shows what changed from the version it was built on, not the full text. Added lines start with + and removed lines with −, and the header gives the totals, for example +4 −2. Each change keeps three lines of context, and a run of other lines folds into "N unchanged lines": click it to open it. Show full SKILL.md shows the whole file and Show changes brings the comparison back. Files added, removed or modified in the version are listed below as Added, Removed or Modified, with their path. A skill with no earlier version shows the full SKILL.md.

Check why and when

Why this was proposed (or Why this update was proposed for a new version of an approved skill) shows the reason and what changed. "This skill looks like it touches knowledge it has not been given access to." means you should check Knowledge access first. When it should fire lists requests under Should trigger and Near misses.

Check for duplicates

A notice reading "May duplicate" followed by skill names, and "Check before approving.", appears when other skills overlap with this one. Click a name to open that skill.

Check how it is used

The Usage tab shows a chart of uses over the last 30 days, Most used by (people and agents) and Assigned to. With no uses it reads "No uses in the last 30 days." The Process tab is described below.

Approve, edit or archive

Approve makes it Active. Edit changes it first, and Archive sets it aside, from the Skill actions menu. Gurusup confirms "[name] is now active." or "[name] is now archived." and opens the next skill.

The Content tab also shows Tags and the skill's Files. Skill actions also has View source (and View document to go back) and Download. When a skill has several pending versions, the table shows the latest and Approve approves it; the older ones stay under Earlier pending versions.

See the process of a skill

The Process tab draws the steps of the skill as a diagram. What it shows depends on your plan.

PlanWhat you see
FreeAn example process, with "This is an example. Upgrade to see the process of your own skills." and Upgrade, which opens the plans.
Pro, Custom and other paid plansThe process of your own skill. Gurusup generates it, so the tab first shows "Preparing process".

If Gurusup cannot generate it, the tab says "This process could not be generated." Admins get Retry; "Retry could not be started. Contact support for help." means you contact support. "The process view could not be loaded." means you reload the page.

Approving a new version of an Active skill replaces the old one for every assistant. Other pending versions built on the replaced one become Outdated.

Edit a skill

Select Edit in the panel.

FieldNotes
NameRequired. Up to 240 characters.
VersionOptional. Up to 80 characters. Empty keeps the current version, or 1.0.0.
Description"When Gurusup should use this skill." Up to 2000 characters.
TagsComma separated, for example sales, analysis. Stored in lowercase, at most 50.
Knowledge access"Who this skill may answer for": general, marketing, sales, finance, product, engineering, customers, hr, leadership. Ticking one unticks general; clearing all goes back to general.
SKILL.mdRequired. Up to 200,000 characters.

Click Save. Gurusup shows the pending-approval notice, or "[name] saved." when there is no notice. A Pending skill changes in place. An Active skill gets a Pending version with your changes (or updates the one already pending) and stays in use until you approve it. Cancel with changes asks Discard your changes?: Keep editing or Discard changes.

Gurusup rewrites the header of SKILL.md from the identifier and description on each save, and drops any other header fields. The name in that header is the skill's identifier and cannot change. If you edit it, the editor stops the save and shows "SKILL.md line 2, field name: the name must stay [slug]. To rename the skill, change the Name field above." under SKILL.md. To rename a skill, change Name.

When the save fails, the message gives the reason Gurusup sent back.

Archive and restore

Archive takes a pending or active skill off the list assistants see. Gurusup asks "Archive [name]?" and says "It will no longer be available to agents. You can restore it later." It stays on the page; there is no delete and no Reject. To set a proposal aside, archive it.

On Archived, Restore, in the Skill actions menu, brings a skill back to Active if it was approved before, or to Pending if not. Approve shows only on archived skills that were never approved.

Import skills

You import one skill per ZIP. A ZIP holds SKILL.md and the files the skill uses, at the ZIP root or inside one skill folder.

Open the dialog

Select Import skills. Drop or pick .zip files, several at once. The dialog says "One skill per ZIP. Select several ZIPs to import several skills. Up to 20 MiB of files per skill." Each ZIP becomes a Pending skill.

Check what Gurusup read

Each row shows the skill's name and description from the SKILL.md header, and N files to open the list of files. To change the instructions or description, edit SKILL.md in your ZIP before importing. A row that could not be read shows why and Read ZIP again, except a file that is not a ZIP: that row has no Read ZIP again, because reading it again would fail.

Choose who the skill is for

Knowledge access is never read from the ZIP and starts as general. Set it per skill with the categories button, or use Set knowledge access for all, then Apply to every file. The X removes a row.

Import

Click Import N. The button is off when every file in the list is blocked; if only some are blocked, it stays on. Each row shows Importing…, then its outcome. Gurusup shows the pending-approval notice and takes you to Pending. If the skills come in without a notice, it says "1 skill imported." or "N skills imported." and stays where you are.

Gurusup identifies a skill by the name in the SKILL.md header (lowercase words joined by hyphens), which must match its skill folder. A ZIP matching an existing skill becomes a new Pending version. Files that didn't go in stay in the dialog with the reason, reading "N skills already imported and waiting for approval. M left.", and Cancel becomes Done.

Limits

WhatLimit
Files of one skill, unpacked20 MiB in total
The ZIP you upload21 MiB
Files in one skill512
SKILL.md200,000 characters
A text file edited in the browser1 MiB. Larger files can be replaced, not edited.
OutcomeMeaningWhat to do
ImportedIn Pending. The row leaves the dialog.Review it.
Already existsDespite the label, Gurusup refused the write because your organization is being reset.Wait a few minutes, then Import again.
RejectedThe content is invalid. The row shows why.Fix the row and import again.
FailedSomething else went wrong. The row reads "Gurusup couldn't complete this request. Your selected files and edits are still here. Contact support if this continues."Import again, then contact support.

If something goes wrong

Import messages. File problems show straight away, in the row of the ZIP, and others after you press Import. Each message says what to fix.

MessageFix
"This ZIP is 22.4 MiB. A skill can be at most 20 MiB. Remove or compress large files and choose it again."Make the skill smaller, then choose the ZIP again.
"This ZIP is X MiB and the upload limit is 21 MiB. Remove or compress large files."Same, when the server refuses it.
"The skill exceeds 20 MiB after unpacking. Remove or compress large files."The files are over 20 MiB once unpacked. Remove or compress large ones.
"This ZIP has more than 512 files. Remove unneeded files."Keep one skill with at most 512 files.
"This ZIP repeats a file path. Keep one copy of each file."Remove the duplicate.
"[file] can't be used as a skill. Choose a ZIP of the skill folder with its SKILL.md inside."The file is not a ZIP. Pack the skill folder as a ZIP.
"Each ZIP must contain exactly one SKILL.md. Upload a separate ZIP for each skill."Split the ZIP.
"Put SKILL.md and its files at the ZIP root or inside one skill folder."Move the files.
"This ZIP could not be opened. Create a new ZIP containing one skill and upload it again."Create the ZIP again.
"This ZIP is password-protected. Upload a copy without a password."Remove the password.

When the SKILL.md header cannot be read, the message names the line, the column and the field, and says how to fix it. The numbers below are examples. It appears under SKILL.md in the editor and in the row of the ZIP in the import dialog.

MessageFix
"SKILL.md line 3, column 45, field description: the value contains ': ' and isn't quoted. Wrap the value in double quotes."Wrap the value in double quotes.
"SKILL.md line 3, column 45, field description: a quote is not closed. Close the quote or remove it."Close the quote.
"SKILL.md line 5, column 1, field name: field name appears twice (lines 2 and 5). Keep one."Keep one copy of the field.
"SKILL.md line 3, column 1, field metadata: indentation contains tabs. Replace tabs with spaces."Use spaces.
"SKILL.md line 2, column 1, field name: the name does not match the skill folder. Set name to 'folder-name'."Set name to the skill folder's name.
"SKILL.md, field description: a description is required. Add 1 to 1,024 characters explaining when to use the skill."Add a description.
"SKILL.md line 3, column 14, field description: the description has N characters. Shorten it to 1,024 characters or fewer."Shorten it. A skill saved earlier with a longer description can now be edited to replace it, from Edit or in SKILL.md, as long as the new description fits.
"SKILL.md line 1: the header is missing. Add name and description between opening and closing '---' lines."Add the header.
"SKILL.md line 1 opens the header with '---' but no closing '---' line follows. Add '---' after the last header field."Close the header.
"SKILL.md line 4, column 10, field version: the value must be text, not a date, number, boolean, null or collection. Wrap the value in double quotes; use finite numbers only."Quote the value.
"SKILL.md line 4, column 14, field description: aliases are not allowed. Write the value out."Write the value out.
"SKILL.md: the instructions exceed 200 KB. Shorten them and move details into references."Shorten SKILL.md.

Skill files, when you edit a skill:

MessageFix
"[path] is 22.0 MiB and the limit is 20 MiB. Remove or compress this file."Choose a smaller file.
"This skill is 22.0 MiB and the limit is 20 MiB. Remove or compress large files. The biggest: a.png (10.0 MiB), b.png (8.0 MiB), c.png (4.0 MiB)."Remove or compress the files it lists.
"Up to 512 files and 20 MiB in total. Text up to 1 MiB can be edited here; larger files can be replaced."This is the help line under the files, not an error.

Page and panel messages:

MessageFix
"Skills could not be loaded" with "Reload this page to try again."Reload the page.
Based on an older version. The active version has changed since.Another version was approved after this one was proposed, so the changes shown are against the version it was built on. Also read the Active version before you approve.
"Couldn't load the previous version, so changes can't be shown. Review the full SKILL.md below."Read the full SKILL.md shown under the message. If it keeps happening, contact support.
"This comparison is too large to display. Review the full SKILL.md below."Read the full SKILL.md shown under the message.
No changes to SKILL.mdThe text matches the version it was built on. Changed files, if any, are listed below.
This version is no longer waiting for review. Refresh the page to see its current state.Someone else changed it. Reload the page.
A newer version of this skill was approved after this one was proposed. Review the latest version instead.Review the newer version.
"Could not update skill." or "Could not save skill." followed by the reason Gurusup givesDo what the reason says. If it gives none, try again, then contact support.
"SKILL.md line 2, field name: the name must stay [slug]. To rename the skill, change the Name field above."Put the original name back in the SKILL.md header. To rename the skill, change Name.
"Gurusup couldn't complete this request. Your selected files and edits are still here. Contact support if this continues."Your files and edits are kept. Try again, then contact support.
"Give the skill a name." or "A skill needs its SKILL.md content."Fill in Name or SKILL.md.
No skill called "…".The link points to no skill.
"… is Superseded and is not listed here."That version is in a status without a tab, such as superseded.
No skills match "…".Change the search.
No skills to show with "Nothing waiting for review. New proposals land here as they come in.", "Approve a pending skill and it becomes part of what the agent can do." or "Nothing archived yet."The tab is empty.