Skillz Integration Skill for Claude
Run and integrate Skillz MCP server with Docker for skill execution.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/github/gh-aw --skill skillz-integrationThe instruction itself
13 sections, as written by the authorSkillz MCP Server Integration
Skillz is an MCP server that turns Claude-style skills (SKILL.md plus optional resources) into callable tools for MCP clients. It discovers skills, exposes instructions/resources, and runs bundled helper scripts.
Repository: https://github.com/intellectronica/skillz
> ⚠️ Experimental proof-of-concept. Potentially unsafe. Treat skills like untrusted code and run in sandboxes/containers. Use at your own risk.
Quick Start
Basic Docker Configuration
To use Skillz with GitHub Agentic Workflows, add it as an MCP server in your workflow frontmatter:
on: issues
engine: copilot
mcp-servers:
skillz:
container: "intellectronica/skillz"
args:
- "-v"
- "/path/to/skills:/skillz"
- "/skillz"
# Your workflow with skills
Use skills from the skillz server to accomplish tasks.
Key points:
- Replace
/path/to/skillswith the actual path to your skills directory - The skills directory is mounted at
/skillzinside the container - Pass
/skillzas the argument to tell skillz where to find skills
Skills Directory Structure
Skillz looks for skills inside the root directory you provide (defaults to ~/.skillz). Each skill lives in its own folder or zip archive that includes a SKILL.md file with YAML front matter.
Example Directory Layout
skills/
├── summarize-docs/
│ ├── SKILL.md
│ ├── summarize.py
│ └── prompts/example.txt
├── translate.zip
└── web-search/
└── SKILL.md
Skill Structure
Each skill folder must contain:
SKILL.md- Required file with YAML frontmatter describing the skill- Helper scripts - Optional Python, Node.js, or other scripts
- Resources - Optional datasets, examples, prompts, etc.
Example SKILL.md:
name: summarize-docs
description: Summarize documentation files
# Document Summarization Skill
This skill helps summarize long documentation files.
Use the provided `summarize.py` script to process documents.
Packaging Skills as Zip Files
Skills can be packaged as .zip archives:
translate.zip
├── SKILL.md
└── helpers/
└── translate.js
Or with a top-level directory:
data-cleaner.zip
└── data-cleaner/
├── SKILL.md
└── clean.py
Skillz vs Claude Code Directory Structure
Claude Code-Compatible Layout (Flat)
For compatibility with Claude Code, use a flat directory structure where every immediate subdirectory is a single skill:
skills/
├── hello-world/
│ ├── SKILL.md
│ └── run.sh
└── summarize-text/
├── SKILL.md
└── run.py
Limitations: No nested directories, no .zip files.
Skillz-Only Layout (Flexible)
Skillz supports nested directories and .zip files:
skills/
├── text-tools/
│ └── summarize-text/
│ ├── SKILL.md
│ └── run.py
└── image-processing.zip
Note: This layout is NOT compatible with Claude Code.
Configuration Options
Environment Variables
When using Docker, you can pass environment variables to skills:
mcp-servers:
skillz:
container: "intellectronica/skillz"
args:
- "-v"
- "/path/to/skills:/skillz"
- "/skillz"
env:
API_KEY: "${{ secrets.SKILL_API_KEY }}"
Verbose Logging
Enable verbose logging for debugging:
mcp-servers:
skillz:
container: "intellectronica/skillz"
args:
- "-v"
- "/path/to/skills:/skillz"
- "/skillz"
- "--verbose"
Other skills for the same job
different authors, same section of the catalogue
Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.
Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.
Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.
Chain agent outputs as inputs in sequential or parallel pipelines for data flow orchestration
Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.
> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated tweet actions. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing guarded tweet actions. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "apps SDK" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets.
>- Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. and work across runtimes (e.g., Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.
How to use it
Take github/skillz-integration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.