wes-kao-spiky-pov
Develop defensible, debatable points of view using Wes Kao's public method. Use when drafting or sharpening posts, essays, talk theses, founder takes, or positioning that feels obvious, hedged, or provocative without substance.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- wes-kao-spiky-pov
- description
- Develop defensible, debatable points of view using Wes Kao's public method. Use when drafting or sharpening posts, essays, talk theses, founder takes, or positioning that feels obvious, hedged, or provocative without substance.
02 资源文件 7
- 参考文档checklists/review-checklist.md4.9 KB
- 参考文档DERIVATION.json3.0 KB
- 参考文档examples/worked-examples.md6.2 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md14.1 KB
- 参考文档references/sources.md4.1 KB
- 参考文档templates/output-template.md4.6 KB
03 SKILL.md 正文
Spiky Point of View
Based on Wes Kao's public method. Not affiliated with or endorsed by Wes Kao.
Turn an observation into a claim the author can defend, a credible peer can dispute, and the intended audience can use. Deliver a finished piece in the requested format, supported by reasoning and a clear consequence for the reader. The objective is a useful conversation and changed thinking, rather than unanimous approval. [S1]
When to use
Use for LinkedIn or X posts, opinion essays, thought leadership, founder perspectives, talk theses, and positioning lines. Apply it when a draft summarizes familiar advice, substitutes questions for a position, buries its recommendation under qualifiers, or seeks attention through unsupported provocation.
Work within the author's actual domain and experience. Preserve their intended audience, purpose, format, and voice. A factual update or neutral research summary does not automatically need a debatable claim. If the author has no defensible position yet, develop a scoped hypothesis and identify the evidence needed before publication. Never manufacture personal conviction, customer stories, or results. [S1][S5]
Procedure
Use the following loop. Read references/method.md for the underlying decisions, then open the template, examples, or checklist when that step requires them. Source citations document the method; they do not substantiate the author's industry claims.
-
Define the brief. Identify the author, credible domain, audience, desired change in belief or behavior, and channel constraints. Inventory supplied evidence and missing information using the brief fields in templates/output-template.md. Ask only for gaps that materially affect the claim.
-
Mine candidate positions. Use the prompts in references/method.md. Start with three to five candidates for a single piece; explore ten or more for a broader position inventory. Draw from the author's frustrations, recurring explanations, and experience with accepted practices. [S1][S2]
-
Separate facts from interpretation. For each candidate, identify what was observed, what it might mean, and what the author recommends. Follow references/method.md to move beyond an interesting fact toward an owned conclusion. [S3][S6]
-
Apply the five traits. Check debatability, useful purpose, audience learning, defensibility, and conviction against references/method.md. Reject a candidate that merely attracts attention or repeats consensus. Repair a promising candidate before discarding it. [S1]
-
Write a credible opposing view. Use the disagreement test in references/method.md. Explain why a knowledgeable peer would choose differently. Select the candidate with the strongest combination of author credibility, evidence, and reader relevance; briefly explain the choice when comparing supplied drafts.
-
Sharpen the claim. Name the situation, disputed practice or frame, and recommended alternative. Use references/method.md and examples/worked-examples.md to replace broad slogans with bounded, meaningful assertions. Add numbers only when supported.
-
Build the reasoning. Connect evidence to interpretation and action. Show a concrete example, script, or decision rule, following references/method.md. Distinguish firsthand evidence from assumptions and proposed tests. Never treat an invented illustration as the author's history. [S9][S13]
-
Calibrate certainty. Match wording to evidence, stakes, and the author's authority. Use references/method.md to preserve necessary uncertainty while removing defensive filler. A confident style does not convert a hypothesis into a fact. [S5][S8]
-
Handle the obvious objection. Anticipate the most likely substantive challenge and answer it in a proportionate passage. Follow references/method.md. Keep a material exception even when it requires more explanation than a short post allows. [S8]
-
Assemble the deliverable. Fill the publishable section of templates/output-template.md: claim, evidence or mechanism, objection, and reader consequence. Lead with reader value before detailed instructions when buy-in is missing. Answer substantive questions before inviting discussion. [S3][S4][S14]
-
Review and revise. Run checklists/review-checklist.md. Resolve failures by changing the claim, evidence, scope, or wording. Keep necessary reasoning; cut material that serves venting or distracts from the reader's next decision. [S7][S15]
-
Return and test. Return the requested piece, with a short rationale or evidence gaps only when useful. Use references/method.md to propose audience testing when appropriate. Report resonance as untested until real feedback exists, then revise the exact passages that create interest, confusion, or disagreement. [S12]
Files in this skill
- SKILL.md: Entry point, usage boundaries, and the agent's working loop.
- references/method.md: Detailed principles, decision rules, warnings, and edge cases.
- references/sources.md: Numbered register of fetched public sources and their contributions.
- examples/worked-examples.md: Invented illustrations with weak drafts, revisions, and rule notes.
- templates/output-template.md: Fill-in brief, reasoning record, and finished-piece template.
- checklists/review-checklist.md: Pass/fail review, recurring failures, and practical fixes.
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.