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 "research this company", "look into this person", "find the best angle for reaching out to", "who should I contact at [company]", "what does [company] care about", or when preparing outreach to a specific target. Also triggered by "help me prepare for an interview with [company]" or "I want to apply to [company]". Combines lead-generation intelligence with LinkedIn-specific approach planning.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Research a target company or person deeply enough to craft outreach that demonstrates genuine understanding — not generic "I saw your profile and thought we'd be a great fit." Produce actionable intelligence: what they care about, what problems they face, what angle gives the user the best chance of a meaningful response.
This skill does the RESEARCH. Other skills use its output:
linkedin-dm-outreach — Uses findings to write personalized messageslead-generation — May trigger this for deep enrichment on hot leadslinkedin-post-writer — May inform commentary posts about the target's spaceosint — Can be invoked for deeper investigation on high-value targetsClarify who and what to research:
target:
type: <company | person | both>
company_name: <if known>
person_name: <if known>
person_role: <if known or "find the right person">
goal: <job_search | client_outreach | networking | partnership | interview_prep>
user_offering: |
<what the user brings to the table — skills, experience, services>
If the user says "find the right person at [company]," determine the right contact based on the user's goal:
Gather structured information about the target company:
Public sources (search in this order):
site:linkedin.com/company/[name] — company page, employee count, postssite:stackshare.com, site:builtwith.com, job posting requirementsSynthesize into:
company_intel:
summary: <what the company does, in plain language>
size: <employee count range>
stage: <startup | growth | enterprise>
recent_news:
- <significant recent events>
current_priorities: |
<what they appear to be focused on, based on hiring/news/content>
tech_stack:
- <confirmed technologies>
challenges: |
<inferred pain points based on hiring patterns, industry context>
culture_signals: |
<what their content and careers page reveal about values/culture>
If researching a specific person:
Public sources:
"[name]" "[company]" site:linkedin.com — profile summary, experience"[name]" (talk OR podcast OR interview)Synthesize into:
person_intel:
name: <full name>
role: <current title>
tenure: <how long at current company>
background: |
<career trajectory — where they came from, pattern of roles>
interests: |
<what they post/talk about, what they care about professionally>
communication_style: |
<how they write — formal/casual, technical/business, verbose/concise>
connection_points:
- <shared interests, experiences, connections with the user>
recent_activity: |
<their most recent posts or public activity>
The most valuable output. Based on company intel, person intel, and the user's goal, identify the best approach:
approach_analysis:
primary_angle: |
<the single strongest reason this person should respond to the user>
supporting_angles:
- <backup angle if primary doesn't resonate>
- <additional angle>
connection_points:
- <specific shared elements — technologies, industries, challenges>
timing_factors: |
<why reaching out NOW is relevant — recent news, hiring, etc.>
what_to_avoid: |
<approaches that would likely backfire with this person>
recommended_channel: <linkedin_dm | email | mutual_introduction | event>
recommended_message_type: <connection_request | inmail | first_message>
confidence: <high | medium | low>
confidence_reasoning: |
<why we're confident or not in this approach>
Combine all findings into a structured report. If Genesis is running this proactively (background task), stage the report for user review.
# Prospect Research: [Target Name/Company]
**Date:** YYYY-MM-DD
**Goal:** [user's stated goal]
**Confidence:** [high | medium | low]
## Company Overview
[company_intel summary]
## Contact: [Person Name]
[person_intel summary]
## Recommended Approach
**Primary angle:** [primary_angle]
**Channel:** [recommended_channel]
**Timing:** [timing_factors]
## What to Avoid
[what_to_avoid]
## Raw Intelligence
[Full yaml blocks for reference]
## Suggested Next Steps
- [Concrete action items — e.g., "Draft connection request using X angle"]
- [Follow-up research if needed]
references/research-sources.md — Detailed source hierarchy and search patterns../linkedin-dm-outreach/SKILL.md — Uses findings for message drafting../lead-generation/SKILL.md — Broader prospecting pipeline../osint/SKILL.md — Deep investigation capabilityまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。