Troubleshooting

Most issues fall into one of these. If yours isn’t here, ask in the team channel.

”Claude can’t reach the repository” during install

This has two distinct causes — check both:

1. GitHub access isn’t finished. Check your email for a GitHub invitation to unicorn-marketers/um-toolkit and click Accept invitation. Confirm with your admin that they added your exact GitHub username. You can self-check by opening github.com/unicorn-marketers/um-toolkit in a browser while signed in — if you see a 404, access isn’t active yet.
2. The machine isn’t signed in to GitHub. On the desktop app, run gh auth login in a terminal (choose GitHub.com → HTTPS → sign in with browser) so the plugin command can authenticate. Then run the install command again.

”I authorized GitHub but Cowork still can’t see the repo”

Authorizing proves who you are; a private repo also needs more:

1. The Claude GitHub App must be installed on the repository (an admin does this once). Without it, Cowork can verify you but cannot sync a private repo.
2. If your organization uses SSO, your GitHub session may need to be authorized for the org — open the repo in a browser and follow any “authorize” banner.
3. Confirm you actually accepted the repo invitation (cause #1 above).

If the repo still won’t appear, ask the repo admin to install the Claude GitHub App on unicorn-marketers/um-toolkit, or install on the desktop app instead. (Teams on a Claude for Work workspace have a third option: an org admin can add the toolkit as an organization plugin so it appears for everyone — personal accounts don’t have that menu.)

The skills don’t show up after installing

1. Make sure the install step actually finished (/plugin install um-toolkit@unicorn-marketers on desktop, or the Install button in Cowork).
2. Reload or restart the app (on desktop, /reload-plugins does it without restarting).
3. On the desktop app, skills are named with the toolkit prefix, like um-toolkit:apollo. Type /um-toolkit to see them all.
4. Still nothing? Ask: “What um-toolkit skills can you use?”

A skill stopped and asked for an API key

That’s by design: rather than ship a broken or placeholder file, image and video skills stop when a key is missing. Add the key it names by following Connect your API keys, then run it again.

”I asked for an image (or video) in Cowork and nothing rendered”

Cowork can’t generate finished images or video yet, because of a sandbox limit on outside services. Use the Claude Code desktop app for anything that renders a finished image, video, or full page. Cowork is still great for everything in the research, copy, strategy, and review group.

”Research can’t run here”

The research skill (apollo) needs a live web connection. Both Cowork and the desktop app have one, so this usually means web access is temporarily unavailable. Try again, or paste the source material in directly and ask it to work from that.

The output feels generic, like it could be any brand

This is almost always thin brand files. The fix:

1. Re-run onboarding and give richer answers.
2. Paste in 3 to 5 real examples of your brand’s actual writing (tweets, an email, a sales-page paragraph). Voice samples are the single biggest lever on how “you” the output sounds.

It made something up, or got a fact wrong

The toolkit is built to flag gaps instead of inventing facts, but always sanity-check specific numbers, quotes, and claims before anything goes live. If a skill ever presents a number without a source, ask it to cite the source or mark it as unverified.