dashboard-inspirations

Capture full-page screenshots of product dashboards for design inspiration into docs/inspirations.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill dashboard-inspirations-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-inspirations
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/dashboard-inspirations
Command: npx skills add https://github.com/falentio/cimi --skill dashboard-inspirations-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Gathering real, populated dashboard screenshots from analytics products for design reference is tedious: signups, email verification, seeded data, and dozens of pages to capture. This Skill automates the entire capture workflow end to end. ## Core Features & Use Cases - Access ladder: Climbs hosted signup (with mail.tm temp mail), client-side gate bypass, public demos, or self-hosting the vendor's OSS stack with seeded data. - Systematic capture loop: Enumerates nav routes and settings subpages, verifies page identity via DOM, and takes full-page screenshots including dialogs, popovers, and theme variants. - Verification and cleanup: Deduplicates captures via md5sum, converts PNG to WebP, and tears down sessions, containers, and helper processes. - Use Case: Ask to capture Plausible or Rybbit dashboards; the Skill registers an account, seeds events through the vendor's ingest API, and stores verified WebP screenshots under docs/inspirations/{domain}/. ## Quick Start Capture dashboard screenshots of umami.is for design inspiration and store them under docs/inspirations.

Frequently Asked Questions about dashboard-inspirations

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

FAQPage Schema
How do I capture dashboard screenshots of a SaaS product for design inspiration?

Run the capture workflow which registers an account, creates a site, seeds events, and takes full-page screenshots of every nav route and settings page. Output lands in docs/inspirations/{domain}/ as zero-padded WebP files.

How to register on a product that requires email verification?

The workflow uses the mail.tm API: create an account, fetch a token, poll messages, and handle 6-digit codes, magic links, or JWT verify links. Credentials are stored locally in /tmp/opencode/.

What if the hosted product is paywalled or the demo lacks pages?

Self-host the vendor's OSS repository with Docker Compose and seed data against its ingest route schema. The self-host-seeding reference covers BASE_URL wiring, same-origin proxying, and verifying landed rows before screenshots.

Why do seeded events not appear on the dashboard?

A success status is not delivery; bot rejection can answer 204 with an empty body. Send a real browser User-Agent, pace batches 10-20ms apart, and verify landed rows through a stats endpoint or ClickHouse count.

Does the workflow handle payment walls during signup?

It captures the checkout page and stops. No payment details or fabricated cards are ever provided; the run falls back to demos or self-hosting for remaining surfaces.