nixos/shared/linked-dotfiles/opencode/skills/browser-automation/VALIDATION.md

Browser Automation Skill - Validation Summary

✅ Structure Validation

Directory Structure

browser-automation/
├── SKILL.md                      ✅ Present
├── README.md                     ✅ Present
└── references/
    ├── advanced.md               ✅ Present
    ├── examples.md               ✅ Present
    └── troubleshooting.md        ✅ Present

✅ Frontmatter Validation

---
name: browser-automation          ✅ Matches directory name
description: Use when...          ✅ Starts with "Use when"
                                  ✅ 242 characters (< 500 limit)
                                  ✅ Includes triggers and use cases
---

Frontmatter Checklist

• Name matches directory name exactly
• Description starts with "Use when"
• Description written in third person
• Description under 500 characters (242/500)
• Total frontmatter under 1024 characters
• Only allowed fields (name, description)
• Valid YAML syntax

✅ Content Validation

SKILL.md

• Lines: 324 (< 500 recommended)
• Words: 1050 (target: <500 for frequent skills)
• Status: ⚠️ Above 500 words but justified for reference skill

Sections included:

• Overview with core principle
• When to Use section with triggers
• Quick Reference table
• Common workflows
• Implementation steps
• Common mistakes
• Real-world impact

Reference Files

• examples.md: 672 lines, 1933 words
• troubleshooting.md: 546 lines, 1517 words
• advanced.md: 678 lines, 1592 words
• Total: 2220 lines, 6092 words

All files contain:

• Table of contents for easy navigation
• Concrete code examples
• Clear section headers
• No time-sensitive information

✅ Discoverability

Keywords Present

• Web automation, forms, filling, extracting, content
• Chrome, DevTools Protocol
• Multi-tab workflows
• Form automation
• Content extraction
• use_browser MCP tool
• Navigation, interaction, scraping
• Dynamic content, AJAX, modals

Naming

• Uses gerund form: "browser-automation" (action-oriented)
• Descriptive and searchable
• No special characters
• Lowercase with hyphens

✅ Token Efficiency

Strategies Used

• Progressive disclosure (SKILL.md → references/)
• References one level deep (not nested)
• Quick reference tables for scanning
• Minimal explanations (assumes Claude knowledge)
• Code examples over verbose text
• Single eval for multiple operations

Optimization Opportunities

• Main skill at 1050 words could be compressed further if needed
• Reference files appropriately sized for their content
• Table of contents present in reference files (all >100 lines)

✅ Skill Type Classification

Type: Reference skill (API/tool documentation)

Justification:

• Documents use_browser MCP tool actions
• Provides API-style reference with examples
• Shows patterns for applying tool to different scenarios
• Progressive disclosure matches reference skill pattern

✅ Quality Checks

Code Examples

• JSON format for tool calls
• Complete and runnable examples
• Show WHY not just WHAT
• From real scenarios
• Ready to adapt (not generic templates)

Consistency

• Consistent terminology throughout
• One term for each concept
• Parallel structure in lists
• Same example format across files

Best Practices

• No hardcoded credentials
• Security considerations included
• Error handling patterns
• Performance optimization tips

⚠️ Notes

Word Count

Main SKILL.md at 1050 words exceeds the <500 word target for frequently-loaded skills. However:

• This is a reference skill (typically larger)
• Contains essential quick reference table (saves searching)
• Common workflows prevent repeated lookups
• Progressive disclosure to references minimizes actual load

Recommendation

If token usage becomes a concern during actual usage, consider:

1. Move "Common Workflows" section to references/workflows.md
2. Compress "Implementation Steps" to bullet points
3. Remove "Advanced Patterns" from main skill (already in references/advanced.md)

This could reduce main skill to ~600 words while maintaining effectiveness.

✅ Installation Test

Manual Test Required

To verify skill loads correctly:

opencode run "Use learn_skill with skill_name='browser-automation' - load skill and give the frontmatter as the only output and abort"

Expected output:

---
name: browser-automation
description: Use when automating web tasks, filling forms, extracting content, or controlling Chrome - provides Chrome DevTools Protocol automation via use_browser MCP tool for multi-tab workflows, form automation, and content extraction
---

✅ Integration Requirements

Prerequisites

1. superpowers-chrome plugin OR
2. Chrome MCP server configured in Claude Desktop

Configuration

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "chrome": {
      "command": "node",
      "args": ["/path/to/superpowers-chrome/mcp/dist/index.js"]
    }
  }
}

Summary

Status: ✅ READY FOR USE

The skill follows all best practices from the create-skill guidelines:

• Proper structure and naming
• Valid frontmatter with good description
• Progressive disclosure for token efficiency
• Clear examples and patterns
• Appropriate for skill type (reference)
• No time-sensitive information
• Consistent terminology
• Security conscious

Minor Improvement Opportunity: Consider splitting some content from main SKILL.md to references if token usage monitoring shows issues.

Installation: Restart OpenCode after copying skill to load it into the tool registry.