dashboard-forge
dashboard-forge handles vendor dashboard operations that have no public API by driving a real Chrome browser with persistent per-site profiles, letting humans handle logins once while scripts execute the rest reproducibly. It extracts secrets safely to vault, survives UI drift through step-and-shoot methodology, and covers tasks like minting scoped tokens and creating OAuth apps where the vendor offers no API or your existing token lacks scope.
dashboard-forge automates vendor dashboard operations without public APIs by supervising browser automation with persistent Chrome profiles.
AI-generated summary based on this skill's SKILL.md
Install
terrylica/cc-skills/dashboard-forge · repository language: Shell
git clone https://github.com/terrylica/cc-skills
cp -r cc-skills/plugins/web-forge/skills/dashboard-forge ~/.claude/skills/dashboard-forgenpx skillfed install terrylica/cc-skills/dashboard-forgeFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does dashboard-forge automate vendor dashboard without API?
dashboard-forge drives a real Chrome browser with persistent per-site profiles to automate vendor dashboard operations that lack public APIs. Humans handle logins once; scripts then execute the remaining steps reproducibly. This approach lets you perform tasks like minting tokens and creating OAuth apps where the vendor offers no API alternative.
Can dashboard-forge mint OAuth token via dashboard?
Yes. dashboard-forge specializes in minting and extracting scoped credentials through supervised browser automation. It automates the click-paths needed to create OAuth apps and tokens directly through web UIs, then safely extracts those secrets to vault without exposing them during the process.
What happens when the dashboard UI changes?
dashboard-forge handles UI drift through step-and-shoot methodology, allowing it to adapt when vendor dashboards change their layouts. Combined with human supervision during automation, this approach helps scripts remain resilient across dashboard updates and consent overlays that may appear during credential setup.
How does dashboard-forge keep secrets safe?
dashboard-forge safely extracts secrets from dashboards without exposing them during automation. Credentials and tokens are vaulted securely rather than logged or displayed, protecting sensitive data throughout the minting and extraction process.
What browser technology powers dashboard-forge?
dashboard-forge uses Chrome DevTools Protocol (CDP) to drive a real Chrome browser instance. This enables supervised web UI automation for vendor dashboards, letting you automate admin console setup and credential creation tasks that would otherwise require manual intervention.
When should I use dashboard-forge instead of an API?
Use dashboard-forge when a vendor offers no public API, when your existing token lacks the required scope, or when you need to automate account setup and credential minting through the web UI. It's designed as an API alternative for dashboard operations that have no programmatic interface.
SKILL.md
rendered from the published skill — quoted content, verbatim
dashboard-forge — supervised dashboard automation doctrine
Some operations exist ONLY behind a vendor's web UI (GitHub fine-grained PATs and OAuth apps have no creation API; a Cloudflare token cannot grant itself new scopes). This skill is the canonical method for automating those click-paths safely: the human supervises and handles logins/2FA;
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
plugins/web-forge/skills/dashboard-forge/SKILL.md