Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "write a hook for my post", "give me opening lines", "help me start this LinkedIn post", "I need a better opener", or when the linkedin-post-writer skill needs strong opening options. Also triggered by "my posts aren't getting clicks" or "how do I get people to read my posts".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Generate attention-grabbing opening lines for LinkedIn posts that earn the click to "...see more" — without resorting to the clickbait patterns that mark content as AI-generated or engagement-farmed. The hook must be honest: it promises something the post actually delivers.
This skill's entire value depends on producing hooks that are NOT on the anti-slop banned-openers list.
../voice-master/references/anti-slop.md — apply the Universal
and Professional / LinkedIn sections. The Banned Openers subsection
under Professional / LinkedIn is the hard constraint for this skill.../voice-master/SKILL.md
and follow its User Calibration Overlay section. Voice-master loads
social-medium exemplars from the user overlay (or template fallback
with warning if no overlay).If no overlay is present, voice-master falls back to generic voice guidance and warns — note this in your output.
LinkedIn shows approximately the first 140-210 characters of a post before truncating with "...see more." The hook must accomplish two things in that space:
A hook that creates curiosity but signals low quality gets skipped. A hook that signals quality but creates no curiosity gets polite scrolling.
Start with a concrete, surprising detail that makes the reader want context.
Why it works: Specific numbers and details signal real experience. The reader wants the story behind the detail.
Start by admitting something most people in your position wouldn't say.
Why it works: Vulnerability from someone with credibility is rare on LinkedIn. It signals an honest post, not a performance.
State something that goes against conventional wisdom — but only if you can back it up.
Why it works: Disrupts autopilot scrolling. The reader needs to see the reasoning.
Notice something specific about the industry, the job, or the professional world that others feel but haven't articulated.
Why it works: Recognition — the reader sees their own experience reflected and wants to see if the post develops it further.
Begin in the middle of a situation, not at the beginning.
Why it works: Narrative momentum — the reader is dropped into a moment and wants to know what happened.
Understand the post — Read the full post content or the angle from the content calendar. The hook must honestly represent what follows.
Generate 3-5 options — Use different patterns. Never generate 5 variations of the same pattern — that's what AI does when it's lazy.
Anti-slop check — Verify each option against the banned openers list. Delete any that feel like they could appear in a "LinkedIn post template."
Rank — Evaluate each hook on: curiosity generated, quality signaled, authenticity, connection to the post body.
Present with reasoning — Show the user options with brief notes on why each works or might not work.
## Hook Options for: [Post Topic/Angle]
### Option 1 (Pattern: [pattern name])
> [Hook text]
**Strength:** [Why this works]
**Risk:** [Why it might not — or "low risk"]
### Option 2 (Pattern: [pattern name])
> [Hook text]
...
### Recommended: Option [N]
**Reasoning:** [Why this one best fits the post and voice]
../voice-master/references/anti-slop.md — Banned openers and AI-tell patterns (Universal + Professional/LinkedIn sections)../voice-master/SKILL.md — Voice authority; follow its User Calibration Overlay section to load social exemplars from the user overlay../linkedin-post-writer/SKILL.md — Post types and writing processまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
日本語の概要は準備中です。原文の説明を表示しています。
Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis
日本語の概要は準備中です。原文の説明を表示しています。
Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and stops at the merge gate for the user's per-PR approval. Do NOT load it for building a feature and opening its PR — that is a build session (`genesis-development`).
日本語の概要は準備中です。原文の説明を表示しています。
Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end content creation and publishing. Takes a topic (or generates one), drafts in the user's voice, gets approval via Telegram, and publishes to Medium via browser automation. Invoke with "publish a post about X", "write and publish to Medium", "content-publish", or when an ego-dispatched session needs to create and distribute content.
日本語の概要は準備中です。原文の説明を表示しています。