Support

Stuck? Write in. We'll sort it.

If the skill won't install, the download broke, or something isn't working the way the product page said it would, reach out. Leave your order ID, the email you used at checkout, and a note about what's happening, and we'll get back to you as soon as we can.

The fastest way to get help

Open a support ticket.

Send an email to the address below, or open a ticket directly in our help center. Either route creates a tracked ticket so nothing falls through the cracks, including weekends.

Include your order ID, email used at checkout, and what's going on
Before you write in

Try these first. Two minutes each.

Most support tickets we get are about the same handful of issues. Check these before you open a ticket. If the fix is here, you're back to building in a couple of minutes. If it isn't, write in and we'll take it from there.

The skill won't upload into Claude.

A few things to check, in order:

  1. Make sure you uploaded the ZIP, not the unzipped folder. Claude wants the archive file, not the contents. If your browser auto-unzips downloads, you'll need to re-zip the folder before uploading.
  2. Check that Code execution is enabled. In Claude, go to Settings, then scroll to the Code execution section, and toggle it on. Skills need this to run.
  3. Check your plan's skill capacity. Free plans have a limit on the number of installed skills. If you're at the cap, you'll need to remove one before adding another.

If you've checked all three and it's still failing, open a ticket with the exact error message Claude shows you. A screenshot helps.

I paid but didn't get the download email.

Check your spam folder first, then your Promotions tab if you use Gmail. The email comes from hello@wisemindcraft.com within a minute of checkout.

If it's not there after ten minutes, open a ticket with the email address you used at checkout and your Stripe order ID (it's on your receipt). We'll resend manually.

The download link expired.

Download links are time-limited for security. If yours has expired, reach out with your order ID and we'll issue a fresh one as soon as we can.

The skill installed but isn't triggering.

Skills trigger based on the language you use in your prompt. If you're asking for something like "help me write an ebook," the skill should activate. If it isn't:

  1. Start a fresh chat. Claude sometimes caches skill state. A new chat forces a clean load.
  2. Reference the skill by name. Try "Run the Content Creation Atelier" or "Use NAPS to help me define my audience." Explicit invocation is always recognized.
  3. Check the skill is actually installed. Go to Customize, then Skills, and confirm the skill appears in the list.

If it's installed and still not triggering on explicit invocation, open a ticket with your prompt and Claude's response. That helps us diagnose whether the issue is in the skill or in the trigger pattern.

I want to request a refund.

Read the refund policy first so you know where we land on this. The short version: because these are instant-access digital downloads, refunds aren't offered by default. But if something doesn't work as described, we make it right.

If that's your situation, open a ticket with your order ID and a brief description of what broke. We'll handle it.

I want to update my email address or login.

Account self-service is in progress and rolling out soon. In the meantime, open a ticket with your old email, your new email, and your order ID, and we'll update it manually.

I found a bug in one of the skills.

Thank you. Please open a ticket with:

  • The skill name
  • What you asked Claude to do
  • What Claude produced (paste the output)
  • What you expected

Bug reports with all four pieces get fixed fastest. These go into the backlog for the next update, and as a suite buyer you get those updates free for 12 months.

I have a question about how to use a skill.

Open a ticket with the skill name and your question. Usage questions go to the front of the queue because they're often a quick answer. If we notice the same question showing up across multiple tickets, it becomes a new entry in the onboarding documentation.

When you write in

Include these five things.

Tickets with complete context get resolved in hours. Tickets without make us ping back and forth for a day or two. This list saves everyone time.

Support ticket checklist

What to include in your first message

  • Your order ID. You'll find it on your Stripe receipt email. It starts with ch_ or pi_.
  • The email you used at checkout. That's how we find your record.
  • What you were trying to do. One sentence is fine. "I was installing the Creation Suite ZIP into Claude."
  • What actually happened. The exact error message, or a description of what went wrong. Quote the text if you can.
  • A screenshot if relevant. Especially for install errors or broken pages, a screenshot cuts diagnosis time in half.
Honest scope

What support covers, and what it doesn't.

Support covers

Getting you unstuck with our products.

  • Install and upload issues with any skill
  • Broken, expired, or missing download links
  • Files that don't open or fail validation
  • Account, login, and access issues
  • Questions about how a specific skill works
  • Bug reports and behavior that doesn't match the docs
  • Update questions and version history
  • Receipt, billing, and refund questions
Out of scope

Things support can't help with.

  • Claude account issues (contact Anthropic support)
  • Stripe payment processing problems on Stripe's side
  • General AI coaching or prompt engineering consulting
  • Customizing a skill to behave differently than its spec
  • Feedback on work you produced using the skills
  • Marketing, business, or strategy advice
  • Third-party tool integrations not mentioned in the docs
  • Requests to build features on demand