Skip to content

Releases

v1.2.1 - Fix YAML Parsing

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 17:38

Critical Fix 🔧

Fixed YAML formatting in the agent description that was preventing the agent from being discovered and registered.

Root Cause

The description field in the agent frontmatter was using escaped newline characters (\n) instead of proper YAML multi-line syntax:

# BROKEN - causes YAML parsing errors
description: Use this agent when...\n\nExamples:\n<example>...

The Fix

Now using proper YAML literal block scalar with |:

# WORKING - proper YAML multi-line format
description: |
  Use this agent when...
  
  Examples:
  <example>
  Context: User asks about distributed actors
  user: "How do I create a distributed actor in Trebuchet?"
  ...
  </example>

The pipe (|) character tells the YAML parser to preserve newlines and indentation, allowing the multi-line description with embedded examples to parse correctly.

Testing

After updating to v1.2.1:

/plugin update trebuchet@briannadoubt
/agents

The trebuchet-expert agent should now appear in the agents list!

Full Changelog: v1.2.0...v1.2.1

v1.2.0 - Match Official Anthropic Plugin Format

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 17:03

Major Update 🎉

Completely reformatted the trebuchet-expert agent to match the official Anthropic plugin format from the anthropics/claude-code repository.

What Changed

After studying working plugins from the official repo, I've updated our agent format to match exactly:

Removed:

  • capabilities field (not used in official plugins)
  • tools field (not used in official plugins)

Added:

  • Detailed description with embedded <example> blocks showing when Claude should invoke the agent
  • model: sonnet field for agent configuration
  • color: blue field for UI theming
  • Clear "Use this agent when..." trigger conditions
  • Multiple examples with <commentary> tags

Agent Format

The description now includes:

description: Use this agent when working with Trebuchet distributed actors, deploying to cloud platforms...

Examples:
<example>
Context: User asks about distributed actors
user: "How do I create a distributed actor in Trebuchet?"
assistant: "I'll use the Task tool to launch the trebuchet-expert agent..."
<commentary>
The trebuchet-expert should handle questions about Trebuchet framework features...
</commentary>
</example>

Based On Official Plugins

This format is modeled directly on production Anthropic plugins:

The agent should now register properly with Claude Code!

Full Changelog: v1.1.5...v1.2.0

v1.1.4 - Fix Agent Discovery

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 11:22

Critical Fix 🔧

Added the missing agents field to plugin.json - this is required for Claude Code to discover and register agents from plugins.

Root Cause

The plugin.json was missing this required field:

{
  "agents": "./agents/"
}

Without it, Claude Code doesn't know where to look for agent files, even if they exist in the agents/ directory.

Changes

  • ✅ Added "agents": "./agents/" to plugin.json
  • ✅ Bumped version to 1.1.4

What This Fixes

The trebuchet-expert agent should now:

  • ✅ Appear in the /agents list in Claude Code
  • ✅ Be automatically invoked when you ask Trebuchet-related questions
  • ✅ Have access to all configured tools (Read, Grep, Glob, Bash, Edit, Write)

Testing

After updating to v1.1.4:

  1. Run /plugin update trebuchet@briannadoubt
  2. Run /agents to verify the agent appears
  3. Ask a Trebuchet question to test automatic delegation

Full Changelog: v1.1.3...v1.1.4

v1.1.3 - Fix Agent Registration

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 11:12

Bug Fix

Fixed critical issue preventing the trebuchet-expert agent from registering with Claude Code.

Root Cause

The agent frontmatter contained an invalid skills field. Skills are separate components discovered from the skills/ directory and should NOT be referenced in agent frontmatter.

Changes

  • ✅ Removed invalid skills field
  • ✅ Removed model field (optional, may cause issues)
  • ✅ Converted tools to proper YAML array format
  • ✅ Added Edit and Write to agent tools

Valid Agent Frontmatter

Now using only valid fields per Claude Code documentation:

  • name - Agent identifier
  • description - When to invoke (required)
  • capabilities - Task list (required)
  • tools - Available tools (optional)

Testing

After updating, the agent should:

  • Appear in /agents list
  • Be automatically invoked for Trebuchet questions
  • Have access to all plugin skills automatically

Full Changelog: v1.1.2...v1.1.3

v1.1.2 - Fix Agent Registration

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 11:05

Bug Fixes

Fixed critical issues preventing the trebuchet-expert agent from registering properly with Claude Code.

Changes

  • Fixed agent structure: Agents must use flat structure , not subdirectories like
  • Added required field: Added field to agent frontmatter (required per Claude Code documentation)
  • Improved capabilities: Added comprehensive list of agent capabilities for better task delegation

What This Fixes

The agent should now properly:

  • Be discovered and registered by Claude Code when the plugin is installed
  • Appear in the agents list
  • Be automatically invoked when users ask Trebuchet-related questions
  • Have clear capabilities for Claude to understand when to delegate

Thanks

Thank you for catching the registration issue! The agent structure now follows the official Claude Code plugin documentation exactly.

Full Changelog: v1.1.0...v1.1.2

v1.1.0 - Updated CLI Documentation

Choose a tag to compare

@briannadoubt briannadoubt released this 27 Jan 10:58

What's New

  • Updated CLI skill documentation with latest features
  • Added Fly.io deployment support
  • Documented fully functional trebuchet dev command
  • Added generate server command documentation
  • Removed outdated --watch flag references
  • Updated provider options to aws/fly

Changes

  • CLI skill now accurately reflects actual implementation
  • Improved examples and output samples
  • Better PostgreSQL state configuration documentation

Full Changelog

Full Changelog: v1.0.0...v1.1.0