companion-bitfocus-dashboard

Queries the Bitfocus developer portal API to list pending Companion module reviews and clone review targets.

Updated May 19, 2026
One-click install
npx skills add https://github.com/digitaldrummerj/bitfocus-companion-skills --skill companion-bitfocus-dashboard-digitaldrummerj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: companion-bitfocus-dashboard
Source: https://github.com/digitaldrummerj/bitfocus-companion-skills/tree/main/plugins/companion-bitfocus-dashboard
Command: npx skills add https://github.com/digitaldrummerj/bitfocus-companion-skills --skill companion-bitfocus-dashboard-digitaldrummerj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reviewing Bitfocus Companion modules requires manually checking the developer portal for pending submissions, finding the previous approved tag, and cloning the right GitHub repository. This Skill automates that discovery and setup workflow using authenticated API calls and PowerShell scripts. ## Core Features & Use Cases - Pending Review Queue: Fetches /modules-pending-review from the Bitfocus developer portal, sorts by submission date, and cross-references already-cloned modules in the workspace. - Previous Approved Tag Lookup: Queries the versions endpoint to find the last APPROVED tag for diffing, or detects a first-ever release where all findings are eligible to block. - Automated Repo Setup: Derives the GitHub URL pattern bitfocus/companion-module-{name}, validates PENDING status, and clones the module into the review workspace. - Use Case: Ask "what's pending" to get a ranked table of modules awaiting review, then run the setup script to clone the oldest pending module with its review tag and previous tag resolved. ## Quick Start Ask the agent to show the pending review queue by saying "what's pending on the Bitfocus dashboard" and it will run the queue script to list modules awaiting review.

Frequently Asked Questions about companion-bitfocus-dashboard

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

FAQPage Schema
How do I check which Bitfocus Companion modules are pending review?▼

Run the bitfocus-queue.ps1 script or query the /modules-pending-review endpoint with a GitHub bearer token from gh auth token. The result is a ranked table sorted by submission date showing module name, tag, days waiting, and clone status.

How do I find the previous approved tag for a Companion module?▼

Query the /public/modules/companion-connection/{moduleName}/versions endpoint and filter for entries with status APPROVED, sorted by createdAt descending. If none exists, the result is NO_PREVIOUS_TAG, meaning it is a first release and all findings can block.

What authentication does the Bitfocus developer portal API require?▼

The portal accepts GitHub bearer tokens obtained via gh auth token from the GitHub CLI. No extra credentials or cookies are needed once gh auth login has been completed on the machine.

Why should I verify PENDING status before cloning a module?▼

The /modules-pending-review endpoint can include WITHDRAWN entries alongside PENDING ones. Only PENDING versions should be reviewed, so always check the module's status via the /versions endpoint before cloning or starting a review.

What is the GitHub repository URL pattern for Companion modules?▼

All Companion modules live in the bitfocus GitHub org at https://github.com/bitfocus/companion-module-{moduleName}, where moduleName is the lowercase kebab-case name returned by the API without any prefix.