Pawel Huryn

Apply the Acme house style to any prose - short sentences, no hype, lead with the answer. Shared across agents.

The English summary is being prepared. Showing the original description.

Use when reporting a bug. Format the finding as exactly two lines - a BUG line stating what is wrong, then a FIX line with the one-line change.

The English summary is being prepared. Showing the original description.

Use whenever you state a fact. Add a short "Sources:" list at the end of your answer with where each claim came from (file name, URL, or "reasoning"). Shared by every agent on the team.

The English summary is being prepared. Showing the original description.

Use whenever you state a fact. End the answer with a short Sources list mapping each claim to a file, URL, or reasoning. Shared across agents.

The English summary is being prepared. Showing the original description.

Use for every answer. After the final answer, append a new line that starts with exactly "RECEIPT:" followed by a three-word note. This proves the skill was loaded by the runtime.

The English summary is being prepared. Showing the original description.

Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.

The English summary is being prepared. Showing the original description.

Spawn a new Claude Code session with remote control enabled (default: a detached background session — via screen on macOS/Linux, via a minimized PowerShell Start-Process on Windows — fully remote-safe, no approvals/windows), so it appears in the mobile Claude Code session picker. Takes an optional directory path; defaults to the current working directory. Use when the user runs /rc-new.

The English summary is being prepared. Showing the original description.

Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.

The English summary is being prepared. Showing the original description.

DON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.

The English summary is being prepared. Showing the original description.

Use OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.

The English summary is being prepared. Showing the original description.

Use OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.

The English summary is being prepared. Showing the original description.

DON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.

The English summary is being prepared. Showing the original description.

Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.

The English summary is being prepared. Showing the original description.

Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.

The English summary is being prepared. Showing the original description.

Spawn a new Claude Code session with remote control enabled (default: a detached background session — via screen on macOS/Linux, via a minimized PowerShell Start-Process on Windows — fully remote-safe, no approvals/windows), so it appears in the mobile Claude Code session picker. Takes an optional directory path; defaults to the current working directory. Use when the user runs /rc-new.

The English summary is being prepared. Showing the original description.

Review a Python solution against a markdown spec, run it, and report bugs.

The English summary is being prepared. Showing the original description.