@intentsolutionsio/youtube-strategy 1.0.0

package/skills/yt-brief/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: yt-brief
+description: |
+  Refine a YouTube video idea into a structured production brief with angle, key points, value proposition,
+  CTA asset, and audience segment. Use this skill whenever the user says "create a brief", "brief this idea",
+  "develop this idea", "write a video brief", "production brief", or has selected a video idea from ideation
+  and wants to define the angle and structure before packaging and outlining. Use when working with yt brief. Trigger with 'yt', 'brief'.
+allowed-tools: WebSearch, Read, Write
+version: 1.0.0
+author: Claude Code Plugins <plugins@claudecodeplugins.io>
+license: MIT
+compatible-with: claude-code, codex, openclaw
+tags: [productivity, yt-brief]
+---
+# YouTube Brief
+
+You are creating a structured production brief for a YouTube video. The brief is the bridge between an idea and a filmable video - it defines what the video IS.
+
+## Before You Start
+
+You need from the user:
+
+1. **The video idea** - Either a validated idea from `/yt-ideate` (with title, tier, type, angle) or a raw idea the user wants to develop
+2. **Any constraints** - Timeline, specific features to include/exclude, target length, team capacity
+
+If the user is coming from the ideation flow, load `validated_ideas.json` for the full context on the selected idea.
+
+## The Briefing Process
+
+### Step 1: Research the Topic
+
+Before writing the brief, understand the topic deeply:
+- What does this feature/tool actually do? (Use WebSearch if needed)
+- What are the common pain points or confusion points?
+- What existing content exists? What angle would differentiate this video?
+- What's the practical value for the target audience?
+
+### Step 2: Define the Video Identity
+
+Work with the user to lock in:
+
+**Content Type & Tier:**
+- Confirm which tier and category this falls under
+- This determines the format, length, and production approach
+
+**The Angle:**
+- What's the unique take? Why would someone click THIS video over alternatives?
+- The angle should be specific and defensible, not generic
+- Good: "How to use MCP integrations to automate your marketing reporting without any code"
+- Bad: "MCP tutorial"
+
+**Target Audience Segment:**
+- Who is the primary viewer?
+- What's their starting knowledge level for this topic?
+
+### Step 3: Write the Brief
+
+The brief must include:
+
+1. **Title (working)** - Will be refined in packaging, but needs a clear working title
+2. **Content tier & type** - e.g., Tier 1 / Feature Tutorial
+3. **The angle** - 1-2 sentences: what makes this video unique
+4. **Target audience** - Who exactly is this for, and what do they already know
+5. **Key points** - 5-8 main things the viewer will learn or see demonstrated
+6. **Value proposition** - After watching, the viewer will be able to [specific outcome]
+7. **CTA asset** - What free asset can be given away? (template, skill, workflow, plugin)
+8. **Prerequisites** - What does the viewer need to have set up before watching?
+9. **Demo requirements** - What tools, accounts, or setups are needed for filming?
+10. **Estimated length** - Target duration based on content type
+11. **Urgency/timing** - Is this time-sensitive (update video) or evergreen?
+
+### Step 4: Review with User
+
+Present the complete brief and ask:
+
+"Here's the brief for '[title]'. Review it:"
+
+```
+[Full brief in clean markdown format]
+```
+
+"What would you like to adjust?"
+- Approve - move to packaging
+- Adjust the angle
+- Add/remove key points
+- Change the CTA asset
+- Change the target audience
+- Start over with a different approach
+
+**This is a mandatory human checkpoint. Do NOT proceed without approval.**
+
+### Step 5: Save the Brief
+
+Save the approved brief as `video-brief-yt-brief.md` in the working directory.
+
+## Key Principles
+
+- **The angle is everything.** A brief without a clear, differentiated angle will produce a generic video. Push the user to be specific.
+- **Practical value first.** Every key point should contribute to the viewer being able to DO something. No filler sections.
+- **CTA integration.** The CTA asset should feel like a natural extension of the video content, not a bolted-on pitch.
+- **Honest about scope.** If a topic is too big for one video, say so and suggest splitting it. Don't try to cram a Full Tutorial into a Feature Tutorial.
+- **Team-ready.** The brief should contain enough detail that a team member could start demo prep without asking follow-up questions.
+
+## Overview
+
+Refine a YouTube video idea into a structured production brief with angle, key points, value proposition, CTA asset, and audience segment.
+
+## Prerequisites
+
+- Access to the Yt Brief environment or API
+- Required CLI tools installed and authenticated
+- Familiarity with Yt Brief concepts and terminology
+
+## Instructions
+
+1. Assess the current state of the Yt Brief configuration
+2. Identify the specific requirements and constraints
+3. Apply the recommended patterns from this skill
+4. Validate the changes against expected behavior
+5. Document the configuration for team reference
+
+## Output
+
+- Configuration files or code changes applied to the project
+- Validation report confirming correct implementation
+- Summary of changes made and their rationale
+
+## Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Yt Brief |
+| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
+| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
+
+## Examples
+
+**Basic usage**: Apply yt brief to a standard project setup with default configuration options.
+
+**Advanced scenario**: Customize yt brief for production environments with multiple constraints and team-specific requirements.
+
+## Resources
+
+- Official Yt Brief documentation
+- Community best practices and patterns
+- Related skills in this plugin pack

package/skills/yt-ideation/SKILL.md

@@ -0,0 +1,168 @@
+---
+name: yt-ideation
+description: |
+  Generate and validate YouTube video ideas aligned with content pillars, audience strategy,
+  and priority tiers. Use this skill whenever the user says "generate ideas", "brainstorm videos",
+  "what should I make next", "video ideas", "content ideas", "ideation", "what topics should I cover",
+  or wants to come up with new video concepts. Use when working with yt ideation. Trigger with 'yt', 'ideation'.
+allowed-tools: WebSearch, Read, Write, Task
+version: 1.0.0
+author: Claude Code Plugins <plugins@claudecodeplugins.io>
+license: MIT
+compatible-with: claude-code, codex, openclaw
+tags: [productivity, yt-ideation]
+---
+# YouTube Ideation
+
+You are generating and validating video ideas for a YouTube channel. Every idea must align with the content strategy and serve the target audience.
+
+## Before You Start
+
+You need from the user:
+
+1. **Focus area** - What tool, niche, or topic to ideate around (e.g., "AI tools for professionals", "recent software updates", "productivity workflows")
+2. **Research data** (optional) - If `/yt-research` was run first, load `niche-analysis.json` and `niche-report.md` for data-informed ideation
+3. **Constraints** (optional) - Any specific requirements (e.g., "only short videos", "needs to be filmable this week", "must tie to a product launch")
+
+If the user provided focus already, confirm and proceed.
+
+## The Ideation Process
+
+### Step 1: Load Context
+
+Understand the creator's:
+- **Content pillars** - What core topics does the channel focus on?
+- **Audience** - Who are the viewers? What's their skill level?
+- **Content types** - What formats work best? (tutorials, reviews, updates, comparisons)
+- **Trending vs evergreen** - What's the balance between timely and long-lasting content?
+
+### Step 2: Generate 15-20 Raw Ideas
+
+Use these ideation methods:
+
+**Method 1: Gap Analysis** (if research data available)
+- Content gaps from competitor analysis
+- Topics with high demand but low competition
+- Complex concepts that need accessible translation
+
+**Method 2: Trend Riding**
+- Recent tool updates or feature launches
+- Industry developments relevant to the audience
+- Viral topics that can be made practical
+
+**Method 3: Format Innovation**
+- Existing topics in new formats (comparison, mega-guide, use-case compilation)
+- Content types competitors aren't using
+- Series potential (multi-part tutorials)
+
+**Method 4: Audience Needs**
+- Questions the audience is asking (Reddit, YouTube comments, community)
+- Problems viewers face with the tools they use
+- "How do I..." queries for the niche
+
+For each idea, define:
+- **Working title**
+- **Content tier** (Tier 1: growth content, Tier 2: supporting content)
+- **Content type** (Full Tutorial, Feature Tutorial, Update Video, Use Case Video, Comparison, etc.)
+- **One-line angle** (what makes this video unique)
+- **Timeliness** (trending/urgent or evergreen)
+
+**Priority distribution:**
+- 60-70% Tier 1 ideas (the growth engine)
+- 30-40% Tier 2 ideas (supporting content)
+
+### Step 3: Quick Self-Filter
+
+Before validation, run each idea through a strategy test:
+- Does it serve the target audience? (Must be yes)
+- Can it be practically demonstrated? (Prefer yes)
+- Does it support the content funnel? (Can we give away an asset?)
+- Is it filmable in the current format?
+
+Remove ideas that fail the test. Note why for transparency.
+
+### Step 4: Validate Ideas
+
+Spawn `idea-validator` sub-agents (5 ideas per agent) to assess:
+- Search demand (YouTube autocomplete, Google Trends, forums)
+- Competition level (existing videos, quality bar)
+- Trend direction (rising, stable, declining)
+- Audience fit (accessibility, practical value)
+
+Each sub-agent returns an opportunity score (1-10) per idea.
+
+### Step 5: Present Ranked Results
+
+Present ideas to the user sorted by opportunity score:
+
+```markdown
+Here are your validated video ideas, ranked by opportunity:
+
+| # | Title | Tier | Type | Demand | Competition | Score |
+|---|-------|------|------|--------|-------------|-------|
+| 1 | [title] | Tier 1 | Feature Tutorial | High | Low | 9.2 |
+| 2 | [title] | Tier 1 | Update Video | High | Medium | 8.5 |
+...
+
+Top recommendation: [title] - [1 sentence why]
+
+Which ideas do you want to develop into briefs?
+```
+
+Options:
+- Pick 1-3 ideas to brief
+- Generate more ideas in a different direction
+- Refine a specific idea before briefing
+- Go back to research
+
+## Key Principles
+
+- **Tier 1 first** - Always prioritize growth content (tutorials, use cases, updates). These drive channel growth.
+- **Audience-appropriate** - Every idea must pass the "would the target viewer find this useful?" test.
+- **Practical over theoretical** - Favor ideas where the viewer walks away with something they can DO.
+- **CTA-ready** - Strong ideas include a natural asset giveaway (template, workflow, plugin) that ties to the creator's business.
+- **Data-informed** - When research data is available, use it. Gut-feel ideation is a fallback, not the default.
+
+## Overview
+
+Generate and validate YouTube video ideas aligned with content pillars, audience strategy, and priority tiers.
+
+## Prerequisites
+
+- Access to the ORM environment or API
+- Required CLI tools installed and authenticated
+- Familiarity with ORM concepts and terminology
+
+## Instructions
+
+1. Assess the current state of the ORM configuration
+2. Identify the specific requirements and constraints
+3. Apply the recommended patterns from this skill
+4. Validate the changes against expected behavior
+5. Document the configuration for team reference
+
+## Output
+
+- Configuration files or code changes applied to the project
+- Validation report confirming correct implementation
+- Summary of changes made and their rationale
+
+## Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with ORM |
+| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
+| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
+
+## Examples
+
+**Basic usage**: Apply yt ideation to a standard project setup with default configuration options.
+
+**Advanced scenario**: Customize yt ideation for production environments with multiple constraints and team-specific requirements.
+
+## Resources
+
+- Official ORM documentation
+- Community best practices and patterns
+- Related skills in this plugin pack

package/skills/yt-outline/SKILL.md

@@ -0,0 +1,187 @@
+---
+name: yt-outline
+description: |
+  Build detailed step-by-step YouTube video outlines with demo prep, screen-share sequences, and visual
+  planning. Use this skill whenever the user says "create an outline", "outline this video", "video outline",
+  "build the outline", "production outline", or has an approved brief and packaging and needs the final
+  pre-production document before demo prep and filming. Use when working with yt outline. Trigger with 'yt', 'outline'.
+allowed-tools: WebSearch, Read, Write
+version: 1.0.0
+author: Claude Code Plugins <plugins@claudecodeplugins.io>
+license: MIT
+compatible-with: claude-code, codex, openclaw
+tags: [productivity, yt-outline]
+---
+# YouTube Outline
+
+You are creating a detailed production outline for a YouTube video. The outline is the final pre-production artifact - it specifies exactly what to show, what to say, and what demos to run, and tells the team exactly what to prepare.
+
+## Before You Start
+
+You need:
+
+1. **The approved brief** - Load `video-brief-yt-outline.md` from the working directory
+2. **The approved packaging** - Load `packaging-yt-outline.md` for the final title and thumbnail direction
+3. **Topic research** (optional) - If the topic requires technical accuracy, use WebSearch to verify specific feature details, steps, or capabilities
+
+## The Outline Process
+
+### Step 1: Research the Topic in Depth
+
+Before writing the outline, deeply understand the feature/tool being demonstrated:
+- Verify all steps work as expected (use WebSearch to check documentation)
+- Identify potential gotchas or failure points
+- Note any prerequisites the viewer needs
+- Find the shortest path to the value proposition (minimize setup time in the video)
+
+### Step 2: Define the Video Structure
+
+Based on the content type from the brief, choose the appropriate structure:
+
+**For Feature Tutorials (15-30 min):**
+1. Hook (30-60 sec) - What they'll be able to do by the end
+2. Context (1-2 min) - Why this matters, brief overview
+3. Core demonstration (10-20 min) - Step-by-step walkthrough
+4. Advanced tips (2-3 min) - Power user moves
+5. CTA + wrap (1-2 min) - Asset giveaway, community mention
+
+**For Update Videos (10-20 min):**
+1. Hook (30 sec) - What just changed
+2. Overview (1-2 min) - What the update includes
+3. Walkthrough (8-15 min) - Demo each new feature
+4. Impact (1-2 min) - What this means for you
+5. CTA + wrap (1 min) - Asset giveaway
+
+**For Use Case Videos (15-30 min):**
+1. Hook (30-60 sec) - The impressive outcome
+2. Problem (1-2 min) - What manual process this replaces
+3. Solution overview (1-2 min) - High-level workflow
+4. Step-by-step build (10-20 min) - Building the workflow live
+5. Results (2-3 min) - Actual metrics and outcomes
+6. CTA + wrap (1-2 min) - Asset giveaway
+
+**For Full Tutorials (30-90+ min):**
+1. Hook (1-2 min) - What they'll know by the end
+2. Overview/roadmap (2-3 min) - What the tutorial covers
+3. Setup (5-10 min) - Getting started from scratch
+4. Core sections (20-60 min) - Organized by feature/capability
+5. Advanced section (5-10 min) - Power user techniques
+6. Summary + next steps (2-3 min) - Recap + what to learn next
+7. CTA (1-2 min) - Asset giveaway
+
+### Step 3: Write the Detailed Outline
+
+For each section, specify:
+
+**Talking points:**
+- Key message for this section (not a script - bullet points)
+- Transition from previous section
+- Any specific phrases or analogies to use
+
+**What's on screen:**
+- Screen-share of what tool/feature
+- Specific actions to perform (click here, type this, navigate there)
+- Any diagrams, slides, or supporting visuals
+
+**Demo sequence:**
+- Exact steps to demonstrate
+- Expected outcome the viewer should see
+- What to do if something goes wrong (backup plan)
+
+**Timing:**
+- Target duration for this section
+- Running total to stay within target video length
+
+### Step 4: Create Demo Prep Checklist
+
+For each demo in the outline, specify what the team needs to prepare:
+- Accounts and tools to have logged in
+- Sample data or projects to have ready
+- Environment settings (clean workspace, no notifications, etc.)
+- Backup plans (what if the live demo fails?)
+
+### Step 5: Present and Review
+
+Present the outline to the user:
+
+```markdown
+## Video Outline: [Title]
+
+Total estimated length: [X] minutes
+
+[Full section-by-section outline]
+```
+
+Also present the demo prep checklist separately:
+
+```markdown
+## Demo Prep Checklist: [Title]
+
+[Full checklist organized by demo sequence]
+```
+
+"Here's the outline and demo prep list. The team can start preparing."
+- Approve and start prep
+- Adjust section order
+- Add/remove sections
+- Change demo approach
+- Need more detail on a specific section
+
+### Step 6: Save
+
+Save two files:
+- `video-outline-yt-outline.md` - The full outline
+- `demo-prep-checklist-yt-outline.md` - The team's preparation checklist
+
+## Key Principles
+
+- **Show, don't tell.** Every section should have something on screen. Minimize talking-head time. The value is in the demonstration.
+- **Shortest path to value.** Get to the first "wow" moment as fast as possible. Front-load the payoff, then go deeper.
+- **Direct and practical.** The outline should reflect a direct, no-fluff style. No "in this section we'll cover..." filler. Just do the thing.
+- **Team-ready.** The demo prep checklist should be detailed enough that a team member can prepare everything without asking questions.
+- **Timing is real.** Be honest about section durations. A 20-minute video with 25 minutes of outline is a problem. Cut or restructure.
+- **Failure-proofed.** For every live demo, include a backup plan. If the API call times out, if the feature bugs out - what's the fallback?
+
+## Overview
+
+Build detailed step-by-step YouTube video outlines with demo prep, screen-share sequences, and visual planning.
+
+## Prerequisites
+
+- Access to the Yt Outline environment or API
+- Required CLI tools installed and authenticated
+- Familiarity with Yt Outline concepts and terminology
+
+## Instructions
+
+1. Assess the current state of the Yt Outline configuration
+2. Identify the specific requirements and constraints
+3. Apply the recommended patterns from this skill
+4. Validate the changes against expected behavior
+5. Document the configuration for team reference
+
+## Output
+
+- Configuration files or code changes applied to the project
+- Validation report confirming correct implementation
+- Summary of changes made and their rationale
+
+## Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Yt Outline |
+| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
+| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
+
+## Examples
+
+**Basic usage**: Apply yt outline to a standard project setup with default configuration options.
+
+**Advanced scenario**: Customize yt outline for production environments with multiple constraints and team-specific requirements.
+
+## Resources
+
+- Official Yt Outline documentation
+- Community best practices and patterns
+- Related skills in this plugin pack

package/skills/yt-packaging/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: yt-packaging
+description: |
+  Create optimized YouTube titles and thumbnail concepts for maximum CTR. Use this skill whenever the user
+  says "title ideas", "thumbnail concepts", "package this video", "CTR optimization", "title options", "packaging",
+  or has an approved brief and needs to finalize the title and thumbnail direction before outlining. Packaging
+  determines whether viewers click. Use when working with yt packaging. Trigger with 'yt', 'packaging'.
+allowed-tools: WebSearch, Read, Write
+version: 1.0.0
+author: Claude Code Plugins <plugins@claudecodeplugins.io>
+license: MIT
+compatible-with: claude-code, codex, openclaw
+tags: [productivity, yt-packaging]
+---
+# YouTube Packaging
+
+You are creating the title and thumbnail concept for a YouTube video. Packaging is where CTR is determined - the title and thumbnail are the single biggest factor in whether a video succeeds.
+
+## Before You Start
+
+You need from the user:
+
+1. **The approved brief** - Either load `video-brief-yt-packaging.md` from the working directory or get the brief details from the user
+2. **Timing context** - Is this a trending/update video (speed matters) or evergreen (optimize for long-term search)?
+3. **Competitive context** - What titles are competitors using for similar content? (Use WebSearch if not already known)
+
+## The Packaging Process
+
+### Step 1: Competitive Title Analysis
+
+Before writing titles, research what's already out there:
+- Search YouTube for the topic
+- Note the top 5-10 existing titles
+- Identify patterns: what words/structures appear in high-view videos?
+- Identify gaps: what angle is NO ONE using?
+
+### Step 2: Generate Title Options
+
+Create 5-10 title options across different strategies:
+
+**Strategy A: Direct Benefit**
+Focus on what the viewer will be able to DO.
+- "How to [Verb] [Tool] to [Outcome]"
+- "Build [Thing] with [Tool] in [Time]"
+
+**Strategy B: Curiosity Gap**
+Create intrigue without being misleading.
+- "The [Tool] Feature Nobody Is Talking About"
+- "I Automated My Entire [Process] - Here's How"
+
+**Strategy C: Authority/Definitive**
+Position as THE resource.
+- "The Complete [Tool] Guide for [Year]"
+- "Everything You Need to Know About [Feature]"
+
+**Strategy D: Trending/Urgency**
+For update videos and time-sensitive content.
+- "[Tool] Just Changed Everything - Here's What You Need to Know"
+- "New [Feature] Walkthrough: [Specific Capability]"
+
+**For each title:**
+- Note which strategy it uses
+- Estimate search-friendliness (contains searchable keywords?)
+- Estimate curiosity factor (would you click?)
+- Note the character count (aim for under 60 characters for full display)
+
+### Step 3: Generate Thumbnail Concepts
+
+Create 3-5 thumbnail concepts. Each concept should include:
+
+**Visual description:**
+- Main visual element (screen-share preview, tool logo, face expression, graphic)
+- Text overlay (1-4 words MAX - the thumbnail is not the title)
+- Color scheme and contrast
+- Layout (rule of thirds, focal point)
+
+**For each concept:**
+- How does it complement the title? (Title + thumbnail = one message, not two separate messages)
+- Does it stand out in a feed of similar videos?
+- Is it readable at mobile size (small thumbnail)?
+- Does it communicate the value proposition visually?
+
+### Step 4: A/B Test Variants
+
+For the top 2-3 title + thumbnail combos, suggest A/B testing variants:
+- Same title, different thumbnail approach
+- Same thumbnail, different title strategy
+- Small tweaks (word swaps, number inclusion)
+
+### Step 5: Present to User
+
+Present all options in a structured format:
+
+```markdown
+## Title Options
+
+| # | Title | Strategy | Keywords | Length |
+|---|-------|----------|----------|--------|
+| 1 | [title] | Direct Benefit | [keywords] | 48 chars |
+| 2 | [title] | Curiosity Gap | [keywords] | 52 chars |
+...
+
+## Thumbnail Concepts
+
+### Concept A: [Name]
+- Visual: [description]
+- Text overlay: "[text]"
+- Complements titles: #1, #3
+
+### Concept B: [Name]
+- Visual: [description]
+- Text overlay: "[text]"
+- Complements titles: #2, #4
+
+## Recommended Combo
+
+Title #[X] + Thumbnail Concept [Y] because [reasoning]
+```
+
+"Pick your title and thumbnail direction."
+- Go with recommended combo
+- Mix and match (pick different title + thumbnail)
+- Request more options
+- Adjust the angle
+
+**This is a mandatory human checkpoint.**
+
+### Step 6: Save
+
+Save the approved packaging as `packaging-yt-packaging.md`.
+
+## Key Principles
+
+- **Title and thumbnail are ONE system.** They must work together. The thumbnail should NOT repeat the title - they should complement each other. Title says what, thumbnail shows the emotion/intrigue.
+- **No clickbait without substance.** Titles should be compelling but honest. Every promise in the title must be delivered in the video.
+- **Search + browse balance.** For evergreen content, include searchable keywords. For trending content, prioritize curiosity and urgency.
+- **Mobile-first thumbnails.** Most YouTube browsing happens on mobile. Thumbnails must be readable at small sizes.
+- **Under 60 characters.** Titles get truncated on mobile. The most important words should be in the first 40 characters.
+
+## Overview
+
+Create optimized YouTube titles and thumbnail concepts for maximum CTR.
+
+## Prerequisites
+
+- Access to the optimization environment or API
+- Required CLI tools installed and authenticated
+- Familiarity with optimization concepts and terminology
+
+## Instructions
+
+1. Assess the current state of the optimization configuration
+2. Identify the specific requirements and constraints
+3. Apply the recommended patterns from this skill
+4. Validate the changes against expected behavior
+5. Document the configuration for team reference
+
+## Output
+
+- Configuration files or code changes applied to the project
+- Validation report confirming correct implementation
+- Summary of changes made and their rationale
+
+## Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with optimization |
+| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
+| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
+
+## Examples
+
+**Basic usage**: Apply yt packaging to a standard project setup with default configuration options.
+
+**Advanced scenario**: Customize yt packaging for production environments with multiple constraints and team-specific requirements.
+
+## Resources
+
+- Official optimization documentation
+- Community best practices and patterns
+- Related skills in this plugin pack