koval-linkedin-authority
Build a LinkedIn authority and email conversion plan using Arthur Koval's public method, including reply then connect, accept then email, and connecting only the top 10% of leads. Use for B2B content, lead magnets, channel sequencing, and pipeline reviews.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- koval-linkedin-authority
- description
- Build a LinkedIn authority and email conversion plan using Arthur Koval's public method, including reply then connect, accept then email, and connecting only the top 10% of leads. Use for B2B content, lead magnets, channel sequencing, and pipeline reviews.
02 资源文件 7
- 参考文档checklists/review-checklist.md4.5 KB
- 参考文档DERIVATION.json2.4 KB
- 参考文档examples/worked-examples.md8.4 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md13.9 KB
- 参考文档references/sources.md3.7 KB
- 参考文档templates/output-template.md5.8 KB
03 SKILL.md 正文
LinkedIn Authority System
Based on Arthur Koval's public method. Not affiliated with or endorsed by Arthur Koval.
When to use
Use this skill when a B2B founder, consultant, agency, or service business wants LinkedIn attention to become qualified conversations and commercial opportunities. It supports an integrated content, lead magnet, email, and connection plan, plus reviews of an existing funnel. It is especially useful when both channels repeat the same pitch, connection requests are spent indiscriminately, or engagement rises without qualified meetings.
Produce a reviewable plan and original message drafts using the supplied business facts. Preserve the user's requested scope: a sequence review does not require a full content rebuild. Preparing a plan does not authorize publishing, sending messages, adding contacts, or subscribing people. Honor any execution authority already granted separately.
Read the relevant sections of the method reference as you work. Its cited rules are Koval's public guidance; its explicitly marked adaptations make that guidance executable. Never present the adaptations as his proprietary scripts, claim access to his private breakdown, or turn reported client outcomes into promises.
Procedure
-
Establish the commercial brief. Identify the ideal customer profile, buyer role, concrete problem, offer, available proof, and desired next action. Record missing facts as assumptions or questions. Use templates/output-template.md, especially the brief and evidence fields, to keep the plan grounded.
-
Set the evidence boundary. Read the scope and attribution notes in references/method.md and the retrieval notes in references/sources.md. Cite public rules with source IDs. Treat unobserved profile views, missing outcome data, and unpublished scripts as unknown.
-
Assign each channel its job. Use LinkedIn to support familiarity and credibility, and email for timely, relevant outreach. Explain how the channels reinforce one another rather than duplicating every message. Follow the channel principles in references/method.md.
-
Prepare the credibility surface. Align the profile's buyer, problem, proof, and next action with the offer. Select real experiences and client evidence that substantiate the positioning. Use the profile adaptation and evidence rules in references/method.md; flag unsupported proof for replacement.
-
Design content with a commercial purpose. Build experience-based posts and, where evidence permits, a client journey with a before state, mistaken diagnosis, intervention, after state, and reusable resource. Consult the content sections in references/method.md and the transformations in examples/worked-examples.md.
-
Define the lead magnet and email handoff. Choose a useful resource connected to the buyer's problem and offer. Specify the request, delivery, email capture, and subsequent value. Keep resource delivery separate from assumed newsletter permission. Follow references/method.md and populate the handoff fields in templates/output-template.md.
-
Choose a channel route for each cohort. Select email reply followed by connection, connection acceptance followed by email, or email outreach followed by connections reserved for the highest-value 10%. Record the trigger, rationale, and pending state using the routing table in references/method.md.
-
Make the top 10% auditable. Define an eligible cohort, rank by documented fit and commercial value, and select only its top decile for route three. Specify rounding, ties, and available capacity. Use the selection adaptation in references/method.md; do not confuse this route with a restriction on all warm relationships.
-
Draft the messages and exceptions. Write distinct email and connection copy tied to observable context. Include negative replies, automatic replies, already connected prospects, no acceptance, and overlapping routes. Use the edge cases in references/method.md and original illustrations in examples/worked-examples.md.
-
Define measurement and iteration. Track qualified conversations, meetings, opportunities, and commercial outcomes alongside engagement. Separate signed contract value from cash collected. Set a review window appropriate to the sales cycle and label any cadence as a local choice. Use the measurement guidance in references/method.md.
-
Assemble and review the deliverable. Complete the applicable fields in templates/output-template.md. Run checklists/review-checklist.md, repair failures, and return the plan with unresolved facts and the next action clearly stated.
Files in this skill
- SLUG.txt: Canonical package identifier for naming and installation.
- SKILL.md: Entry point, usage criteria, procedure, and resource routing.
- references/method.md: Cited method, channel decisions, adaptations, and exceptions.
- references/sources.md: Five fetched public sources and their evidence limits.
- examples/worked-examples.md: Invented before-and-after applications of all three routes.
- templates/output-template.md: Deliverable template with field-by-field guidance.
- checklists/review-checklist.md: Pass/fail review and corrections for common failures.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.