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 "optimize my LinkedIn profile", "update my LinkedIn headline", "rewrite my LinkedIn summary", "improve my LinkedIn about section", or when Genesis identifies that the user's profile doesn't align with their current goals or target audience.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Analyze and rewrite LinkedIn profile sections to clearly communicate the user's value to their target audience — whether that's employers, clients, or professional network. Avoid generic "results-driven professional" language. Sound human. Sound like the user.
Before writing any profile content, load the user's voice via voice-master's overlay resolution:
../voice-master/SKILL.md and follow its User Calibration
Overlay section to load the user's exemplars and voice-dimensions from
the out-of-repo overlay (or template fallback with warning if no overlay).professional. Select professional-medium
exemplars from whatever voice-master loads.../voice-master/references/anti-slop.md — apply the Universal
and Professional / LinkedIn sections.If no overlay is present, voice-master falls back to the generic template and warns — note this in your output.
Profile copy follows the same anti-slop rules as posts. A profile that reads like a ChatGPT template is worse than an outdated one.
The most visible element. Appears in search, comments, connection requests.
Formula: [What you do] | [For whom or in what domain] | [Differentiator]
Rules:
First-person narrative. Not a resume summary — a conversation with the reader.
Structure:
Rules:
Each role should communicate impact, not just responsibilities.
Formula: [What you did] → [What changed because of it] → [How you did it]
Rules:
Prioritize skills that:
Curate 3-5 items maximum:
Gather current state — Ask the user to paste their current profile sections, or provide their LinkedIn URL for reference.
Clarify goals — What is the profile optimized FOR? Job search? Client acquisition? Professional networking? Thought leadership? The rewrite differs significantly based on the answer.
Identify target audience — Who should find this profile compelling? Recruiters in cloud engineering? CTOs evaluating consultants? Peers in the same field?
Rewrite sections — Apply voice profile, anti-AI rules, and the structure guidance above. Provide before/after for each section.
Keyword check — Ensure high-value search terms appear naturally in headline, about, and experience sections. Never keyword-stuff.
target_goal: <job search | client acquisition | networking | thought leadership>
target_audience: <who this profile should attract>
sections_optimized:
- section: <headline | about | experience | skills | featured>
before: |
<original text if provided>
after: |
<optimized text>
rationale: |
<why these changes were made>
../voice-master/SKILL.md — Voice authority; follow its User Calibration Overlay section to load professional exemplars from the user overlay../voice-master/references/anti-slop.md — Universal + Professional/LinkedIn anti-slop rulesまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。