dzianisv

Use when the user wants to drive their real running Chrome with agent-browser-style commands — open pages, snapshot interactive elements as @e1 refs, click, fill, type, screenshot, scroll, eval. Triggers on chrome, browser automation, web automation, fill a form, click a button, snapshot the page, @e1 refs, agent-browser, take a screenshot. Connects to the user's actual Chrome profile (live sessions, cookies, auth) via DevToolsActivePort autoConnect, zero dependencies. Do NOT use for headless/throwaway browsers or launching a new Chrome instance.

Produce a 1-minute visual ops/session report as an HTML artifact: status banner, root-cause table, one flow diagram, shipped/open tables, and a session work log with PR links and live-verified statuses. Use when asked for a report, session report, incident recap page, or 'write up what we did'.

analyse assets using fundamental, technical, smartmoney and narrative. Use when user ask to analyze stocks or an advice if he should buy hold or sell

Use when directing, configuring, recovering, or scheduling a Hermes Agent through chat, Telegram, or another messaging gateway instead of logging into its host. Triggers on "prompt Hermes", "set up Hermes", "configure Hermes cron", "recover Hermes credentials", "message the Hermes bot", "make Hermes do this daily", and "Hermes ignored my prompt".

Write or edit blog posts in the user's preferred style: short, technical, software-engineer voice, understandable to non-experts, value-first, with light SEO and subtle promotion of the relevant product or service. Use when asked to create, draft, rewrite, review, or improve a blog post, article, technical announcement, founder note, or SEO content.

Write or improve any AI agent instruction surface — SKILL.md, AGENTS.md, CLAUDE.md, GOAL.md, dynamic workflow scripts, or any agent documentation. Also refines a user's rough prompt into a production-quality agent prompt. MUST be loaded whenever writing, editing, reviewing, or refining agent instructions. Triggers: "write a skill", "improve SKILL.md", "write agent instructions", "update AGENTS.md", "update CLAUDE.md", "write GOAL.md", "create a workflow script", "write a dynamic workflow", "refine this prompt", "turn this into an agent prompt", "improve this prompt", "prompt engineering". For scaffolding/discovery, pair with skill-creator.

Find a past GitHub Copilot CLI agent session on this machine by project or topic via BM25 search, then summarize what was done. Use when the user asks "which Copilot session did I do X in", "find the Copilot CLI session where I worked on Y", or wants to locate/recall a previous GitHub Copilot conversation. Reads local ~/.copilot session stores. Not for searching code, git history, or the current live session.

Use the preinstalled gws CLI for Google Drive, Gmail, and Calendar workflows, including customer-assisted OAuth login and multi-account control.

Write or edit a general-purpose technical/news/timely blog post in the VibeBrowserProductPage repo (root `blog/*.md`), which publishes to BOTH vibebrowser.app and agentlabs.cc from one file. Use for any source-cited post that is NOT a sales/competitive-landscape piece (use blog-hub) and NOT an #ainativecompany series post (use blog-ainative). Prefer this over the global blogpost skill when working inside this repo, because it encodes the real frontmatter parser, dual-domain publishing, route-parity link rules, and validation commands. Triggers: draft/write/rewrite/review a blog post, technical announcement, news reaction, founder note, or timely research post for this repo.

Write, optimize, validate, and publish Vibe blog posts using canonical product sources, with clear steps for placement in /blog, compilation, SEO/LLM optimization, and production publishing.

Use this skill when writing or editing blog posts for the #ainativecompany series on vibebrowser.app. Governs voice, structure, tags, evidence requirements, and anti-patterns. All posts must be short, technical, honest, and useful to a reader who wants to run a similar setup.

Drive growth for VibeBrowser products. Use when asked to promote, post to Reddit/HN/X, find competitor complaint threads, reply to community discussions, update growth tracking files, run the daily growth routine, or check post performance. Triggers on "promote", "post to reddit", "show HN", "growth", "community post", "find threads", "check HN", "reply to", "daily routine", "track posts", "competitor search".

Promote VibeBrowser products on Reddit, Hacker News, and X/Twitter. Use when asked to create community posts, find relevant threads, reply to discussions, track post performance, update growth.md strategy, or log posts in growth.csv. Triggers on phrases like "post to reddit", "show HN", "promote", "growth", "community post", "find threads about", "check HN", "track our posts".

Explain, verify, and extend PostHog analytics for vibebrowser.app using the current product-page integration and first-party proxy setup.

Analyze Search Console compare views for vibebrowser.app (especially 28 days vs previous, breakdown=page), convert findings into prioritized SEO + LLM optimization tasks, and decide when /blog investment is justified.

Video conversion and hosting workflow using ffmpeg and git-lfs for Next.js/React projects

Verify OpenCode Mobile is PRODUCTION READY end-to-end. Triggers like "check production readiness", "are we ready to ship", "readiness check", "is opencode-mobile live", "is the app published". Runs a script that confirms both Google Play and F-Droid (self-hosted + mainline) are PUBLISHED and the app/site are healthy.

Generate production and local development keystores for Android release signing

Scan Android project and generate Play Console setup checklist (analysis only, no file modifications)

Complete Play Store setup - orchestrates scanning, privacy policy, version management, Fastlane, and workflows (Internal track only)

Step-by-step guide for creating Google Cloud service account for Play Store API access

Read OpenCode sessions, messages, and tool outputs directly from the SQLite database at ~/.local/share/opencode/. Use when asked to "read opencode sessions", "query opencode db", "find old sessions", "search session history", "read message history", "export session", "inspect opencode data", "look up past conversations", or any task requiring direct access to OpenCode's local storage. Does NOT require a running OpenCode server.

Evaluate GenAI agent task execution using LLM-as-judge. Produces structured scores (0-5), feedback, and improvement recommendations.

Verify plugin spec requirements with actionable test cases. Use when testing reflection or TTS plugins, validating code changes, or running the test suite before deployment.

Verify all OpenCode plugin services are healthy and ready. Use when diagnosing plugin issues, after deployment, or when services like Whisper, TTS, Supabase, or Telegram aren't working.

Standard workflow for developing features. Follow this process for all non-trivial changes - from planning through PR merge. Ensures proper testing, review, and CI verification.