Skip to content

Comments

chore: replace ascii-box-check with skillshare skill in hub registry#3

Merged
runkids merged 4 commits intomainfrom
modify-default-skill
Feb 12, 2026
Merged

chore: replace ascii-box-check with skillshare skill in hub registry#3
runkids merged 4 commits intomainfrom
modify-default-skill

Conversation

@runkids
Copy link
Owner

@runkids runkids commented Feb 12, 2026

Remove ascii-box-check skill and add the built-in skillshare skill for installing, searching, and managing skills from the hub.

Remove ascii-box-check skill and add the built-in skillshare
skill for installing, searching, and managing skills from the hub.
@gemini-code-assist
Copy link

Summary of Changes

Hello @runkids, I'm Gemini Code Assist1! 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 refines the skill registry by removing an outdated entry and integrating a new, foundational built-in skill. This change aims to streamline the available skills and enhance the platform's core functionality for skill management.

Highlights

  • Skill Removal: The 'ascii-box-check' skill has been removed from the 'skillshare-hub.json' registry.
  • Skill Addition: The 'skillshare' built-in AI skill has been added to the 'skillshare-hub.json' registry, providing capabilities for installing, searching, and managing skills from the hub.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • skillshare-hub.json
    • Removed the 'ascii-box-check' skill entry.
    • Added the 'skillshare' skill entry, including its description, source, and relevant tags.
Activity
  • No specific activity (comments, reviews) has been recorded for this pull request yet.
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.

Footnotes

  1. 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request replaces the ascii-box-check skill with the new skillshare skill in the hub registry. The change is straightforward, but the new skillshare entry introduces a data format for defining a skill's source that is inconsistent with other entries in the file. I've suggested a change to align it with the existing format to improve the maintainability and consistency of the hub file.

Comment on lines +13 to 22
{
"name": "skillshare",
"description": "Built-in AI skill for skillshare – helps install, search, and manage skills from the hub",
"source": "https://github.com/runkids/skillshare/tree/main/skills/skillshare",
"tags": [
"skillshare",
"agent",
"skill"
]
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with other entries in this file, I suggest defining the source and skill properties for the new skillshare skill using the established owner/repo pattern. The current use of a full URL for source and the omission of the skill property introduces a new format, which can make parsing and maintenance of this file more complex. Adhering to a single pattern improves maintainability.

    {
      "name": "skillshare",
      "description": "Built-in AI skill for skillshare – helps install, search, and manage skills from the hub",
      "source": "runkids/skillshare",
      "skill": "skillshare",
      "tags": [
        "skillshare",
        "agent",
        "skill"
      ]
    }

The audit script now handles all source formats:
- GitHub browser URL: https://github.com/owner/repo/tree/branch/path
- GitHub domain shorthand: github.com/owner/repo/path
- GitHub shorthand: owner/repo/path
- Plain HTTP URLs (non-GitHub)

For sources with subpaths, only the subdirectory is audited
instead of the entire cloned repo.
- Remove skillshare init workaround (path mode no longer needs config)
- Switch audit.sh from sed/awk text parsing to --json + jq for
  reliable risk extraction
- Add Gitea/Forgejo URL parsing (src/branch/ pattern) for non-GitHub
  skill sources
- Add duplicate source validation in validate.sh
@runkids runkids force-pushed the modify-default-skill branch from c32871d to b18c28e Compare February 12, 2026 18:06
@runkids runkids merged commit da16dcf into main Feb 12, 2026
2 checks passed
@github-actions
Copy link
Contributor

Skill Audit Results

Source Status Risk
https://github.com/runkids/skillshare/tree/main/skills/skillshare ✅ Passed CLEAN (0/100)

All skills passed the security audit.

Audit Details

https://github.com/runkids/skillshare/tree/main/skills/skillshare

Risk: CLEAN (0/100)

@runkids runkids deleted the modify-default-skill branch February 12, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant