Z.AI CLI
numman-ali/zai-cli
Command-line access to Z.AI vision analysis, web search, page reading and GitHub repo exploration through npx zai-cli, using an API key.
Execute and manage Gemini CLI built-in tools including file operations, web search, shell commands, and memory.
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install majiayu000/claude-skill-registry gemini-tools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ai-llm/gemini-tools .claude/skills/gemini-tools && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .claude/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-toolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install majiayu000/claude-skill-registry gemini-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ai-llm/gemini-tools .agents/skills/gemini-tools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .agents/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install majiayu000/claude-skill-registry gemini-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ai-llm/gemini-tools .cursor/skills/gemini-tools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .cursor/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/majiayu000/claude-skill-registry.git --path skills/ai-llm/gemini-tools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install majiayu000/claude-skill-registry gemini-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ai-llm/gemini-tools .gemini/skills/gemini-tools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .gemini/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install majiayu000/claude-skill-registry gemini-toolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ai-llm/gemini-tools .github/skills/gemini-tools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .github/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install majiayu000/claude-skill-registry gemini-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ai-llm/gemini-tools .opencode/skills/gemini-tools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gemini-tools" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/gemini-tools into .opencode/skills/gemini-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gemini-tools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gemini-toolsExecute and manage Gemini CLI built-in tools including file operations, web search, shell commands, and memory.
Gemini Tools is an agent skill from majiayu000/claude-skill-registry. Execute and manage Gemini CLI built-in tools including file operations, web search, shell commands, and memory. Use for automated workflows, tool orchestration, and safe execution patterns.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Productivity & Automation, covering Web search and Computer vision. It works with Google Gemini. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 2d14a69. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
geminigitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Gemini Tools loads about 3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 176 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
"blockedPaths": [".env", "*.key", "*.pem"]Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from majiayu000/claude-skill-registry at commit 2d14a69, republished under its MIT licence (© majiayu000). 176 words, ~3,041 tokens.
.claude/skills/gemini-tools/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Comprehensive patterns for executing Gemini CLI's built-in tools safely and effectively.
# List directory contents
gemini -p "List all Python files in ./src"
# Read files
gemini -p "Read and explain @./config.json"
# Write files
gemini --yolo -p "Create a README.md for this project"
# Modify files
gemini --sandbox -p "Add error handling to @./main.py"# Google search
gemini --yolo -p "Search for React performance optimization best practices"
# Fetch web content
gemini -p "Analyze the API documentation at @https://api.example.com/docs"
# Research workflow
gemini --yolo -p "Research and summarize the latest Python 3.12 features"# Safe execution with confirmation
gemini -p "Run the test suite and fix any failing tests"
# Auto-approve (use carefully!)
gemini --yolo -p "Set up a new Next.js project with TypeScript"
# Sandbox mode (recommended)
gemini --sandbox -p "Install dependencies and run the build"# Save information
gemini -p "Remember that the API endpoint is https://api.prod.example.com"
# Recall information
gemini -p "What API endpoint did I tell you about?"
# Project-specific memory
cd project && gemini -p "Save project configuration: Node 20, PostgreSQL 15, Redis 7"# Each tool call requires confirmation
gemini -p "Organize the project files into proper directories"
# > Tool call: list_directory('./') - Approve? [Y/n]
# > Tool call: write_file('./src/index.js') - Approve? [Y/n]# All tools execute automatically
gemini --yolo -p "Create a complete Express.js API with authentication"
# Keyboard shortcut in chat
# Ctrl+Y to toggle YOLO mode# Creates isolated environment
gemini --sandbox -p "Experiment with different npm packages"
# Limitations in sandbox:
# - No system modifications
# - Restricted file access
# - No network requests to productionYOLO mode is ideal for trusted, repeatable tool operations. Here are proven automation patterns:
# ✅ SAFE for YOLO (low-risk, high-value)
gemini --yolo -p "Organize project files by type and create index files"
gemini --yolo -p "Add JSDoc comments to all functions in ./src"
gemini --yolo -p "Generate comprehensive test suite for API endpoints"
gemini --yolo -p "Create complete documentation from code comments"
gemini --yolo -p "Set up ESLint, Prettier, and pre-commit hooks"
gemini --yolo -p "Generate TypeScript definitions from JavaScript"# ⚠️ REVIEW FIRST (higher risk)
gemini -p "Refactor authentication system for security improvements"
gemini -p "Migrate database schema to new structure"
gemini -p "Update production deployment configuration"
gemini -p "Delete unused files and dependencies"
# Then if comfortable, use YOLO for execution:
gemini --yolo -p "Execute the reviewed plan step by step"# Combine YOLO with checkpointing for safety
gemini --yolo --checkpointing -p "Comprehensive codebase modernization"
# Use YOLO with specific constraints
gemini --yolo -p "Add logging to all functions, but preserve exact functionality"
# YOLO with backup strategy
backup_and_execute() {
local task="$1"
git stash push -m "pre-yolo-backup-$(date +%s)"
gemini --yolo -p "$task"
echo "Backup created. Use 'git stash pop' to revert if needed."
}#!/bin/bash
# Automated project initialization
setup_project() {
local name="$1"
local type="$2" # react, node, python, etc.
gemini --yolo -p "Create a new $type project named '$name' with:
1. Proper directory structure
2. Configuration files
3. Git initialization
4. README with setup instructions
5. Basic CI/CD workflow
6. Docker setup
7. Environment variables template
8. Initial tests
Use industry best practices."
}
# Usage
setup_project "my-app" "react"#!/bin/bash
# Generate code from specifications
generate_from_spec() {
local spec_file="$1"
local output_dir="${2:-./generated}"
gemini --yolo \
--include-directories "$output_dir" \
-p "Read the specification: @$spec_file
Generate:
1. Data models/schemas
2. API endpoints
3. Database migrations
4. Unit tests
5. Integration tests
6. API documentation
Output to: $output_dir/"
}#!/bin/bash
# Smart file organization
organize_files() {
local project_dir="${1:-.}"
# Use YOLO for file organization (generally safe)
gemini --yolo -p "Analyze and organize directory: $project_dir
Execute automatically:
1. Identify file types and purposes
2. Create optimal directory structure
3. Move files to appropriate locations
4. Update import paths in code files
5. Create index files for each module
6. Generate structure documentation
7. Create a change log of all moves"
}#!/bin/bash
# Process multiple files
process_files() {
local pattern="$1" # e.g., "*.js"
local operation="$2" # e.g., "add JSDoc comments"
gemini --yolo -p "For each file matching $pattern:
1. Read the file
2. $operation
3. Preserve formatting
4. Save changes
5. Log modifications
Create a summary of all changes."
}
# Examples
process_files "*.py" "add type hints"
process_files "*.test.js" "convert to TypeScript"
process_files "*.md" "fix formatting and add TOC"#!/bin/bash
# Validate before execution
validate_then_execute() {
local command="$1"
# First pass: analyze without execution
gemini -p "Analyze but DON'T execute: $command
Check for:
- Potential risks
- Missing dependencies
- Breaking changes
- Security issues
Report findings."
read -p "Continue with execution? [y/N] " -r
if [[ $REPLY =~ ^[Yy]$ ]]; then
gemini --yolo -p "Now execute: $command"
fi
}#!/bin/bash
# Execute with rollback
with_rollback() {
local operation="$1"
local backup_dir=".backups/$(date +%Y%m%d-%H%M%S)"
# Create backup
mkdir -p "$backup_dir"
cp -r . "$backup_dir/"
# Execute operation
if gemini --yolo -p "$operation"; then
echo "Success! Backup at: $backup_dir"
else
echo "Failed! Rolling back..."
cp -r "$backup_dir/"* .
echo "Rolled back to previous state"
fi
}// ~/.gemini/tool-policy.json
{
"tools": {
"shell": {
"enabled": true,
"requireConfirmation": true,
"blockedCommands": ["rm -rf", "sudo", "chmod 777"],
"allowedDirectories": ["./", "/tmp/"]
},
"fileSystem": {
"enabled": true,
"readOnly": false,
"allowedPaths": ["./src/", "./tests/"],
"blockedPaths": [".env", "*.key", "*.pem"]
},
"web": {
"enabled": true,
"allowedDomains": ["*.github.com", "docs.*.com"],
"blockedDomains": ["*.internal.com"]
},
"memory": {
"enabled": true,
"maxItems": 100,
"encryption": true
}
}
}#!/bin/bash
# Chain multiple tools
chain_operations() {
gemini --yolo -p "Execute this workflow:
1. Search for 'React hooks best practices'
2. Read the top 3 results
3. Create a summary document
4. Generate example code
5. Save to ./docs/react-hooks-guide.md
6. Create unit tests for examples
7. Run the tests
8. Fix any issues"
}#!/bin/bash
# Execute based on conditions
conditional_tools() {
gemini -p "Check if package.json exists.
If it exists:
1. Read package.json
2. Update all dependencies
3. Run npm audit fix
4. Run tests
If it doesn't exist:
1. Detect project type
2. Initialize appropriate package manager
3. Add common dependencies
4. Create basic scripts"
}#!/bin/bash
# Run tools in parallel
parallel_analysis() {
local project="$1"
gemini --yolo -p "Analyze $project in parallel:
Stream 1: Code Quality
- Check for lint errors
- Identify code smells
- Suggest refactoring
Stream 2: Security
- Scan for vulnerabilities
- Check dependencies
- Review auth patterns
Stream 3: Performance
- Identify bottlenecks
- Suggest optimizations
- Memory usage analysis
Combine all findings into a report."
}#!/bin/bash
# Monitor tool usage
track_tool_usage() {
local log_file="~/.gemini/tool-usage.log"
# Wrap gemini command
gemini_tracked() {
local start=$(date +%s)
local output=$(gemini "$@" 2>&1)
local end=$(date +%s)
local duration=$((end - start))
# Log usage
echo "$(date '+%Y-%m-%d %H:%M:%S') | Duration: ${duration}s | Args: $*" >> "$log_file"
echo "$output"
# Parse and count tool calls
local tool_count=$(echo "$output" | grep -c "Tool call:")
echo "Tools executed: $tool_count" >> "$log_file"
}
alias gemini='gemini_tracked'
}#!/bin/bash
# Complete audit trail
audit_tools() {
local audit_dir="~/.gemini/audit/$(date +%Y%m%d)"
mkdir -p "$audit_dir"
# Before execution
find . -type f -name "*" | xargs md5sum > "$audit_dir/before.md5"
# Execute with logging
gemini "$@" | tee "$audit_dir/execution.log"
# After execution
find . -type f -name "*" | xargs md5sum > "$audit_dir/after.md5"
# Generate diff
diff "$audit_dir/before.md5" "$audit_dir/after.md5" > "$audit_dir/changes.diff"
echo "Audit trail saved to: $audit_dir"
}#!/bin/bash
# Handle tool failures gracefully
resilient_execution() {
local max_retries=3
local retry_count=0
while [ $retry_count -lt $max_retries ]; do
if gemini --sandbox -p "$1"; then
echo "Success on attempt $((retry_count + 1))"
return 0
else
retry_count=$((retry_count + 1))
echo "Attempt $retry_count failed. Retrying..."
sleep 5
fi
done
echo "Failed after $max_retries attempts"
return 1
}#!/bin/bash
# Implement recovery strategies
with_recovery() {
local operation="$1"
# Set trap for cleanup
trap 'echo "Cleaning up..."; cleanup_function' ERR
gemini -p "$operation" || {
echo "Operation failed. Attempting recovery..."
# Try recovery
gemini -p "The previous operation failed. Please:
1. Identify what went wrong
2. Fix the issue
3. Complete the operation safely"
}
trap - ERR
}Use Appropriate Mode
Set Boundaries
Monitor Execution
Batch Operations
# Process multiple files in one prompt
gemini --yolo -p "Process all *.js files: add types, format, test"Use Caching
# Cache web fetches
export GEMINI_CACHE_WEB=trueOptimize Context
# Include only necessary files
gemini --include-directories ./src --max-depth 2gemini-cli: Main Gemini CLI integrationgemini-auth: Authentication managementgemini-chat: Interactive chat sessionsgemini-mcp: MCP server management© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/ai-llm/gemini-tools of majiayu000/claude-skill-registry.
Open the folder on GitHubat commit 2d14a69
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.
Gemini Tools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gemini Tools this skillmajiayu000/claude-skill-registry | 666 | 1 repos | ~3k | Automated safety check: Notes | MIT | |
| Z.AI CLInumman-ali/zai-cli | 110 | — | ~528 | Automated safety check: Pass | MIT | |
| OpenCLI Smart Search Routerjackwener/OpenCLI | 30k | 2 repos | ~753 | Automated safety check: Pass | Apache-2.0 | |
| ModLens Image Vision Bridgeliustack/modlens | 4.2k | 1 repos | ~1.3k | Automated safety check: Notes | MIT | |
| Web Searchjjyaoao/HelloAgents | 3.2k | 1 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Local Web SearchuluckyXH/OpenMOSS | 1.3k | — | ~392 | Automated safety check: Notes | MIT |
numman-ali/zai-cli
Command-line access to Z.AI vision analysis, web search, page reading and GitHub repo exploration through npx zai-cli, using an API key.
jackwener/OpenCLI
Routes a search question to the most suitable opencli source, normally one AI site plus up to two specialist sites, with call limits per question and a recap at the end.
liustack/modlens
Gives text-only models sight by running the modlens CLI on an image path or URL and returning structured JSON evidence with transcribed text, layout and semantics.
jjyaoao/HelloAgents
Implement web search capabilities using the z-ai-web-dev-sdk.
uluckyXH/OpenMOSS
A skill your agent uses when the user asks for web search that should run via the local-160 Responses API with websearch tool (base URL like https://proxy.example.com, model gpt-5.2-codex(xhigh)).
EXboys/skilllite
Web search and content extraction with Tavily and Exa via inference.sh CLI.
majiayu000/claude-skill-registry
Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.
majiayu000/claude-skill-registry
Neural search via Exa MCP for web, code, and company research.
majiayu000/claude-skill-registry
Unified media generation via fal.ai MCP — image, video, and audio.
majiayu000/claude-skill-registry
Interact with Zotero reference management libraries using the pyzotero Python client.
majiayu000/claude-skill-registry
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.
majiayu000/claude-skill-registry
Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.
Works with
Categories
Execute and manage Gemini CLI built-in tools including file operations, web search, shell commands, and memory. Gemini Tools is an agent skill from majiayu000/claude-skill-registry. Execute and manage Gemini CLI built-in tools including file operations, web search, shell commands, and memory.
Gemini Tools fits situations like: automated workflows; tool orchestration; safe execution patterns.
Run `npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a claude-code`. Or copy the skill folder (skills/ai-llm/gemini-tools in majiayu000/claude-skill-registry) into .claude/skills/gemini-tools in your project. Claude Code loads it when a task matches its description.
Run `npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a codex`. Or copy the skill folder (skills/ai-llm/gemini-tools in majiayu000/claude-skill-registry) into .agents/skills/gemini-tools in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add majiayu000/claude-skill-registry --skill gemini-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gemini-tools, .gemini/skills/gemini-tools, .github/skills/gemini-tools and .opencode/skills/gemini-tools in your project.
Going by SKILL.md and its folder, Gemini Tools needs the command-line tools its instructions call (gemini and git). Our summary lists: Python 3; Docker.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Gemini Tools is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Gemini Tools: Z.AI CLI (numman-ali/zai-cli, 110 stars), OpenCLI Smart Search Router (jackwener/OpenCLI, 30k stars), ModLens Image Vision Bridge (liustack/modlens, 4.2k stars) and Web Search (jjyaoao/HelloAgents, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 1,273 skills in this directory. The repository was last updated on October 7, 2026.
Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.