How to Get Support for bradautomates/claude-video: GitHub Issues and Enterprise Channels

To get support for bradautomates/claude-video, open a GitHub Issue for bug reports and usage questions, visit the author's YouTube channel for community discussion, or contact Solaris Automation for paid enterprise consulting.

The bradautomates/claude-video repository provides an open-source /watch skill that enables Claude to analyze videos via frame extraction and transcription. When you encounter installation errors, runtime failures, or need architectural guidance, understanding the correct support channels ensures you receive timely assistance. This guide covers every resource available—from community-driven GitHub Issues to commercial support—backed by the actual project structure and maintainer workflow.

Official Support Channels for bradautomates/claude-video

The project maintains distinct pathways depending on your needs, ranging from free community help to professional consulting.

GitHub Issues for Bug Reports and Feature Requests

For technical bugs, feature requests, and usage questions, navigate to the GitHub Issues page. This is the primary channel where the maintainer tracks problems and community contributions.

When opening an issue, reference the specific script that failed. For example, if skills/watch/scripts/watch.py crashes during execution, include the exact command you ran and the traceback. The maintainer monitors this board and typically responds to reproducible issues faster when they include environment details and logs.

YouTube Community for General Discussion

For general enquiries and tutorial-based questions, the author maintains the @bradbonanno YouTube channel, linked directly from the README.md. This channel hosts video walkthroughs where you can leave comments for clarifications on skill usage or installation nuances.

Solaris Automation for Enterprise Support

If you require commercial-grade support or consulting integration, contact Solaris Automation via solarisautomation.io. This is the author's company, which offers paid assistance for enterprise deployments, custom skill modifications, and production troubleshooting beyond the scope of community support.

Self-Service Troubleshooting Resources

Before engaging official channels, validate your environment using the built-in diagnostic tools included in the repository.

Pre-Flight Setup Validation

Run the setup.py pre-flight script to verify dependencies and scaffold your configuration. Located at skills/watch/scripts/setup.py, this script checks for required binaries including ffmpeg and yt-dlp, and validates API keys in your .env file.

python3 "skills/watch/scripts/setup.py" --check

If binaries are missing, the script outputs platform-specific installation commands (e.g., brew install ffmpeg yt-dlp on macOS). Errors printed to stderr here are the most common first-stop for support questions.

Test Suite Verification

Confirm your installation integrity by executing the pytest suite in the tests/ directory. A clean run proves that core modules—watch.py, download.py, frames.py, transcribe.py, and whisper.py—function correctly on your platform.

python3 -m pytest -q

If tests fail, capture the output and include it in your GitHub Issue. This diagnostic step eliminates environment-specific problems before requesting human assistance.

Documentation References

Consult these canonical files before submitting requests:

• README.md – Contains the complete installation guide, first-run instructions, and author contact links.
• SKILL.md (located at skills/watch/SKILL.md) – Defines the /watch slash-command contract and explains how scripts are located and executed across Agent Skills hosts.
• scripts/whisper.py – Pure-stdlib client for Groq and OpenAI Whisper APIs; useful for debugging transcription failures.

How to Submit an Effective Support Request

Following this workflow maximizes your chances of rapid resolution:

1. Validate your environment – Run python3 -m pytest -q and capture any failures.
2. Check pre-flight setup – Execute python3 "skills/watch/scripts/setup.py" --check to identify missing dependencies.
3. Search existing issues – Review open and closed GitHub Issues to see if your problem has already been solved.
4. Open a detailed GitHub Issue – Include:
   • Operating system and version
   • Exact command executed (e.g., python3 "skills/watch/scripts/watch.py" "<url>" --detail balanced)
   • Full traceback or error messages
   • Steps to reproduce
   • Host context (Claude Code, Codex, or other Agent Skills host)
5. Follow up promptly – Respond quickly to maintainer requests for additional logs or minimal reproducible examples.

Summary

• bradautomates/claude-video offers tiered support: GitHub Issues for technical problems, YouTube for community discussion, and Solaris Automation for enterprise consulting.
• Always run setup.py --check and pytest -q before opening issues to isolate environment problems.
• Reference SKILL.md for architectural questions and README.md for installation guidance.
• Include specific script paths (e.g., skills/watch/scripts/watch.py), error logs, and host context in all support requests.

Frequently Asked Questions

Where do I report bugs for bradautomates/claude-video?

Report bugs via the GitHub Issues page. Include the specific script that failed (such as watch.py or setup.py), your operating system, the exact command used, and the full error traceback. The maintainer triages issues here and coordinates fixes through the pull-request workflow.

How do I verify my installation before asking for help?

Run the pre-flight check with python3 "skills/watch/scripts/setup.py" --check to validate that ffmpeg, yt-dlp, and API keys are properly configured. Then execute python3 -m pytest -q to verify that the core scripts function correctly. Successful completion of both steps confirms your environment is properly set up.

Is commercial support available for claude-video?

Yes. For enterprise consulting or production support, contact Solaris Automation at solarisautomation.io. This is the author's company, which provides paid assistance for custom integrations, security audits, and dedicated troubleshooting beyond community support channels.

What information should I include in a GitHub issue?

Include your OS version, Python version, the exact command you executed (e.g., python3 "skills/watch/scripts/watch.py" "video.mp4" --detail balanced), the full error traceback, and whether you are using Claude Code, Codex, or another Agent Skills host. Mention if you have already run setup.py --check and the pytest suite, and provide their output if relevant.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}