Campus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
This skill should be used when the user asks to "推荐插件", "查找插件", "搜索插件", "有什么插件", "安装插件", "plugin recommendation", "find plugins", "search plugins", or needs help discovering and managing CodeBuddy…
No licenceAuto-check passed
Install Plugin Discovery
$ npx skills add infometa/workbuddyskills --skill plugin-discovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills plugin-discovery --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/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .claude/skills/plugin-discovery && 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 "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .claude/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discoveryType 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 infometa/workbuddyskills --skill plugin-discovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills plugin-discovery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .agents/skills/plugin-discovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .agents/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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 infometa/workbuddyskills --skill plugin-discovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills plugin-discovery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .cursor/skills/plugin-discovery && 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 "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .cursor/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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/infometa/workbuddyskills.git --path plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery--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 infometa/workbuddyskills --skill plugin-discovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills plugin-discovery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .gemini/skills/plugin-discovery && 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 "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .gemini/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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 infometa/workbuddyskills plugin-discoveryInstalls 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 infometa/workbuddyskills --skill plugin-discovery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .github/skills/plugin-discovery && 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 "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .github/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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 infometa/workbuddyskills --skill plugin-discovery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills plugin-discovery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery .opencode/skills/plugin-discovery && 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 "plugin-discovery" agent skill from https://github.com/infometa/workbuddyskills/tree/main/plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery into .opencode/skills/plugin-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-discovery", 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.
Facts
- Skill name
plugin-discovery- GitHub stars
- 342
- Token cost
- ~3k tokens
- SKILL.md length
- 1,017 words
- Files
- 2 (incl. references)
- Skills in repo
- 235
- Repo updated
- First seen
- Licence
- None found
At a glance
This skill should be used when the user asks to "推荐插件", "查找插件", "搜索插件", "有什么插件", "安装插件", "plugin recommendation", "find plugins", "search plugins", or needs help discovering and managing CodeBuddy…
- Works in 10 steps: Read Marketplace Data → Semantic Matching → Present Recommendations → …
- Plugin recommendation
- SKILL.md covers Purpose, When to Use, Core Concepts and Plugin Discovery Workflow, plus 4 more sections
- Reaches github.com
What it does
Plugin Discovery is an agent skill from infometa/workbuddyskills. This skill should be used when the user asks to "推荐插件", "查找插件", "搜索插件", "有什么插件", "安装插件", "plugin recommendation", "find plugins", "search plugins", or needs help discovering and managing CodeBuddy Code plugins from marketplaces.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/marketplace-format.md`).
The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- Plugin recommendation
- Needs help discovering and managing CodeBuddy Code plugins from marketplaces
Example prompts
- “plugin recommendation”
- “find plugins”
- “search plugins”
- “/plugin-discovery”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Read Marketplace Data
- Semantic Matching
- Present Recommendations
- Install Selected Plugins
- Post-Installation
- Identify Relevant Plugins
- Determine Invocation Method
- Parallel Execution
- Results Collection
- AI Analysis and Comparison
What it can do on your machine
Read from SKILL.md and the folder at commit 9830caf. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash, json, markdown and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plugin Discovery loads about 3k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 1,017 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.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,017 words (~2,965 tokens).
“This skill provides comprehensive guidance for discovering, recommending, installing, and comparing plugins from CodeBuddy Code and Claude Code plugin marketplaces. Enable intelligent plugin discovery through AI semantic matching, streamlined installation workflows, and multi-plugin comparison capabilities.”
- name
- plugin-discovery
- version
- 0.1.0
Files
SKILL.md and 1 other file (references) in plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery of infometa/workbuddyskills.
- SKILL.md
- references/marketplace-format.md
Open the folder on GitHubat commit 9830caf
More from infometa/workbuddyskills
All 235 skills in this repoTeachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Questions about Plugin Discovery
What does Plugin Discovery do?
This skill should be used when the user asks to "推荐插件", "查找插件", "搜索插件", "有什么插件", "安装插件", "plugin recommendation", "find plugins", "search plugins", or needs help discovering and managing CodeBuddy…. Plugin Discovery is an agent skill from infometa/workbuddyskills. This skill should be used when the user asks to "推荐插件", "查找插件", "搜索插件", "有什么插件", "安装插件", "plugin recommendation", "find plugins", "search plugins", or needs help discovering and managing CodeBuddy Code plugins from marketplaces.
When should I use Plugin Discovery?
Plugin Discovery fits situations like: plugin recommendation; needs help discovering and managing CodeBuddy Code plugins from marketplaces.
How do I install Plugin Discovery in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill plugin-discovery -a claude-code`. Or copy the skill folder (plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery in infometa/workbuddyskills) into .claude/skills/plugin-discovery in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Discovery in Codex?
Run `npx skills add infometa/workbuddyskills --skill plugin-discovery -a codex`. Or copy the skill folder (plugins/codebuddy-plugins-official/plugins/plugin-finder/skills/plugin-discovery in infometa/workbuddyskills) into .agents/skills/plugin-discovery in your project. Codex loads it when a task matches its description.
Can I use Plugin Discovery in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add infometa/workbuddyskills --skill plugin-discovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-discovery, .gemini/skills/plugin-discovery, .github/skills/plugin-discovery and .opencode/skills/plugin-discovery in your project.
What does Plugin Discovery need to run?
SKILL.md names no scripts, command-line tools or credentials: Plugin Discovery is instructions for the agent only.
Does Plugin Discovery access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Plugin Discovery safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plugin Discovery use?
No licence was found for Plugin Discovery or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plugin Discovery use?
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. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
Who maintains Plugin Discovery?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 342 GitHub stars. The repository holds 235 skills in this directory. The repository was last updated on October 6, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.