opal-agent-builder

Generate Opal-ready agent specs from client requirements and validate fields.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nansen/nansen-cowork-plugins --skill opal-agent-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opal-agent-builder
Source: https://github.com/nansen/nansen-cowork-plugins/tree/main/nansen-agent-studio/skills/opal-agent-builder
Command: npx skills add https://github.com/nansen/nansen-cowork-plugins --skill opal-agent-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps engineering teams convert client requirements into production-ready Opal agent specs, providing a single source of truth for agent_id, name, version, and frontmatter constraints.

Core Features & Use Cases

  • Generates standardized agent definitions (specialized and workflow) from the project brief.
  • Validates required fields (name, agent_id, version, description) and parameter typing to ensure Opal compatibility.
  • Exports clean JSON in the format expected by Opal and supports documentation of dependencies and resources.

Quick Start

Provide a client brief and agent requirements, and I will generate a production-ready Opal agent spec ready for export.

Frequently Asked Questions about opal-agent-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create production-ready Opal agent specs from client requirements?

To create Opal agent specs, provide a client brief and development standards. The tool generates standardized definitions for specialized and workflow agents, complete with required frontmatter fields and parameter typing.

What fields are required when generating an Opal agent spec?

Required frontmatter fields for an Opal agent spec include name, agent_id, version, and description. The generation process also enforces parameter types such as string, number, boolean, and object to ensure Opal compatibility.

How do I validate Opal agent frontmatter and parameter types before export?

You validate Opal agent frontmatter by checking mandatory fields like name, agent_id, version, and description. The spec generator enforces parameter types (string, number, boolean, object) and preserves the _nansen block along with dependencies and components.

Can I generate both specialized and workflow agents for client projects?

Yes, you can generate both specialized and workflow agents across client projects. The process applies client requirements and development standards to produce standardized agent definitions ready for export.

How do I export Opal agent specs as clean JSON?

Exporting Opal agent specs produces clean JSON formatted exactly as expected by Opal. The exported spec documents dependencies, resources, and preserves the _nansen block for production readiness.

What is the best way to document changes and dependencies for Opal agents?

The best way to document changes and dependencies is through the generated spec itself. It preserves the _nansen block, records dependencies and components, and exports clean JSON to maintain a single source of truth.