Claude Skill Not Working? Here's How to Fix It

You enabled the Gmail Skill, it showed as Connected, and now Claude is just answering from its training data like you never set anything up. Or it throws a vague error. Or it says it can't access your calendar. These issues are common — and almost always fixable in under five minutes.

Problem 1: Claude Ignores the Skill and Answers Normally

This is the most common complaint. You have the Skill connected, but Claude doesn't use it. It just gives you a generic answer based on training data instead of actually checking your inbox or searching the web.

Fix: Be explicit in your prompt. Instead of "what emails do I have?", say: "Using my Gmail, show me unread emails from today." Instead of "find recent AI news," say: "Search the web for AI news published in the last 48 hours."

Claude uses Skills when it recognizes the intent clearly. The more ambiguous your prompt, the more likely Claude defaults to its own knowledge. Adding the name of the Skill or the service name removes ambiguity entirely.

Problem 2: The Skill Shows Connected But Returns an Error

You see "Connected" in Settings → Integrations, but when you try to use the Skill, Claude returns an error like "I couldn't access your Gmail" or "authorization failed."

Fix — Step 1: Go to Settings → Integrations and check when you last connected the Skill. OAuth tokens expire. If it's been several months, the token may have expired even though the UI still shows Connected.

Fix — Step 2: Click Disconnect on the Skill, then reconnect it fresh by clicking Connect and going through the OAuth flow again. This generates a new token and is the fix for 80% of authorization issues.

Problem 3: The OAuth Authorization Didn't Complete

Sometimes the OAuth popup closes before you finish authorizing — maybe you clicked away, or the browser blocked the popup. The Skill appears in a half-connected state.

Fix: Go to Settings → Integrations, find the Skill showing a partial or error status, click Disconnect, then click Connect again. This time, make sure you fully complete the Google/Notion/Shopify authorization screen before closing anything. Don't close the popup early.

Also, if your browser has a popup blocker, it may have silently blocked the authorization window. Check your browser's notification bar for a "popup blocked" message and allow it.

Problem 4: The Skill Isn't Available on Your Plan

Some Skills are Pro-only. If you're on the free tier and trying to enable Gmail, Calendar, Notion, or Shopify, they simply won't be available in the Skills library — or they'll show with a "Pro required" indicator.

Fix: Check what plan you're on at Settings → Account. If you want access to integration Skills, upgrade to Claude Pro ($20/month). The free Claude Skills guide shows exactly what's available without upgrading.

Problem 5: Third-Party Service Is Down

Claude's Skills rely on the API of the service they connect to — Google's API for Gmail and Calendar, Notion's API for Notion, Shopify's API for Shopify. If that API is having issues, the Skill will fail even though Claude and the connection are both fine.

Fix: Check the status page for the affected service. Google Workspace status is at workspace.google.com/status. Notion's status is at notion.statuspage.io. If there's a reported incident, wait for it to resolve — Claude's Skill isn't broken, the service it's talking to is temporarily unavailable.

Problem 6: Claude Rate-Limited the Skill

If you've been sending a lot of Skill-invoking prompts in quick succession, Claude may hit rate limits — either its own or the third-party service's. You'll typically get an error message or a response saying it couldn't complete the action.

Fix: Wait a few minutes and try again. Free tier users have lower rate limits than Pro users. If this happens frequently, consider batching your Skill requests into fewer, more comprehensive prompts rather than many individual ones.

Problem 7: Browser Extension Interference

Some browser extensions — especially privacy-focused ones like uBlock Origin, Privacy Badger, or certain VPN extensions — can interfere with OAuth redirects or block the Skill's API calls.

Fix: Try using Claude.ai in a private/incognito window, which typically disables extensions. If the Skill works there but not in your normal window, an extension is the culprit. Try temporarily disabling extensions one by one to identify which one is causing the conflict, then whitelist claude.ai in that extension's settings.

Quick Diagnostic Checklist

Run through this when a Skill isn't working:

1. Is the Skill showing "Connected" in Settings → Integrations?
2. Did you complete the full OAuth flow when connecting?
3. Are you on a plan that includes this Skill?
4. Is the prompt explicit enough — does it name the service?
5. Is the third-party service currently up?
6. Have you tried disconnecting and reconnecting?
7. Have you tried in a private browser window?

If you've gone through all seven steps and the Skill still doesn't work, it's worth checking Anthropic's status page and the community forums for any known issues with that specific Skill.