Explorar skills

Capture full-page screenshots of one or more websites. Handles scroll-triggered animations, lazy-loaded content, cookie banners, and bot-protected sites. Uses a tiered approach: Microlink API first, Chrome browser fallback for protected sites. Use when you need design references, competitive analysis screenshots, or visual audits. Invoke with /site-capture:capture.

Audit existing screenshot captures for quality issues. Checks every PNG file in a directory for wrong-company content, blank sections, cookie banners, error pages, and other problems. Reports what needs recapturing. Use when screenshots look wrong or after a batch capture to verify quality. Invoke with /site-capture:audit.

Daily research automation. Scans configured domains for actionable intelligence, filters through the weekly strategy brief for relevance, and produces a dated research report with action items for PM ingestion. Opens an auto-mergeable PR. Reads pulse-config.yaml from the nearest research directory. Trigger: "run daily research", "research scan", "what's new", "check for updates", or /product-pulse

Interactive sprint worker. Reads status/ready + owner/ai items from GitHub Issues (or local backlog), presents them with context, groups into proposed PRs, and waits for your approval before building. Dispatches parallel sub-agents with self-review and full testing. Reads CONTEXT.md for domain terminology and .pm/out-of-scope/ for negative constraints. Trigger: "let's build", "work the backlog", "

Weekly strategic intelligence. Dispatches 5 analyst agents (Market Scout, Competitor Tracker, Audience Analyst, Growth Analyst, Product Scout), reads the last 7 daily reports, and produces a strategy brief + recommendations for PM ingestion. Reads pulse-config.yaml from the nearest research directory. Run Monday mornings or whenever you need strategic direction. Trigger: "run weekly strategy", "we

Sync project reality with the issue tracker. Scans git history for completed items, detects stale work, classifies deferred blockers, updates epic progress, proposes CONTEXT.md updates and ADRs. Run after sprints, after merges, or periodically. Trigger: "reconcile", "sync issues", "clean up backlog", "check progress", or /pm:reconcile.

Onboard Product Pulse to a new project. Interviews you about your product, competitors, target audiences, and strategic priorities, then scaffolds the research directory, pulse-config.yaml, research context, research sources, and deep-dives directory. Run this once when you first install the plugin. Use when you say "setup product pulse", "onboard", "configure pulse", "initialize research", or inv

Read research reports from product-pulse (daily, weekly, deep-dive) and create status/needs-triage items in the configured issue tracker. Diffs against existing issues, current codebase, and out-of-scope rejections to avoid duplicates. Uses ingestion watermarks to process only new reports. Trigger: "ingest research", "process reports", "import findings", or /pm:ingest.

Trigger on "weekly podcast", "timeln podcast", "podcast from my saves", "turn my saves into audio", "listen to my saves". Produces one Timeln Podcast MP3 from Timeln saves (default: last 7 days). Full pipeline: pull, connect, TTS script, local render. NOT for text-only search (timeln-find) or action plans (timeln-plan).

Trigger on "pursue client", "pitch email", "follow up proposal", "call script proposal", "consult pursue", "cos pursue", "/cos-pursue {client} for {topic}". Post-pack pursuit: cover email, 30-min call script, objection stubs. Cold-start mode when only client + topic given — synthesizes pack from public research. Uses timeln-shipped and timeln-quickly. NOT packaging (consult-package), NOT frame (co

Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to