「links」の検索結果

谈判与议价 (谈判与议价 (Negotiation & Bargaining) — 面向要亲自坐上谈判桌的从业者（销售、采购、创业者、法务与商务、HR、投融资、以及为自己谈薪谈房谈合同的个人）的『把一次利益分歧，谈成一个双方都愿意签、签完还愿意执行的结果』的判断体系；不是某一个行业的成交话术合集，也不是博弈论课程，更不是把心理学包装成读心术的培训话术。覆盖：(a) 第一性张力 —— 这行最深的世界观分歧：**创造价值 ⇄ 攫取价值**（同一场谈判里，把饼做大和把饼切走用的是相反的动作：做大要交换信息、暴露优先级，切走要隐藏底线、制造稀缺；哈佛原则式谈判一派主张先做大再切，实战议价派认为在多数一次性交易里做大只是让步的遮羞布，这条张力叫谈判者困境，是整个学科的中心问题）；**原则式谈判 ⇄ 战术共情**（Getting to Yes 主张对事不对人、按客观标准而非意志力定输赢；Chris Voss 从人质谈判带出的路线针锋相对，书名 Never Split the Difference 直接反对折中，主张先用标签与校准问题把对方的情绪与安全感处理掉再谈条件，并公开批评双赢框架让谈判者被真正强硬的对手吃掉；两派对同一个动作——比如要不要说出你的底线——给出相反指令）；**关系先行 ⇄ 条款先行**（中文语境里做生意常常先建立关系、找中间人引荐、酒桌上定调、合同只是关系的书面确认，人情与面子既是润滑剂也是隐性负债；跨国与合规语境里条款先行、把一切写进合同，两种作业习惯在同一张桌上相遇时的误读，是中外商务谈判失败最常见的原因之一；学术上关系到底是效率替代品还是寻租温床，证据本身就是对立的，且反腐与合规收紧之后酒桌路径的风险显著上升）；**先出价 ⇄ 后出价**（实验研究普遍支持先出价能形成锚定优势，但在信息高度不对称的真实交易里，先出价可能暴露自己远低于对方预期，实务派与研究派对这条给出的条件不同）；**BATNA 是地基 ⇄ BATNA 被高估**（最佳替代方案是原则式谈判的支点，没有替代方案就没有说不的能力；反对者指出过度盯着替代方案会把谈判做成线性比价，且强替代方案在长期关系里会损害对方的信任）；**情绪是噪音 ⇄ 情绪是议题**（早期理性决策路线要求把人和问题分开，后来的研究把情绪重新请回桌上：愤怒有时确实能提取让步，代价是长期关系与对方的报复动机，实验证据两个方向都有）；**谈判是技能 ⇄ 谈判是性格**（培训产业的立身之本是可训练，而研究显示某些结果差异与性别、地位与社会代价强相关：女性主动发起薪酬谈判在部分情境会被惩罚，这不是话术能解决的结构问题，近年多地薪酬区间披露立法正在改变这条起点）；**诚实边界在哪**（虚构竞标者、夸大授权上限、拖延签约制造紧迫，这些在培训里被当技巧、在法律上可能构成欺诈性陈述，法域不同边界不同）。(b) 工具栈 —— 这一行最重要的工具是纸笔：议题清单与优先级打分表、替代方案与保留价的估算表、可交换筹码矩阵、同时抛出的多个等值报价、让步阶梯与理由库、授权与升级路径表、复盘表；软件侧则是合同全生命周期管理与条款库（Ironclad、DocuSign、Juro、LinkSquares，中国侧法大大、e签宝）、采购电子寻源与反向拍卖（SAP Ariba、Coupa、Keelvar，以及已在大企业跑通的自动化议价机器人 Pactum）、销售侧的折扣审批矩阵与 deal desk、薪酬与职级数据（Levels.fyi、Mercer、Radford 以及各地薪酬透明披露）、可比交易与市场价数据、调解与仲裁机构（CIETAC、SIAC、香港 HKIAC）、以及正在快速变化的大模型陪练与合同审查；选型的真正分岔从来不是功能表，而是『这场谈判赢在信息、赢在替代方案，还是赢在流程设计』。(c) 心智模型层 —— 结果在坐上桌之前就决定了大半；谈的是利益不是立场；议价区间是估计出来的不是给定的；让步是信息不是善意；说不出口的常常是面子与安全感而不是价格；代表别人谈判的人激励与授权跟本人不同；一次性交易与长期关系的最优打法不同而多数人搞错了自己在玩哪一种。(d) 工作流 —— 立项与利益相关方梳理、准备与对手画像、替代方案与保留价、议题打分与打包设计、开场与锚定、探询与试探性提议、让步管理、僵局与第三方介入、收口与防止反悔加码、合同化与争议解决条款、复盘与关系维护，以及薪资谈判、采购年度框架议价、并购价格与条款、多方与联盟、跨文化与远程邮件谈判这些特化路径。(e) 表达 DNA、质量基准（什么算一次好的谈判：不是拿到最低价，而是可执行、可复盘、不透支关系）、反模式（外行最容易犯的错：不准备就上桌、把立场当利益、单方面让步买好感、把折中当公平、拿假竞标者施压、口头承诺不落纸、赢了条款输了执行）、智识谱系（哈佛谈判项目与原则式谈判、行为决策与实验社会心理学派、危机谈判与战术共情派、谈判分析与博弈论派、销售采购的实战议价培训派、争议解决与调解派、跨文化谈判派、中文语境的关系与人情派）。) Master OS — automated mastery of 谈判与议价 (Negotiation & Bargaining) — 面向要亲自坐上谈判桌的从业者（销售、采购、创业者、法务与商务、HR、投融资、以及为自己谈薪谈房谈合同的个人）的『把一次利益分歧，谈成一个双方都愿意签、签完还愿意执行的结果』的判断体系；不是某一个行业的成交话术合集，也不是博弈论课程，更不是把心理学包装成读心术的培训话术。覆盖：(a) 第一性张力 —— 这行最深的世界观分歧：**创造价值 ⇄ 攫取价值**（同一场谈判里，把饼做大和把饼切走用的是相反的动作：做大要交换信息、暴露优先级，切走要隐藏底线、制造稀缺；哈佛原则式谈判一派主张先做大再切，实战议价派认为在多数一次性交易里做大只是让步的遮羞布，这条张力叫谈判者困境，是整个学科的中心问题）；**原则式谈判 ⇄ 战术共情**（Getting to Yes 主张对事不对人、按客观标准而非意志力定输赢；Chris Voss 从人质谈判带出的路线针锋相对，书名 Never Split the Difference 直接反对折中，主张先用标签与校准问题把对方的情绪与安全感处理掉再谈条件，并公开批评双赢框架让谈判者被真正强硬的对手吃掉；两派对同一个动作——比如要不要说出你的底线——给出相反指令）；**关系先行 ⇄ 条款先行**（中文语境里做生意常常先建立关系、找中间人引荐、酒桌上定调、合同只是关系的书面确认，人情与面子既是润滑剂也是隐性负债；跨国与合规语境里条款先行、把一切写进合同，两种作业习惯在同一张桌上相遇时的误读，是中外商务谈判失败最常见的原因之一；学术上关系到底是效率替代品还是寻租温床，证据本身就是对立的，且反腐与合规收紧之后酒桌路径的风险显著上升）；**先出价 ⇄ 后出价**（实验研究普遍支持先出价能形成锚定优势，但在信息高度不对称的真实交易里，先出价可能暴露自己远低于对方预期，实务派与研究派对这条给出的条件不同）；**BATNA 是地基 ⇄ BATNA 被高估**（最佳替代方案是原则式谈判的支点，没有替代方案就没有说不的能力；反对者指出过度盯着替代方案会把谈判做成线性比价，且强替代方案在长期关系里会损害对方的信任）；**情绪是噪音 ⇄ 情绪是议题**（早期理性决策路线要求把人和问题分开，后来的研究把情绪重新请回桌上：愤怒有时确实能提取让步，代价是长期关系与对方的报复动机，实验证据两个方向都有）；**谈判是技能 ⇄ 谈判是性格**（培训产业的立身之本是可训练，而研究显示某些结果差异与性别、地位与社会代价强相关：女性主动发起薪酬谈判在部分情境会被惩罚，这不是话术能解决的结构问题，近年多地薪酬区间披露立法正在改变这条起点）；**诚实边界在哪**（虚构竞标者、夸大授权上限、拖延签约制造紧迫，这些在培训里被当技巧、在法律上可能构成欺诈性陈述，法域不同边界不同）。(b) 工具栈 —— 这一行最重要的工具是纸笔：议题清单与优先级打分表、替代方案与保留价的估算表、可交换筹码矩阵、同时抛出的多个等值报价、让步阶梯与理由库、授权与升级路径表、复盘表；软件侧则是合同全生命周期管理与条款库（Ironclad、DocuSign、Juro、LinkSquares，中国侧法大大、e签宝）、采购电子寻源与反向拍卖（SAP Ariba、Coupa、Keelvar，以及已在大企业跑通的自动化议价机器人 Pactum）、销售侧的折扣审批矩阵与 deal desk、薪酬与职级数据（Levels.fyi、Mercer、Radford 以及各地薪酬透明披露）、可比交易与市场价数据、调解与仲裁机构（CIETAC、SIAC、香港 HKIAC）、以及正在快速变化的大模型陪练与合同审查；选型的真正分岔从来不是功能表，而是『这场谈判赢在信息、赢在替代方案，还是赢在流程设计』。(c) 心智模型层 —— 结果在坐上桌之前就决定了大半；谈的是利益不是立场；议价区间是估计出来的不是给定的；让步是信息不是善意；说不出口的常常是面子与安全感而不是价格；代表别人谈判的人激励与授权跟本人不同；一次性交易与长期关系的最优打法不同而多数人搞错了自己在玩哪一种。(d) 工作流 —— 立项与利益相关方梳理、准备与对手画像、替代方案与保留价、议题打分与打包设计、开场与锚定、探询与试探性提议、让步管理、僵局与第三方介入、收口与防止反悔加码、合同化与争议解决条款、复盘与关系维护，以及薪资谈判、采购年度框架议价、并购价格与条款、多方与联盟、跨文化与远程邮件谈判这些特化路径。(e) 表达 DNA、质量基准（什么算一次

日本語の概要は準備中です。原文の説明を表示しています。

Ahrefs API analyst (extension). Reads referring domains, backlinks, organic keywords, and content explorer data via the official @ahrefs/mcp server. Pairs with seo-backlinks for multi-source confidence weighting.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.

日本語の概要は準備中です。原文の説明を表示しています。

Generate UTM-tagged URLs for campaign tracking. Create consistent, organized tracking links for Google Analytics, HubSpot, and other analytics platforms. Supports bulk generation, naming conventions, and campaign documentation. Use when creating tracking links, campaign URLs, or organizing marketing attribution.

日本語の概要は準備中です。原文の説明を表示しています。

Remix v2 performance, streaming, caching, and server/client boundaries. Use when configuring HTTP caching, server-only modules, hydration safety, or prefetch. Triggers on headers export, Cache-Control, PrefetchPageLinks, Link prefetch, .server.ts, .client.ts, useHydrated, ClientOnly, window.ENV, links preload, useId.

日本語の概要は準備中です。原文の説明を表示しています。

Use whenever the user wants to find, rank, or shortlist directories and registries where they can submit or list an MCP server (Model Context Protocol server) — to get backlinks, referral traffic, and discovery by agent builders. Triggers on "where do I list my MCP server", "best MCP directories", "MCP registries to submit to", "get my MCP server discovered", or "pull submission details for these MCP-directory domains", even when described indirectly (we built an MCP server, where do we publish it). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-ai-directories for general AI-tool / AI-agent / agent-skill listings, and to find-product-directories for general SaaS/software launches. Skip building an MCP server or asking how MCP works (DIY), finding a firm to build one (use find-ai-consultancy / find-software-developer), and MCP link-building *services*.

日本語の概要は準備中です。原文の説明を表示しています。

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

日本語の概要は準備中です。原文の説明を表示しています。

Check the health and freshness of locally-stored Claude documentation. Use this skill when the user asks about documentation health, broken links, stale docs, freshness checks, or wants to validate that their local install is up-to-date and all URLs are reachable. Triggers on: "are my docs current", "check doc health", "validate documentation", "broken links", "stale docs".

日本語の概要は準備中です。原文の説明を表示しています。

Use before publishing documentation, merging a docs PR, or reporting a Markdown-heavy repo's navigation as complete — when you want ground-truth confirmation that internal links, heading anchors, and directory links resolve, without opening every file yourself.

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a travel day hour by hour, fill a spare block of time ("I'm near X with 2 free hours"), turn a finished plan into a designed page (eight themed renders: illustrated / clay / noir / glass / journal / zine / splash / portal — 插画/黏土/夜航/玻璃/手账/Zine/闪屏/穿越版), or asks 旅行规划/行程安排/机票比价/去某国玩N天怎么安排/现在有空档干嘛/把行程做成好看的网页 — even if they only mention one piece (just flights, just hotels, or just navigation), the playbook and verification rules here still apply.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when creating or editing notes inside an Obsidian-compatible vault, to write correct Obsidian Flavored Markdown — wikilinks, embeds, callouts, YAML properties (frontmatter), tasks, highlights, and block references. Use whenever writing .md notes for a second brain / Obsidian vault so links resolve and metadata is queryable.

日本語の概要は準備中です。原文の説明を表示しています。

Design intentional internal link graphs for SEO, UX, and LLM-readable sites. Use this skill when the user asks for links between short briefs, longform articles, topics, projects, author pages, breadcrumbs, source trails, related stories, orphan-page checks, overlink checks, anchor intent, or validation that a link graph reinforces the canonical content model without creating duplicate story bodies or hidden links.

日本語の概要は準備中です。原文の説明を表示しています。

Navigation in React Native — both React Navigation v7 (classical, modular) and Expo Router (file-based, Expo 49+). Stack, tab, drawer navigators, deep linking, typed navigation, modal presentation, authentication flow patterns. Use this skill to: - Pick navigation lib based on what's installed (@react-navigation/* vs expo-router). - Configure typed routes with ParamList types or Expo Router's generated types. - Set up deep linking (URL schemes, Universal Links, App Links). - Build authentication flow with conditional navigators. - Use modal presentation correctly. Do NOT use this skill for: - Project structure (see rn-conventions). - Platform-specific differences (see rn-platform-specific). - State / storage (see rn-state-and-storage). - Testing navigation (see rn-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Fix Node.js CLI tools crashing inside Docker containers when host-installed node_modules require a newer Node version than the container provides. Use when: (1) "SyntaxError: Invalid regular expression flags" with /v flag in string-width or similar packages, (2) node_modules installed on host with Node 20+ but container has Node 18, (3) `npm install` with file: protocol creates symlinks that break inside Docker, (4) pnpm workspace packages become broken symlinks in containers. Covers version detection, Node binary mounting, and npm install strategies for cross-version compatibility.

日本語の概要は準備中です。原文の説明を表示しています。

Fix and verify iOS Universal Links, TestFlight deeplinks, AASA files, Expo Router callback URLs, associated domains, and sign-in returnTo flows in NowStack Mobile apps.

日本語の概要は準備中です。原文の説明を表示しています。

Launch a product across 56 platforms — generates all copy, tracks submissions, and guides launch day operations. Use this skill whenever someone wants to submit to directories, get backlinks, launch on Product Hunt or Hacker News, run an AppSumo campaign, or needs help getting their product in front of users. Also triggers on: 'I just built something and want people to know', 'how do I get users', 'where can I submit my SaaS', 'get backlinks for my product', 'multi-platform launch', 'directory submissions', 'startup launch playbook', 'submit everywhere', 'launch across platforms'. This is the operational launcher — it does the work. For high-level launch strategy and phased planning, see launch-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Find realistic link prospects with SERP and backlink evidence, discover contact paths via web tools, and draft personalized outreach — with targets saved to .seo/backlink-targets.json for off-page-seo campaigns. Use this skill when the user has a linkable asset (study, tool, guide, template, product page) and wants backlinks, resource-page inclusions, or comparison mentions. Triggers: "link prospecting", "find backlink opportunities", "resource page outreach", "get backlinks for", "link building outreach".

日本語の概要は準備中です。原文の説明を表示しています。

Call Exa Contents (POST /contents) for LLM-ready extraction from known URLs: text, highlights, summaries, links, image links, subpages, freshness-controlled crawl. Use when the agent already has URLs. Prefer Exa MCP web_fetch_exa when available; otherwise raw HTTP with EXA_API_KEY. NOT for open-ended discovery (use exa-search) or auth-walled X/Twitter (use mktg-x). For full-site crawl of a known domain, firecrawl may be better.

日本語の概要は準備中です。原文の説明を表示しています。

Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like "what do I know about X", "find notes related to Y", "what connects to Z", or "summarize my notes on W" — even when they never say NoteBrain, vector search, or ChromaDB.

日本語の概要は準備中です。原文の説明を表示しています。

Perform a reflective consolidation pass over a hyalo-managed knowledgebase directory — detecting structural issues, fixing broken links, flagging stale content, normalizing metadata, and reporting what changed. Use this skill when the user says /hyalo-tidy, "consolidate the knowledgebase", "clean up the KB", "run KB hygiene", "tidy", or "what needs attention in the knowledgebase". Also use when the user asks about knowledgebase health, broken links, orphan files, stale iterations, or metadata inconsistencies.

日本語の概要は準備中です。原文の説明を表示しています。

ブラウザを手足のように操る。ページ遷移、フォーム入力、スクショ、なんでもこい。Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include 'go to [url]', 'click on', 'fill out the form', 'take a screenshot', 'scrape', 'automate', 'test the website', 'log into', or any browser interaction request. Do NOT load for: sharing URLs, embedding links, screenshot image files.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

日本語の概要は準備中です。原文の説明を表示しています。

"Evaluate backlink quality using Domain Authority, Domain Rating, and trust metrics. Use this skill when the user needs to assess link profile health, identify toxic backlinks, or plan link building strategy — even if they say 'check my backlinks', 'link building', or 'domain authority analysis'.".

日本語の概要は準備中です。原文の説明を表示しています。

Detect documentation drift, stale references, and cross-document inconsistencies in any project. Scans for code-doc drift (API/function changes not reflected in docs), cross-doc drift (conflicting information across documents), and stale references (broken links, deleted files, outdated versions). Use when checking "doc freshness", "stale docs", "documentation drift", "broken links", "outdated documentation", "doc accuracy", "docs out of date", "doc audit", "doc health", or "verify documentation".

日本語の概要は準備中です。原文の説明を表示しています。