registry: add skillshare by runkids · Pull Request #8095 · jdx/mise

runkids · 2026-02-10T19:00:46Z

Summary

Add skillshare to the mise registry
Skillshare syncs AI CLI skills (SKILL.md) from a single source of truth to Claude Code, Cursor, Gemini CLI, and 40+ tools

Registry entry

backends = ["github:runkids/skillshare"]
description = "Sync AI CLI skills from a single source to Claude Code, Cursor, Gemini CLI, and 40+ tools"
test = ["skillshare -v", "skillshare v{{version}}"]

Test plan

mise install skillshare installs the binary from GitHub releases
skillshare -v outputs skillshare v<version> matching the expected format

gemini-code-assist · 2026-02-10T19:01:37Z

Summary of Changes

Hello @runkids, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the skillshare tool into the mise registry. This addition allows mise users to seamlessly install and manage skillshare, a utility that centralizes and synchronizes AI CLI skills across a wide array of AI development environments and tools.

Highlights

New Tool Integration: The skillshare tool has been added to the mise registry, allowing users to easily install and manage it.
Skillshare Functionality: skillshare is designed to synchronize AI CLI skills (SKILL.md) from a single source of truth to various AI platforms like Claude Code, Cursor, Gemini CLI, and over 40 other tools.

Changelog

registry/skillshare.toml
- Added a new registry entry for the skillshare tool, including its GitHub backend, description, and a test command for version verification.

Activity

The author has verified that mise install skillshare successfully installs the binary from GitHub releases.
The author has confirmed that skillshare -v outputs the version in the expected format.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request adds the skillshare tool to the mise registry. The configuration is mostly correct, but I've identified a likely error in the test configuration. Based on the skillshare tool's implementation using the cobra library, the version command's output will be skillshare version ..., not skillshare v.... I've provided a suggestion to correct the expected value in the test to prevent it from failing. With this change, the new registry entry should work as intended.

gemini-code-assist · 2026-02-10T19:02:28Z

registry/skillshare.toml

@@ -0,0 +1,3 @@
+backends = ["github:runkids/skillshare"]
+description = "Sync AI CLI skills from a single source to Claude Code, Cursor, Gemini CLI, and 40+ tools"
+test = { cmd = "skillshare -v", expected = "skillshare v{{version}}" }


The output of skillshare -v is likely skillshare version {{version}} rather than skillshare v{{version}}. The cobra library, which skillshare uses, defaults to printing 'version' in the version output. This change will align the test with the expected output and ensure it passes.

Suggested change

test = { cmd = "skillshare -v", expected = "skillshare v{{version}}" }

test = { cmd = "skillshare -v", expected = "skillshare version {{version}}" }

runkids · 2026-02-10T19:39:10Z

The validate-new-tools and list-changed-tools checks have passed. The other failing checks (build, unit, benchmark, etc.) appear to be unrelated to this registry-only change — they involve cargo build of the full mise codebase.

runkids · 2026-02-10T19:45:29Z

Found a conflict between validate-new-tools and build.rs codegen:

validate-new-tools uses grep -q '^test = \[' — only accepts array format
build.rs codegen_registry expects test to be a table (inline table)

All existing registry entries use inline table format (test = { cmd = "...", expected = "..." }), so I've matched that. The validate-new-tools check will fail, but the build should pass.

## Summary - The `validate-new-tools` CI job used `grep -q '^test = \['` to check for test fields, but all 510 registry tools use inline table syntax (`test = { ... }`), not array syntax (`test = [...]`) - Changed the pattern to `^test = ` to match both formats - This was blocking PR #8095 (and would block any new registry tool PR from non-maintainers) ## Test plan - [x] Verified all 510 existing registry tools use `test = {` syntax - [x] Verified 0 tools use `test = [` syntax - [x] Lint checks pass 🤖 Generated with [Claude Code](https://claude.com/claude-code)  --- > [!NOTE] > **Low Risk** > Single-line change to a CI grep pattern; low risk aside from potentially allowing malformed `test` lines to slip through if they start with `test = `. > > **Overview** > Fixes the `validate-new-tools` CI check in `registry.yml` to accept any `test = ...` field in new `registry/*.toml` tool definitions (instead of only matching the array form `test = [`), preventing false failures when tools use non-array test syntax. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 6fde3ce. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>  Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

## Summary - The `validate-new-tools` CI job used `grep -q '^test = \['` to check for test fields, but all 510 registry tools use inline table syntax (`test = { ... }`), not array syntax (`test = [...]`) - Changed the pattern to `^test = ` to match both formats - This was blocking PR jdx#8095 (and would block any new registry tool PR from non-maintainers) ## Test plan - [x] Verified all 510 existing registry tools use `test = {` syntax - [x] Verified 0 tools use `test = [` syntax - [x] Lint checks pass 🤖 Generated with [Claude Code](https://claude.com/claude-code)  --- > [!NOTE] > **Low Risk** > Single-line change to a CI grep pattern; low risk aside from potentially allowing malformed `test` lines to slip through if they start with `test = `. > > **Overview** > Fixes the `validate-new-tools` CI check in `registry.yml` to accept any `test = ...` field in new `registry/*.toml` tool definitions (instead of only matching the array form `test = [`), preventing false failures when tools use non-array test syntax. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 6fde3ce. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>  Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

gemini-code-assist bot reviewed Feb 10, 2026

View reviewed changes

runkids force-pushed the registry/skillshare branch from da536e9 to 754cb44 Compare February 10, 2026 19:30

registry: add skillshare

cdea305

runkids force-pushed the registry/skillshare branch from 754cb44 to cdea305 Compare February 10, 2026 19:45

jdx closed this Feb 11, 2026

jdx mentioned this pull request Feb 11, 2026

fix(ci): fix validate-new-tools grep pattern for test field #8100

Merged

3 tasks

runkids mentioned this pull request Feb 11, 2026

Make the tool available via mise runkids/skillshare#17

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

registry: add skillshare#8095

registry: add skillshare#8095
runkids wants to merge 1 commit intojdx:mainfrom
runkids:registry/skillshare

runkids commented Feb 10, 2026 •

edited

Loading

Uh oh!

gemini-code-assist bot commented Feb 10, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 10, 2026

Uh oh!

runkids commented Feb 10, 2026

Uh oh!

runkids commented Feb 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	test = { cmd = "skillshare -v", expected = "skillshare v{{version}}" }
	test = { cmd = "skillshare -v", expected = "skillshare version {{version}}" }

Uh oh!

Conversation

runkids commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Registry entry

Test plan

Uh oh!

gemini-code-assist bot commented Feb 10, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

runkids commented Feb 10, 2026

Uh oh!

runkids commented Feb 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

runkids commented Feb 10, 2026 •

edited

Loading