Repository of Agent skills that provide ease of use to users and developers interested in Red5.
A skill is a folder containing a SKILL.md (instructions plus a short description of when to use it) and, optionally, scripts and reference files. Your coding agent reads the description, and loads the rest only when a task matches. Adding a skill to your agent means putting its folder where the agent looks for skills.
| Skill | What it does | Needs |
|---|---|---|
red5-start-server |
Pulls the latest red5pro/server Docker release and starts a running Red5 container. |
Docker, Python 3 |
red5-log-triage |
Summarizes a red5.log (plain, .gz or .zip) into ranked findings with likely causes and next steps, so support can diagnose from the log alone. |
Python 3 |
red5-create-plugin |
Helps a developer create a Red5 (open source) or Red5 Pro plugin: explains how the two differ, generates a Maven project that compiles, then guides build, deploy and verification. | Java 21, Maven, Python 3 |
Each skill lives in .github/skills/<skill-name>/.
git clone https://github.com/Red5/skills.git
cd skillsTo update later, run git pull in this folder.
Every agent has two kinds of location. Use a personal location to have the skill in every project on your machine, or a project location to have it only in one repository (and shared with your team if you commit it).
| Agent | Personal (all your projects) | Project (one repository) | Reload |
|---|---|---|---|
| Claude Code | ~/.claude/skills/<skill-name>/ |
.claude/skills/<skill-name>/ |
Picked up in the running session |
| GitHub Copilot (CLI, VS Code, cloud agent) | ~/.copilot/skills/<skill-name>/ or ~/.agents/skills/<skill-name>/ |
.github/skills/<skill-name>/ (also reads .claude/skills/ and .agents/skills/) |
/skills reload in the CLI |
| OpenAI Codex | ~/.agents/skills/<skill-name>/ |
.agents/skills/<skill-name>/ |
Restart Codex if it does not appear |
On Windows, ~ is your user profile folder (for example %USERPROFILE%\.claude\skills).
Paths are current as of the agents' documentation at the time of writing. If an agent does not find the skill, check its documentation: Claude Code, GitHub Copilot, Codex.
Copy the whole folder, not just SKILL.md, because the scripts and reference files are part of the skill. The examples below use red5-log-triage; swap in red5-start-server for the other skill.
Claude Code, for all your projects:
mkdir -p ~/.claude/skills
cp -r .github/skills/red5-log-triage ~/.claude/skills/Claude Code, for one project (run from that project's root):
mkdir -p .claude/skills
cp -r /path/to/skills/.github/skills/red5-log-triage .claude/skills/GitHub Copilot, for all your projects:
mkdir -p ~/.copilot/skills
cp -r .github/skills/red5-log-triage ~/.copilot/skills/GitHub Copilot, for one project: the skills in this repository already sit in .github/skills/, which is where Copilot looks. To use one in another repository, copy it there:
mkdir -p .github/skills
cp -r /path/to/skills/.github/skills/red5-log-triage .github/skills/Codex, for all your projects:
mkdir -p ~/.agents/skills
cp -r .github/skills/red5-log-triage ~/.agents/skills/Codex, for one project: use .agents/skills/ in that project's root instead.
To install every skill in this repository at once, replace red5-log-triage with *, for example cp -r .github/skills/* ~/.claude/skills/.
Prefer a link so git pull updates your skills? Link the folder instead of copying it:
ln -s "$PWD/.github/skills/red5-log-triage" ~/.claude/skills/red5-log-triage(Use the matching folder from the table for your agent.)
- Claude Code: type
/and look for the skill name in the list, or ask "what skills do you have?". - GitHub Copilot CLI: run
/skills reload, then/skills list. In VS Code, ask "what skills do you have?". - Codex: restart Codex if the skill is missing, then ask which skills are available.
Your agent will use a skill on its own when your request matches the skill's description. You can also name it directly:
| Agent | Direct call |
|---|---|
| Claude Code | /red5-log-triage |
| GitHub Copilot | /red5-log-triage |
| Codex | $red5-log-triage |
Examples:
red5-log-triage: "Here is a red5.log from a customer,~/Downloads/red5.log. Viewers kept freezing around 09:53. What is going on?"red5-start-server: "Start the latest Red5 Pro server in Docker."red5-create-plugin: "I want to write a plugin that logs every stream that gets published. My Red5 Pro server is in/usr/local/red5pro."
Requires Python 3 and nothing else. The agent runs a bundled script that collapses repeated messages, ranks them, and prints findings and likely causes, then explains the result. The script reads the log locally and does not upload it, but the agent can see what the script prints and anything it searches out of the log.
Logs often contain IP addresses, usernames and, in some versions, the license key. Redact before sharing a log or the agent's report widely.
To teach it a new pattern, add an entry to references/knowledge.json in the skill folder. Its _about field explains the format.
Needs Java 21, Maven 3.6 or newer and Python 3. A Red5 plugin and a Red5 Pro plugin are different things: different base classes, jar manifest keys and dependencies, and a Pro plugin runs only on a Red5 Pro server. The skill asks which one you are building and explains the difference before it generates anything.
For a Red5 Pro plugin, tell it where your Red5 Pro server is installed. It then builds against that server's own jars, so the API matches what will run; the Red5 Pro Maven repository otherwise needs credentials. The skill never deploys to or restarts a server on its own. The generated projects are compile-tested against Red5 2.0.29 and against Red5 Pro 16.2 and 16.3 installs; loading them in a running server is left to you.
Requires Docker running and permission to run Docker commands as your user, plus Python 3. It replaces any existing container named red5-server. See the skill's SKILL.md for the port and image overrides.
- The agent does not mention the skill. Confirm the folder is named exactly like the skill and contains
SKILL.mddirectly inside it (~/.claude/skills/red5-log-triage/SKILL.md, not one level deeper). Then reload or restart as in the table above. - The skill is found but its script is not. Tell the agent the folder the skill was installed in, and make sure you copied the whole folder (including
scripts/), not justSKILL.md. - A skill runs when you did not want it. Tell the agent to skip it, or remove the folder to uninstall.
- Uninstall. Delete the skill's folder from the location you copied it to.
Create .github/skills/<skill-name>/SKILL.md with a name and a description that says what the skill does and when to use it, put any scripts in scripts/ and reference material in references/, and add a row to the table above.