Skip to content
SkillCheatSheet Sign in

voyager-crew/voyager

Agent skills in the GitHub repository voyager-crew/voyager, each with its code score out of 100.

Enhancement suite for Gemini, AI Studio, Claude, ChatGPT & DeepSeek — plus a prompt manager for any website, DeepSeek Harness included. / 面向 Gemini、AI Studio、Claude、ChatGPT 与 DeepSeek 的增强套件;其中的提示词管理器可用于任意网站,如 DeepSeek Harness。

Repository score
60 / 100 C
Skills
9
Verified
0
Average skill score
61
GitHub stars
20,605
License
GPL-3.0

Open voyager-crew/voyager on GitHub

9 skills in this repository

  1. create-voyager-plugin

    Create or change a Voyager declarative plugin, site adapter, or native primitive.

    66C
  2. writing-docs

    Sets the standard for Voyager's guide pages and their screenshots. Use when editing or adding a page under docs/guide/ or any locale's docs/<lang>/guide/, or when taking or replac…

    66C
  3. release

    Prepare, publish, or recover a Voyager release. Use for version bumps and releases, failed store submissions, or Safari release failures.

    65C
  4. verify-in-browser

    Proves a Voyager change on the live host page and shows the evidence as screenshots. Use after changing content scripts, injected CSS, MAIN-world scripts or plugin site code, when…

    65C
  5. write-voyager-plugin

    Voyager plugin authoring: write and check a local plugin (a JSON manifest plus CSS) for the Voyager browser extension. Use when the user wants to change how Gemini, AI Studio, Cha…

    65C
  6. voyager-contribute

    Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

    64C
  7. update-safari-extension

    Build, reload, and verify Voyager in Safari for web-extension changes, native integration, or signed-app testing while preserving installed apps and extension data.

    58C
  8. issue-review

    Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.

    53D
  9. pr-description

    Write or rewrite a Voyager pull request description.

    44D

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.