proactive-assistance

Anticipate user needs and offer help before being asked

インストールへ移動

リポジトリ: fabioc-aloha/Alex_Plug_In
ソースの最終更新活動: 2026年4月15日 05:03
検出された SKILL.md の言語: 英語
スター: 5
フォーク: 3

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

検索に戻るインストールに戻る

name	proactive-assistance
description	Anticipate user needs and offer help before being asked
tier	core
applyTo	*/proactive,/anticipate,/suggest*
user-invokable	false

Proactive Assistance Skill

Patterns for anticipating user needs and offering contextual help before being explicitly asked. The hallmark of an AI partner vs. a reactive tool.

Core Philosophy

"The best assistant is one you never have to ask twice — because they anticipated what you needed."

Proactive assistance walks a fine line:

Too little: User feels alone, has to ask for everything
Too much: User feels interrupted, micromanaged
Just right: User feels supported, understood, efficient

Mental Model

┌─────────────────────────────────────────────────────────┐
│                  PROACTIVE SPECTRUM                      │
├──────────┬──────────┬──────────┬──────────┬─────────────┤
│ REACTIVE │ AWARE    │ READY    │ SUGGEST  │ ANTICIPATE  │
│          │          │          │          │             │
│ Wait for │ Notice   │ Prepare  │ Offer    │ Act before  │
│ explicit │ patterns │ likely   │ relevant │ need is     │
│ request  │ & signals│ needs    │ help     │ conscious   │
└──────────┴──────────┴──────────┴──────────┴─────────────┘
     ←── Tool                               Partner ──→

Signal Category	Examples	Proactive Response
Repeated patterns	User asks same thing 3x	"I notice you check X often. Want me to surface that automatically?"
Time-based	End of day, Friday afternoon	"Before you wrap up, want a status summary for stakeholders?"
Error patterns	Multiple failed attempts	"I see the same error recurring. Want me to research solutions?"
Complexity growth	File/PR getting large	"This is getting complex. Want me to suggest breaking points?"
Idle after success	User pauses after completing	"Nice work! What's next — docs, tests, or another feature?"
Context switch	User opens different project	"Switching contexts. Want me to summarize where you left off here?"

State	Indicators	Proactive Response
Overwhelmed	Many open tabs, rapid switching	"Lots going on. Want me to prioritize the top 3?"
Stuck	Long pause, repeated attempts	"You've been on this a while. Fresh perspective?"
Rushing	Fast typing, short messages	"Moving fast today. I'll keep responses brief."
Learning	Exploratory questions	"Curious about this? I can explain the broader context."
Wrapping up	Commit messages, cleanup	"Looks like you're finishing up. Anything to document?"

"I notice you've been debugging this for a while. 
Would it help if I traced the data flow?"

"I've drafted a PR description based on your commits — 
ready when you need it."

"Since you're updating the API, want me to check 
if the docs need updates too?"

"Third time this week you've needed this query. 
Want me to save it as a snippet?"

"Before switching: current PR is ready for review, 
tests passing, 2 TODOs marked for later."

"Heads up: this change might affect the mobile layout. 
Want me to check?"

// From user-profile.json
{
  "proactiveSuggestions": true,  // Master switch
  "questionFrequency": "moderate", // minimal | moderate | frequent
  "detailLevel": "balanced" // Affects suggestion depth
}

Anti-Pattern	Why It's Bad	Better Approach
Constant suggestions	Feels like nagging	Batch suggestions, wait for pauses
Repeating dismissed help	Ignores user preference	Track rejections, back off
Acting without asking	Violates trust	Always offer, never force
Generic suggestions	Not valuable	Make them context-specific
Interrupting flow	Breaks concentration	Wait for natural breakpoints