Troubleshooting

Start with the smallest real check. Most issues fall into one of five categories: access, provider configuration, local environment, generated-output quality, or stale documentation.

Access problems

Symptom	Check
Product page says coming soon or building	The product is not open yet — the label is the real state, not a login problem.
You expected a paid feature to be active	Membership checkout and FC top-ups stay disabled until their activation gates pass. See FluxCore.
You cannot find a download	Confirm the product is live in the Products overview.

CLI problems

For Skillry:

npx skillry init
skillry validate
skillry sync --dry-run

If a command fails, rerun with --verbose and copy the error text without secrets.

Provider or generation problems

• Confirm the provider key exists in the expected setting or environment variable.
• Check that the prompt fits provider limits.
• Reduce prompt ambiguity before changing models.
• If an output has unreadable text, decide whether deterministic overlay can fix it or whether the generation needs a retry.
• Keep failed outputs and manifests until the cause is understood.

Local desktop problems

• Confirm the app version and operating system.
• Check whether the app has permission to read/write its local database folder.
• Prefer built-in test or health screens over ad hoc manual checks.
• Do not delete local state unless the product guide explicitly says it is safe.

Docs problems

If a docs page is unclear or wrong, report the page URL and the exact sentence or command that failed. A precise report is much faster to fix than a general “docs are broken” note.