Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Quality Control Provisions

ASecurity

Drafts Quality Control Provisions as an exhibit to a Trademark License Agreement, covering quality standards, inspection rights, sample approval, non-compliance remedies, and recall obligations. Use when drafting trademark license QC exhibits, brand standards compliance annexes, or IP licensing quality schedules. Protects licensor rights and prevents abandonment under the Lanham Act.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgoexpresstestinggitperformance

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill quality-control-provisions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quality Control Provisions?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Quality Control Provisions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-quality-control-provisions/badge)](https://www.skillsdirectory.com/skills/lev-os-quality-control-provisions)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: quality-control-provisions
description: Drafts Quality Control Provisions as an exhibit to a Trademark License Agreement, covering quality standards, inspection rights, sample approval, non-compliance remedies, and recall obligations. Use when drafting trademark license QC exhibits, brand standards compliance annexes, or IP licensing quality schedules. Protects licensor rights and prevents abandonment under the Lanham Act.
---

# Quality Control Provisions (Trademark License Exhibit)

Drafts an exhibit to a Trademark License Agreement establishing quality standards, monitoring procedures, and compliance obligations that preserve the licensor's trademark rights under the Lanham Act, 15 U.S.C. § 1127.

## Prerequisites

1. **Executed or draft Trademark License Agreement** — defined terms, exhibit numbering, territory, licensed marks, product categories
2. **Brand standards / style guide** — Pantone/CMYK values, approved mark forms, trademark designations (™ / ®)
3. **Approved pre-production samples** (if any) — definitive quality benchmark
4. **Applicable regulatory framework** — FDA, CPSC, FTC, or industry-specific standards
5. **Quality metrics** — material specs, durability requirements, performance criteria

## Quick Start

1. Gather prerequisites above and confirm exhibit numbering with the main agreement
2. Draft the seven sections below in order
3. Adapt regulatory and quality-metrics content to the specific product category
4. Cross-check all defined terms against the principal License Agreement
5. Verify exhibit does not conflict with main agreement remedies or termination provisions

## Document Header

| Element | Content |
|---------|---------|
| Exhibit designation | Next sequential letter/number per agreement structure |
| Title | "Quality Control Standards and Procedures" |
| Integration clause | Reference the Trademark License Agreement by date and parties; incorporate defined terms |

## Core Sections

### 1. Foundational Quality Standards

- Applies to all products, services, packaging, and materials bearing the licensed marks
- State compliance is a **material term** of the Agreement
- Quality floor: meet or exceed quality of licensor's comparable products under the same marks
- Reference approved pre-production samples as the definitive benchmark
- Licensee bears sole regulatory responsibility; must maintain all licenses/permits; must promptly notify licensor of any regulatory inquiry or enforcement action

Include applicable regulatory requirements (FDA, CPSC, FTC, environmental, industry-specific) and quality metrics covering materials, workmanship, durability, performance, and aesthetics.

### 2. Trademark Usage Standards

- Marks displayed only in approved forms per brand standards manual
- Proper designations: ™ for common law, ® for registered
- No alteration without prior written consent

Prohibited uses: connection with unlawful/objectionable content, comparative advertising, registration of marks or confusingly similar variations, use in corporate/domain names without authorization, unauthorized sublicensing. All advertising and packaging require the same approval process as product samples.

### 3. Sample Submission & Approval

**Scope:** all items before production, distribution, or commercial use — finished products, packaging, labels, advertising/promotional materials, POS displays.

| Parameter | Standard |
|-----------|----------|
| Format | Physical samples (3 per variation) and/or high-res digital |
| Lead time | 30–60 days before production/launch |
| Review period | 15–30 business days from complete submission |
| Approval form | Written only; oral approvals insufficient |

Outcomes: Approve (may be conditional) · Request revisions · Reject. Approval does not waive inspection rights, is revocable if production materially differs, and both parties retain approved samples as the quality standard.

### 4. Inspection & Monitoring Rights

- Licensor may inspect licensee facilities on **5–10 business days' notice** (immediate access for suspected material violations or safety concerns)
- Access to personnel, QC records, production logs, testing results
- Random sampling at no charge for lab/performance/safety testing
- Compliant inspection costs: licensor. Non-compliant inspection costs: licensee
- Licensee must maintain documented QC procedures, designate a QC officer, and submit periodic quality reports

### 5. Non-Compliance & Remediation

**Graduated cure periods:**

| Severity | Cure Period | Examples |
|----------|-------------|----------|
| Minor | 15–30 days | Cosmetic deviations, minor labeling errors |
| Serious | 5–10 days | Material quality shortfall, unapproved mark usage |
| Critical | Immediate; no cure | Safety defects, regulatory violations |

Adequate cure requires: corrective action plan approved by licensor, cessation of non-conforming production, destruction or rework of non-conforming inventory (documented), enhanced QC procedures, and new samples demonstrating correction.

Failure to cure triggers cumulative remedies: suspension, termination, monetary damages, injunctive relief.

### 6. Product Recall & Market Withdrawal

- Licensor may require immediate cessation and recall in its sole discretion
- Licensee obligations: notify distributors/retailers, consumer notification per licensor direction, establish return/refund process, retrieve and destroy recalled products (certified)
- **All recall costs borne exclusively by Licensee**
- Licensee indemnifies licensor from all claims arising from non-conforming products, quality deficiencies, regulatory violations, recalls, or breach of these provisions (survives termination)

### 7. Licensee Acknowledgments

Licensee expressly acknowledges:
1. Quality control is essential to trademark validity under federal and state law
2. Failure to control may result in trademark abandonment
3. These provisions are **material terms**; material breach entitles licensor to immediate termination
4. All goodwill vests exclusively in licensor
5. Licensee will not challenge mark validity or claim ownership
6. Upon termination, licensee retains no rights in marks or associated goodwill

## Drafting Conventions

- "shall" for obligations, "may" for discretionary rights, "will" for future events
- Match defined terms exactly to the principal License Agreement; define new terms on first use
- Use numbered sections/subsections; avoid vague cross-references ("above," "herein")
- Incorporate industry standards (ISO, ASTM) by reference where applicable
- Include specific Pantone/CMYK values from brand guidelines where available

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →