agent-skills

Operate a local Omnigent install — crashes, blank UI, restarts, session attach/resume/dispose, process topology — and drive other agents via the sys_* MCP tools.

Extract a person's LinkedIn writing voice DNA into an 8-dimension style profile with vocabulary fingerprint, signature moves, and a Prompt Engineering Guide.

Audit third-party code (repos, npm packages, binaries, plugins) for telemetry, exfiltration, supply-chain risk, and hostile defaults before install; verdict SAFE/CAUTION/UNSAFE with file:line evidence.

When loaded: deliver reports, intake interviews (>3 fields), and option/mockup choices as one self-contained offline .html page instead of chat Markdown. Forms return answers via a copy-paste token.

Optional layer: write specs, plans, designs, and reports as MDX (Markdown + a component library) rendered locally via Vite — git-diffable, degrades to plain Markdown, no remote services.

Pre-install safety check for a software update — invoke on an update prompt, 'new version available', upgrade notice, or when asked if an installed/trusted tool is safe to update.

Drive a browser via Playwright MCP — navigate, fill forms, click, scrape, or run e2e tests/scripts. Two servers: `playwright` (fresh, no logins) and `user-browser` (the user's live logged-in browser via CDP).

Multi-round multi-source research (Perplexity, Tavily, Exa, Gemini, WebSearch) producing a cited report with confidence scores and gaps.

Search past Claude Code conversations (JSONL session history) by topic, content, date, or working directory.

Use when a vague work item needs product/user clarification before planning or implementation.

Use when the user wants to run a work item through the workflow engine, e.g. "/workflow <prompt>", "start a workflow for ...", or "run the workflow engine on ...".

Autonomous brainstorm→PR pipeline. Invoke on /autopilot. Runs an interactive brainstorming session to an approved spec, then launches a background Workflow that plans, builds, reviews, verifies, and opens a PR with no further human input. Resumes a halted run when re-invoked.

DEPRECATED — do not activate. Superseded by the workflow engine skill (workflow:workflow) and the OMP workflow core. Kept for historical reference only; the .work/ directory convention it describes is obsolete.

Structured grilling to clarify a vague product/feature need before any implementation. Invoke only on /product-discovery. Produces a discovery log + the artifact the user requests (PRD, RFC, design note, message, or just chat clarity).

Use when an approved spec needs a technical design -- architecture and technology choices grounded in compared options -- before planning.

Use when working on a drawio diagram with a user who views or edits it in a browser — remote/SSH sessions, "let's collaborate on the diagram", "open it in my browser", live review of diagram changes — or whenever the drawio skill is active and the user cannot open local files. Overlay on the drawio skill; check this BEFORE building any export-and-show review loop.

Platform knowledge for ChatGPT Deep Research at chatgpt.com. Standalone: spawns browser-researcher agent. Or loaded by browser-researcher at runtime via skill_path. Trigger on "chatgpt deep research", "run this through ChatGPT", "ask ChatGPT to research", "delegate to ChatGPT deep research", "use ChatGPT for this research". Does NOT trigger on generic "deep research".

Platform knowledge for Claude.ai Research at claude.ai. Standalone: spawns browser-researcher agent. Or loaded by browser-researcher at runtime via skill_path. Trigger on "claude.ai research", "use claude research", "run this on claude.ai", "delegate to claude ai", "ask claude.ai to research". Does NOT trigger on generic "deep research".

Platform knowledge for Gemini Deep Research at gemini.google.com. Standalone: spawns browser-researcher agent. Or loaded by browser-researcher at runtime via skill_path. Trigger on "gemini deep research", "use gemini to research", "run deep research on gemini", "google deep research", or when explicitly requesting Gemini's native deep research capability.

Analyze a project and extract conventions, patterns, and context into a CLAUDE.md file. Works for any project type — code repos, presentation collections, research corpora, documentation projects. Trigger on "extract conventions", "analyze project patterns", "generate CLAUDE.md", "what are the conventions", or /conventions.