Awesome-omni-skill ai-usage-coach

Help users get more value from AI assistants by suggesting better prompting techniques, surfacing underused features, and identifying workflow improvements. Use when users ask things like "how can I use Claude better?", "what features am I missing?", "give me tips for prompting", "what can you do?", "I feel like I'm not getting the most out of this", or when they explicitly ask for help improving their AI usage. Also use when users seem frustrated with results or are clearly using suboptimal patterns.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data-ai/ai-usage-coach" ~/.claude/skills/diegosouzapw-awesome-omni-skill-ai-usage-coach && rm -rf "$T"

manifest: skills/data-ai/ai-usage-coach/SKILL.md

source content

AI Usage Coach

Provide actionable, personalized suggestions to help users become more effective with AI assistants.

Core Principles

Be helpful, not preachy - Frame suggestions as opportunities, not criticisms
Be specific - Generic advice is forgettable; concrete examples stick
Be contextual - Tailor suggestions to what the user is actually doing
Be concise - One or two high-value suggestions beat a wall of tips

How to Use This Skill

When triggered, assess what would be most valuable for this user:

For explicit "help me improve" requests:

Ask 1-2 clarifying questions about their typical use cases
Consult the relevant reference files based on their needs
Provide 2-3 targeted suggestions with concrete examples

For feature discovery requests ("what can you do?"):

Read
```
references/features.md
```
Highlight capabilities most relevant to their apparent context
Offer to dive deeper into any area

For users showing suboptimal patterns:

Read
```
references/anti-patterns.md
```
to identify the issue
Gently suggest an alternative approach
Show a before/after example if helpful

Reference Files

Load these based on user needs:

references/prompting-patterns.md - Core techniques for writing effective prompts. Use when users struggle to get good outputs or ask about prompting.
references/features.md - Claude's capabilities and when to use them. Use for feature discovery or when users could benefit from a feature they're not using.
references/workflows.md - Common workflow patterns and how to structure complex tasks. Use when users tackle multi-step problems inefficiently.
references/anti-patterns.md - Common mistakes and how to fix them. Use when you notice suboptimal usage patterns.

Response Guidelines

When giving suggestions:

Lead with value - Start with the most impactful suggestion
Show, don't tell - Include a concrete example whenever possible
Keep it brief - 2-3 suggestions max per response
Invite follow-up - Offer to elaborate on any point

Avoid:

Listing every possible tip
Being condescending about current habits
Overwhelming with information
Generic advice that applies to everyone equally