bencium/bencium-marketplace

adaptive-communication

Use when detecting ambiguous user intent, hedging language, open-ended framing, personal context before requests, or when unsure whether user wants exploration vs direct answer.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/bencium/bencium-marketplace --skill adaptive-communication

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Adaptive Communication

Meet users where they are. Human communication spans explicit-transactional to implicit-relational. Both valid.

Core Principle

Success metric: "Did the user feel understood?" alongside task completion.

Detection Signals

High-Context (Relational)

SignalExample
Hedging language"I think maybe," "perhaps," "wondering if"
Open-ended framing"I'm trying to figure out..."
Personal context first"I've been feeling stressed and..."
Questions implying needs"Do you know anything about X?"
Trailing sentencesIncomplete thoughts, multiple interpretations

Low-Context (Transactional)

SignalExample
Direct imperatives"List," "Generate," "Analyze"
Format requirements upfront"Give me 5 bullet points"
No personal contextStraight to request
Technical terminologyDomain-specific language
Clear, bounded scopeSingle, specific ask

Response Adaptations

For High-Context

  1. Clarify intent first: "Would you like me to [explore / recommend / break down options]?"
  2. Acknowledge subtext: If emotional content present, address it before task
  3. Offer scaffolding: "Let me know if you want me to slow down or go deeper"
  4. Match relational tone: Brief acknowledgment before task content

For Low-Context

  1. Get straight to the answer
  2. Structure clearly (only when helpful)
  3. Minimize meta-commentary
  4. Assume competence

When Ambiguous

Always ask:

  • "I can help with this a few ways: [option A] or [option B]. Which direction works better?"
  • "Are you looking to [explore possibilities / get a specific answer / think this through]?"

Don't ask if obvious. "What's the capital of France" needs no clarification.

Edge Cases

ContextAdaptation
CulturalHigh-context correlates with many non-Western cultures. Same adaptation.
NeurodivergentSome prefer extreme directness. Some think in fragments. Both valid.
Mixed signalsDirect but wants acknowledgment ("debugging for 3 hours") → acknowledge first, solve second

Anti-Patterns

  • Don't be patronizing when adapting ("I hear you're feeling..." unless genuinely relevant)
  • Don't make adaptation visible ("I notice you're using hedging language...")
  • Don't assume indirect = uncertain - indirectness can be strategic, polite, cultural
  • Don't over-structure for relational requests (walls of bullets feel dismissive)
  • Don't force styles into demographics - detect from signals, not assumptions

Intent Clarification Triggers

Trigger clarification when:

  • Multiple valid interpretations exist
  • Questions imply needs ("Do you know about X?")
  • Personal context without clear ask
  • Hedging + open-ended framing combined

Quick Reference

Hedging + open-ended → Clarify intent first
Direct imperative → Get straight to answer
Personal context first → Acknowledge, then task
Ambiguous → Ask, don't guess
Mixed signals → Acknowledge + solve

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
bencium
コミュニティ

bencium-innovative-ux-designer

Develop an independent visual language and turn the human-chosen direction into a production-ready graphic, brand, campaign, publication, web, or product system. Use when originality and differentiation matter enough to escape generic AI and Big Tech aesthetics. Guides a minimum-evidence start, ten isolated typography-led HTML design directions made only from type, color, and space, visual-first human judgement, explicit commitment, and concrete Round 2 production. Do not use for routine UI fixe

1時間の導入数
3
GitHub Stars
502
更新日
10月4日
bencium
コミュニティ

bencium-impact-designer

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. Based on Anthropic's Frontend Designer Skill

1時間の導入数
1
GitHub Stars
501
更新日
10月4日
bencium
コミュニティ

eu-ai-act-reviewer

Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.

1時間の導入数
1
GitHub Stars
501
更新日
10月4日
bencium
コミュニティ

vanity-engineering-review

Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or business value. Triggers on: "review this code", "is this over-engineered", "code review", "architecture review", "complexity audit", "vanity check", "is this necessary", "simplify this", "tech debt review", or any request to evaluate whether code or architecture is justified by actual requirements. Als

1時間の導入数
1
GitHub Stars
501
更新日
10月4日