Contents

Features

Agent Library

•6 min read
Agent Library

Agent Library

The Agent Library is a panel in the Ritemark activity bar that finds your AI agents, skills, and commands across .claude/, .agents/, and AGENTS.md files, then lets you open them, create new ones, duplicate existing ones, and start a chat with any agent in one click.

If you write Claude Code agents or OpenAI Codex skills, this is where they live now.

Agent Library empty state with New skill and New agent buttons

What It Scans

The library scans three things, automatically, on workspace open and on refresh:

  • .claude/agents/, .claude/skills/, .claude/commands/ in your workspace root and your home directory (~/.claude/)
  • .agents/ directory at workspace root, for OpenAI/Codex layout
  • AGENTS.md and CLAUDE.md at workspace root, surfaced as the main agent config for that workspace

Workspace-scoped and user-scoped entries are grouped separately, so you always know whether a helper belongs to one project or applies to everything you do.

Each row shows the name and description from frontmatter. If a helper has no description, the row marks it as missing - a hint that the frontmatter could use a quick cleanup.

As of v1.7.0, the library preserves branded casing for known agent names. So "UX Expert", "PR Reviewer", "QA Validator", and "VS Code Expert" appear with their proper casing in the row label, even if the underlying slug uses lowercase.

Creating New Agents and Skills

The empty state shows two buttons: New skill and New agent. Either button scaffolds a fresh markdown file with the right frontmatter, opens it in the editor, and you start writing.

Once the library has at least one entry, the buttons move to a + affordance on each section header. The + next to "Agents" creates an agent. The + next to "Skills" creates a skill. The intent comes from where you click.

Creating a new agent from the library

The file gets created in the right scope (workspace or user, depending on which section you used) with starter frontmatter that includes name, description, icon, and color.

Forking with Duplicate

Right-click any row in the library and you get a context menu with these actions:

  • Open - opens the source .md file in the editor
  • Duplicate - copies the row as a new file you can edit
  • Reveal in Finder (macOS) or Reveal in File Explorer (Windows) - shows the file in the OS file manager
  • Move scope - moves between workspace and user scope
  • Delete - removes the file

Duplicate is the primary way to fork. Find a skill that is almost what you need, duplicate it, edit the copy, and you have a new helper that started from something that already worked. This is how you build up a library over time.

Tip: Duplicate keeps the original frontmatter, including the icon and color. Change the name and description first, then iterate on the body.

Launch Chat: Talk to Any Agent

This is the feature most people pick up first. Right-click an agent and choose Launch Chat. The AI panel opens with that agent pinned as hidden context, an indigo chip in the composer shows you which agent is active, and you start typing.

Pinned agent chip in the composer

How it works underneath:

  1. The agent's full instructions are sent once on the first turn
  2. Subsequent turns get a short reminder, so you do not burn context resending the entire prompt every message
  3. Switching agents in-thread sends an explicit handoff note so the new agent knows what was happening before it took over

The @mention popup uses the same Pin Agent mechanism. One chip, one source of truth. No "wait, did the @mention actually take effect" guessing.

Agents Across Runtimes

In v1.6.3, conversations are durable across runtimes. You can pin an agent and start with Claude, then switch to Codex on the next turn. Both turns stay in the same thread, with provenance shown on each assistant response (which runtime, which model). The agent context follows the conversation, not the runtime.

Switching agents inside one conversation

The Plan and Edit toggle on Codex is a per-turn footer toggle now, not a per-conversation property.

Icons and Colors

Every row has a color-coded icon chip (32×32 pixels, eight brand colors, thirty-three Phosphor icons). Icons are auto-assigned from the agent's name and description keywords. A skill called "summarize meeting notes" gets a notes-style icon. A "code reviewer" gets something terminal-flavored.

If the auto-assignment is wrong, override it in frontmatter:

---
name: my-skill
description: What this skill does
icon: notebook
color: indigo
---

Available icons match the Phosphor icon library; available colors are the eight Ritemark brand colors. The library validates the values on parse and falls back to the auto-assignment if either is invalid.

AGENTS.md and .agents/ Support

If you keep your agent definitions in OpenAI/Codex layout instead of Anthropic's .claude/, the library finds them without configuration. AGENTS.md at workspace root is treated as the main agent config for that workspace and surfaces in the library alongside skills and commands.

CLAUDE.md shown in the Agent Library as the main agent config

This means you can use Ritemark's library UI even if your team has standardized on the OpenAI conventions instead of Anthropic's.

Starter Pack

If your ~/.claude/ directory is empty on first run, Ritemark seeds four example helpers so the library is not empty out of the box:

  • skill-creator (Apache-2.0, originally from Anthropic) - a skill that helps you write other skills
  • outline-from-notes - takes raw notes and produces a structured outline
  • frontmatter-cleanup - normalizes YAML frontmatter across documents
  • document-reviewer - reviews a document for clarity, structure, and tone

Seeding only happens once and never overwrites existing files. If you already have a .claude/ directory, nothing changes.

Quick Reference

Action How
Create new agent + next to Agents row, or New agent button when empty
Create new skill + next to Skills row, or New skill button when empty
Open source file Click the row, or right-click then Open
Fork an existing helper Right-click then Duplicate
Pin agent for chat Right-click then Launch Chat
Move between workspace and user scope Right-click then Move scope
Override icon/color Add icon: and color: to frontmatter
Refresh library Refresh button in the panel toolbar

Frontmatter Reference

Minimum frontmatter for an agent or skill:

---
name: my-agent
description: One-line description of what this agent does
---

Optional fields:

---
name: my-agent
description: One-line description of what this agent does
icon: lightbulb        # any Phosphor icon name
color: indigo          # one of the 8 Ritemark brand colors
---

The frontmatter parser handles CRLF line endings and YAML block scalar syntax (>, >-, |, |-), so agents authored on Windows or with multi-line descriptions parse correctly.

Back to support
Agent Library