Skip to main content
If a skill doesn’t appear in the @ picker dropdown when you type its name:
  1. For Official Library skills — the skill must be installed before it appears in the picker. Go to Settings → Skills → Official Library, find the skill, and click Install.
  2. For custom skills — confirm the skill was saved successfully. Go to Settings → Skills → Custom and look for it in the list. If it’s there, it should appear in the @ picker.
  3. Check the skill name — the @ trigger is the skill’s exact name. If you named it code-review, you must type @code-review (not @codeReview or @code_review).
  4. Try refreshing the page — if you just installed or created a skill, a page refresh may be needed before it shows in the picker.
  5. Check for typos in the name — open the skill in Settings → Skills and verify the exact trigger name.
If invoking the same skill with similar inputs produces different formats or quality each time:
  1. Add more specific instructions to the system prompt — vague instructions produce variable results. Replace soft guidelines with explicit rules: 
    // Vague
"Summarize the text"

// Specific
"Summarize in exactly 4 bullet points. Each bullet must be under 20 words.
Start each bullet with a noun or verb. Return only the bullets — no intro."
  2. Add an output example — include a sample of the exact format you want directly in the system prompt. This is the single most effective way to improve format consistency.
  3. Use a lower-temperature or reasoning model — creative/generative models introduce more variation. For format-sensitive tasks, switch to a more consistent base model in the skill’s settings.
  4. Reduce scope — if the skill is trying to do too much, split it into two focused skills. Simpler instructions are followed more reliably.
If a skill isn’t using the tools you configured for it (e.g., not searching the web even though web search is enabled):
  1. Verify tools are enabled — go to Settings → Skills → [skill name] → Edit → Tools. Confirm the tools are toggled on.
  2. Re-save after changes — if you recently toggled a tool, make sure you clicked Save. Changes don’t take effect until saved.
  3. Be explicit in the skill prompt — add an instruction telling the skill to use the tool: “Use web search to find current information before answering.” Tools don’t always activate automatically from the trigger alone.
  4. Test in the preview pane — use the built-in preview to verify the tool activates during a test run before invoking the skill in a real chat.
If a GitHub-imported skill isn’t working after import:
  1. Check that the repo has a valid skill configuration file — the repo must contain a skill.json (or compatible format) with the required fields. See Import from GitHub for the expected format.
  2. Verify repo accessibility — if the repo is private, confirm you have access to it (your GitHub account must be authorized). Public repos should be accessible without authentication.
  3. Re-import after updates — ZeroTwo doesn’t auto-sync with source repos. If the config was recently updated in the repo, go to Settings → Skills → GitHub Import and re-import from the same URL.
  4. Check for JSON syntax errors — if the skill.json file has a syntax error, the import may silently fail or import incomplete data. Validate the JSON at jsonlint.com before importing.
  5. Try the import URL again — paste the exact GitHub repository URL (not a link to a specific file) into the import field and try again.
Depending on the skill type:
  • Official Library skills cannot be edited — they’re provided by ZeroTwo as-is. If you need custom behavior, create a new custom skill with your preferred system prompt instead. To remove an official skill from your picker, uninstall it: Settings → Skills → Installed → Remove.
  • Custom skills can be edited — go to Settings → Skills → Custom → [skill name] → Edit. Make changes and click Save.
  • GitHub-imported skills — these are treated as custom skills after import and can be edited in the Custom tab. Note that edits won’t sync back to the source repo.
If you’re unable to edit or delete a custom skill you own:
  1. Refresh the page
  2. Log out and back in
  3. Contact ZeroTwo support if the issue persists

​
Getting More Help

If an issue isn’t resolved:
  • Review Create a Skill for system prompt best practices
  • Review Testing Skills for iteration techniques
  • Contact ZeroTwo support with the skill name, your system prompt, a sample input, and a description of the unexpected output