skill-porter
- Repo stars 180
- Author updated Live
- Author repo skill-porter
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @jduncan-rva · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-porter
description: Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to…
category: other
runtime: no special runtime
---
# skill-porter output preview
## PART A: Task fit
- Use case: Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to make a skill cross-platform compatible, port a skill between platforms, or create a universal extension that works on both Claude Code and Gemini CLI..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Capabilities / Bidirectional Conversion / Smart Platform Detection” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to make a skill cross-platform compatible, port a skill between platforms, or create a universal extension that works on both Claude Code and Gemini CLI.”.
- **02** When the source has headings, the agent prioritizes “Core Capabilities / Bidirectional Conversion / Smart Platform Detection” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, read environment variables.
Start with a small task and check whether the result follows “Core Capabilities / Bidirectional Conversion / Smart Platform Detection”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-porter
description: Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to…
category: other
source: jduncan-rva/skill-porter
---
# skill-porter
## When to use
- Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to make a skill cross-pla…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Capabilities / Bidirectional Conversion / Smart Platform Detection” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-porter" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Capabilities / Bidirectional Conversion / Smart Platform Detection
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Skill Porter - Cross-Platform Skill Converter
This skill automates the conversion between Claude Code skills and Gemini CLI extensions, enabling true cross-platform AI tool development.
Core Capabilities
Bidirectional Conversion
Convert skills and extensions between platforms while preserving functionality:
Example requests:
- "Convert this Claude skill to work with Gemini CLI"
- "Make my Gemini extension compatible with Claude Code"
- "Create a universal version of this skill that works on both platforms"
- "Port the database-helper skill to Gemini"
Smart Platform Detection
Automatically analyzes directory structure to determine source platform:
Detection criteria:
- Claude: Presence of
SKILL.mdwith YAML frontmatter or.claude-plugin/marketplace.json - Gemini: Presence of
gemini-extension.jsonorGEMINI.mdcontext file - Universal: Has both platform configurations
Example requests:
- "What platform is this skill built for?"
- "Analyze this extension and tell me what needs to be converted"
- "Is this a Claude skill or Gemini extension?"
Metadata Transformation
Intelligently converts between platform-specific formats:
Conversions handled:
- YAML frontmatter ↔ JSON manifest
allowed-tools(whitelist) ↔excludeTools(blacklist)- Environment variables ↔ settings schema
- MCP server configuration paths
- Platform-specific documentation formats
Example requests:
- "Convert the metadata from this Claude skill to Gemini format"
- "Transform the allowed-tools list to Gemini's exclude pattern"
- "Generate a settings schema from these environment variables"
MCP Server Preservation
Maintains Model Context Protocol server configurations across platforms:
Example requests:
- "Ensure the MCP server config works on both platforms"
- "Update the MCP server paths for Gemini's ${extensionPath} variable"
- "Validate that the MCP configuration is compatible"
Validation & Quality Checks
Ensures converted output meets platform requirements:
Validation checks:
- Required files present (SKILL.md, gemini-extension.json, etc.)
- Valid YAML/JSON syntax
- Correct frontmatter structure
- MCP server paths resolve correctly
- Tool restrictions are valid
- Settings schema is complete
Example requests:
- "Validate this converted skill"
- "Check if this Gemini extension meets all requirements"
- "Is this conversion ready to install?"
Conversion Process
When you request a conversion, I will:
- Analyze the source directory structure
- Detect which platform it's built for
- Extract metadata, MCP configuration, and documentation
- Transform the data to target platform format
- Generate required files for target platform
- Validate output meets all requirements
- Report what was converted and any manual steps needed
Platform Differences Handled
File Structure
- Claude:
SKILL.md+.claude-plugin/marketplace.json - Gemini:
GEMINI.md+gemini-extension.json - Universal: Both sets of files + shared documentation
Metadata Format
- Claude: YAML frontmatter in SKILL.md
- Gemini: JSON manifest file
- Conversion: Bidirectional YAML ↔ JSON transformation
Tool Restrictions
- Claude:
allowed-tools(whitelist - only listed tools permitted) - Gemini:
excludeTools(blacklist - listed patterns blocked) - Conversion: Logic inversion with intelligent mapping
Configuration
- Claude: Environment variables (user sets before running)
- Gemini: Settings schema (prompted during installation)
- Conversion: Infer schema from env vars or generate env var docs
MCP Server Paths
- Claude: Relative paths from skill directory
- Gemini: Uses
${extensionPath}variable substitution - Conversion: Automatic path transformation
Usage Examples
Convert Claude Skill to Gemini
User: "I have a Claude skill at ./database-helper. Convert it to Gemini."
Claude: I'll analyze the skill and convert it to Gemini format...
- Detected Claude skill (found SKILL.md with frontmatter)
- Extracted metadata and MCP configuration
- Generated gemini-extension.json and GEMINI.md
- Transformed allowed-tools to excludeTools
- Created settings schema from environment variables
✓ Conversion complete! Ready to install with: gemini extensions install ./database-helper
Convert Gemini Extension to Claude
User: "Port my Gemini extension to Claude Code"
Claude: I'll convert this Gemini extension to a Claude skill...
- Detected Gemini extension (found gemini-extension.json)
- Extracted manifest and context file
- Generated SKILL.md with YAML frontmatter
- Created .claude-plugin/marketplace.json
- Converted excludeTools to allowed-tools
✓ Conversion complete! Install with: cp -r ./extension ~/.claude/skills/
Create Universal Extension
User: "Make this skill work on both platforms"
Claude: I'll create a universal extension structure...
- Analyzing current configuration
- Generating both Claude and Gemini files
- Moving shared content to shared/ directory
- Updating MCP server paths for both platforms
✓ Universal extension created! Works with both Claude Code and Gemini CLI
Advanced Features
Pull Request Generation
Create a PR to add dual-platform support to the parent repository:
Example requests:
- "Convert this skill and create a PR to add Gemini support"
- "Generate a pull request with the universal version"
Fork and Dual Setup
Create a fork with both platform configurations:
Example requests:
- "Fork this repo and set it up for both platforms"
- "Create a dual-platform fork I can use with both CLIs"
Validation Only
Check compatibility without converting:
Example requests:
- "Validate this skill's conversion to Gemini"
- "Check if this extension can be ported to Claude"
- "What needs to change to make this universal?"
Configuration
This skill operates directly on filesystem directories and doesn't require external configuration. It uses:
- File system access to read and write skill/extension files
- Git operations for PR and fork features
- GitHub CLI (
gh) for repository operations
Safety Features
- Non-destructive: Creates new files, doesn't modify source unless explicitly requested
- Validation: Checks output before completion
- Reporting: Clear summary of changes made
- Rollback friendly: All changes are standard file operations
Limitations
Some aspects may require manual review:
- Custom slash commands (platform-specific syntax)
- Complex MCP server configurations with multiple servers
- Platform-specific scripts that don't translate directly
- Edge cases in tool restriction mapping
These will be flagged in the conversion report.
Technical Details
Tool Restriction Conversion
Claude → Gemini (Whitelist → Blacklist):
- Analyze allowed-tools list
- Generate exclude patterns for all other tools
- Special handling for wildcard permissions
Gemini → Claude (Blacklist → Whitelist):
- List all available tools
- Remove excluded tools
- Generate allowed-tools list
Settings Inference
When converting Claude → Gemini, environment variables in MCP config become settings:
// MCP env var
"env": { "DB_HOST": "${DB_HOST}" }
// Becomes Gemini setting
"settings": [{
"name": "DB_HOST",
"description": "Database host",
"default": "localhost"
}]
Path Transformation
Claude uses relative paths, Gemini uses variables:
// Claude
"args": ["mcp-server/index.js"]
// Gemini
"args": ["${extensionPath}/mcp-server/index.js"]
For implementation details, see the repository at https://github.com/jduncan-rva/skill-porter
Decide Fit First
Design Intent
How To Use It
Boundaries And Review