Managing Skills

How to discover, browse, install, update, and remove skills in SuperAgent -- including skill status tracking and required environment variables.

SuperAgent provides tools for discovering skills from your configured skillsets, installing them into agents, tracking their status, and keeping them up to date.

Configuring skillsets

Before you can install skills, you need at least one skillset configured. SuperAgent ships with a default public skillset, but you can add your own.

To add a skillset:

  1. Open Settings and navigate to the Skillsets tab.
  2. Enter the Git repository URL of the skillset (HTTPS or SSH format).
  3. Click Add. SuperAgent validates the repository by cloning it and checking for a valid index.json.

Once added, the skillset appears in your list with its name, description, and skill count. You can add multiple skillsets -- skills from all configured skillsets are available for installation across your agents.

For private GitHub repositories, you need SSH authentication configured. SuperAgent clones repositories with GIT_TERMINAL_PROMPT disabled, so interactive password prompts are not supported.

Platform skillsets

If you are connected to a SuperAgent platform organization, your organization's skillsets are synced automatically. These appear in your skillsets list with a "Platform" badge and do not require manual URL entry.

Refreshing a skillset

Click the refresh button next to any skillset to pull the latest changes from the remote repository. This updates the local cache so that new skills and version changes become visible.

Removing a skillset

Click the delete button next to a skillset to remove it from your configuration. This removes the skillset from your settings and cleans up the local cache. Skills that were already installed into agents are not affected -- they remain in the agent's workspace.

Discovering and browsing skills

Each agent has a Skills section on its home page. If there are skills available from your configured skillsets that the agent does not yet have installed, an Add Skill button appears.

Clicking Add Skill opens a browse dialog where you can:

  • Search skills by name or description.
  • Filter by skillset when you have multiple skillsets configured.
  • Page through results if the skill catalog is large.

Each skill card shows the skill name, which skillset it belongs to, and its version number.

Installing a skill

To install a skill into an agent, click the install button on its card in the browse dialog. SuperAgent copies the skill's files from the skillset cache into the agent's workspace at .claude/skills/<skill-name>/.

Required environment variables

Some skills declare required environment variables in their SKILL.md frontmatter. These are typically API keys or configuration values the skill needs at runtime.

When you install a skill that has required environment variables, SuperAgent opens a dialog prompting you to enter each value. The variables are stored securely as agent secrets and made available to the agent during execution.

Example of a skill that requires environment variables:

---
name: Database Query
description: Queries a PostgreSQL database and returns formatted results.
metadata:
  version: 1.0.0
  required_env_vars:
    - name: DATABASE_URL
      description: PostgreSQL connection string
    - name: DB_READ_ONLY_TOKEN
      description: Read-only access token for the database
---

You must provide all required environment variables before the install completes.

Skill status tracking

Every installed skill displays a status badge that tells you whether it is current, has updates available, or has been modified locally. SuperAgent computes status by comparing the installed skill's content hash against the original and the latest version in the skillset cache.

Up to date

The skill matches the version in the skillset repository. No action is needed.

Update available

The skillset repository contains a newer version of this skill -- either a version bump in index.json or changed file content. An Update button appears on the skill card. Clicking it pulls the latest version from the skillset and overwrites the local copy.

Locally modified

You (or the agent) have edited the skill's files since it was installed, and the content no longer matches the original. This status appears when the SHA-256 hash of the installed skill package differs from the hash recorded at install time.

When a skill is locally modified, you have several options:

  • Submit changes -- Open a pull request (for GitHub skillsets) or submit through the platform queue (for platform skillsets) to propose your changes back to the upstream repository. SuperAgent generates AI-suggested PR titles, descriptions, and version bumps based on the diff.
  • Force sync -- Discard your local changes and replace the skill with the latest version from the skillset. This is a destructive action that cannot be undone.

Local

The skill was created locally and is not linked to any skillset. Local skills have no upstream tracking. If you have a skillset configured that supports publishing, you can publish a local skill to make it available to others.

Updating skills

SuperAgent automatically checks for skill updates when you navigate to an agent. A background refresh pulls the latest changes from all configured skillsets and compares them against your installed skills.

To manually update a single skill, click the Update button on any skill showing the "update available" status. SuperAgent re-fetches the skillset, copies the latest files into the agent's workspace, and updates the metadata to record the new version and content hash.

Publishing and submitting changes

When you modify an installed skill, you can contribute your changes back to the skillset. The workflow depends on the skillset's provider:

GitHub skillsets (pull request)

  1. Click Open PR on a locally modified skill.
  2. SuperAgent generates a suggested title, description, and version bump using AI.
  3. Review and edit the suggestions, then confirm.
  4. SuperAgent forks the repository (if needed), creates a branch, commits your changes, and opens a pull request against the upstream repository.

This requires the GitHub CLI (gh) to be installed and authenticated.

Platform skillsets (hosted submit)

  1. Click Submit on a locally modified skill.
  2. Review the suggested title and description.
  3. SuperAgent submits the changes to the platform's review queue.
  4. The submission status is tracked in the skill's metadata. Once the platform processes it (merged or rejected), the skill status updates accordingly on the next refresh.

Publishing a local skill

If you have a local skill (not linked to any skillset), you can publish it to a configured skillset:

  1. Click the publish button on the local skill's card.
  2. Select the target skillset.
  3. Review the AI-generated PR title, description, and version.
  4. Confirm to submit the skill to the skillset repository.

The skill is added to the skillset's index.json and placed under skills/<skill-name>/ in the repository.

Removing a skill

To remove an installed skill, delete its directory from the agent's workspace. The skill's directory is located at .claude/skills/<skill-name>/ inside the agent's workspace folder. Removing the directory removes the skill from the agent.

Removing a skill from an agent does not affect other agents that may have the same skill installed, nor does it remove the skill from the skillset repository.