
from domo-ai-vibe-rules14
End-to-end guidance and wiring to build a branded client portal that serves Domo dashboards to external users with per-user filters, auth, and optional edit-mod
Guides the construction of a branded embed portal that surfaces Domo dashboards to external users (clients, partners, customers) with per-user authorization and data isolation. The skill defines a full implementation plan: requirement gathering, Next.js scaffolding, auth and user management patterns, a dynamic dashboard registry, and safe handoffs to specialized sub-skills for embed token generation, Identity Broker edit flows, and JS API filter wiring.
Use this skill when you need to give external users login-based access to Domo content—whether read-only dashboards, editable dashboards via Identity Broker, or a mix of both. Trigger when the project scope includes 'client portal', 'white-label reporting', 'sell access to analytics', or 'external users see their own dashboards.'
This skill pairs well with agents that can author web app code and configuration (Copilot/Code assistants, Claude Code). It explicitly relies on sub-skills for embed token flows and JS API work, so it's best used in environments where those sub-skills are available or can be referenced.
Comprehensive Domo embed portal skill covering auth, user management, dashboard registry, and sub-skill handoffs for read-only/edit embeds and JS API. No bundled scripts — purely instructional SKILL.md. Strong security posture with proper env var handling, bcrypt, HttpOnly cookies, and server-side token generation. Architecture is well-organized with clear delegation to sub-skills, though the SKILL.md itself is quite long.
Well-crafted skill for a niche Domo audience. The sub-skill handoff pattern is exemplary — explicitly avoids duplication and points users to maintained skills. Security checklist is thorough. No scripts to audit. The SKILL.md is lengthy but well-structured with clear phases.