build-brand-rights-agent

Manage brand licensing and approve creatives via API-compliant handlers.

18|15|Updated Aug 20, 2025
One-click install
npx skills add https://github.com/adcontextprotocol/adcp-client --skill build-brand-rights-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-brand-rights-agent
Source: https://github.com/adcontextprotocol/adcp-client/tree/main/skills/build-brand-rights-agent
Command: npx skills add https://github.com/adcontextprotocol/adcp-client --skill build-brand-rights-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps brands centrally manage identity, licensable usage rights, and approval workflows for generated or submitted creatives, ensuring brand guidelines and license terms are consistently enforced across distributed advertising operations.

Core Features & Use Cases

  • Capabilities registration: Declare AdCP major versions and supported 'brand' protocol.
  • Brand identity: Serve brand metadata including names, logos, and guidelines URL.
  • Rights catalog and transactions: List licensable rights, pricing options, acquire and update rights grants with required identifiers.
  • Creative approval workflow: Accept creative submissions and return a decision of approved, rejected, or review with feedback and associated rights_grant_id.
  • Use Case: A buyer discovers a brand, purchases a license for AI-generated imagery, submits a generated creative, and the agent validates it against guidelines, auto-approves or routes for human review, and echoes correlation context for orchestration.

Quick Start

Build a Brand Rights Agent that registers capabilities, exposes get_brand_identity, get_rights, acquire_rights, update_rights, and creative_approval handlers, echoes opaque context in every response, and enforces brand guidelines during approvals.

Frequently Asked Questions about build-brand-rights-agent

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

FAQPage Schema
How do I manage brand licensing and approve submitted creatives for advertising assets?

Brand rights management involves serving brand metadata, listing licensable rights, and processing creative approval workflows. An agent exposes API handlers to acquire rights, validate submitted creatives against guidelines, and return approved, rejected, or review decisions with correlation context.

What is the AdCP protocol for brand identity and rights management?

The AdCP protocol enables brand platforms and ad servers to publish identity metadata, declare licensable usage rights, and process creative approvals. It uses major version capabilities registration and requires echoing opaque context in every response.

How does creative approval workflow work for AI-generated advertising assets?

The creative approval workflow accepts submissions, validates them against brand guidelines, and returns approved, rejected, or review decisions with feedback and an associated rights_grant_id. This ensures AI-generated or user-submitted assets comply with brand standards before publishing.

Can I sell or grant usage licenses for brand assets through an automated agent?

Yes, you can sell or grant usage licenses by implementing get_rights and acquire_rights handlers. These list available licensable rights with pricing options and process acquisition requests using required identifiers, enabling automated license transactions for advertising operations.

Do I need dependencies to build a brand rights agent for ad servers?

No external dependencies are required. You build the agent with API-compliant tool handlers for capabilities registration, brand identity, rights transactions, and creative approval, using empty input schemas with taskToolResponse wrappers for orchestration.

What are the limitations of using empty input schemas for rights management handlers?

Empty input schemas with taskToolResponse wrappers require all context and parameters to be managed through opaque context echoing rather than structured inputs. This design supports orchestration correlation but limits direct parameter validation at the schema level for rights and approval handlers.