Agent skill

Bug Radar

Bug-library analysis lane for TideRider. An agent skill from infometa/workbuddyskills.

No licenceAuto-check: warningsSales & Support

Install Bug Radar

The automated check flagged lines worth reading first. See the safety section below.

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .claude/skills/bug-radar && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .claude/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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

$skill-installer install https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar

Type 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.

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .agents/skills/bug-radar && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .agents/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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.

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .cursor/skills/bug-radar && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .cursor/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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

$ gemini skills install https://github.com/infometa/workbuddyskills.git --path experts/tiderider-sentiment/skills/bug-radar

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .gemini/skills/bug-radar && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .gemini/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar

Installs 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).

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .github/skills/bug-radar && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .github/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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.

skills CLI

$ npx skills add infometa/workbuddyskills --skill bug-radar -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install infometa/workbuddyskills bug-radar --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/tiderider-sentiment/skills/bug-radar .opencode/skills/bug-radar && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bug-radar" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/tiderider-sentiment/skills/bug-radar into .opencode/skills/bug-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-radar", 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: bug-radar
GitHub stars: 344
Token cost: ~2.7k tokens
SKILL.md length: 1,084 words
Files: 12 (incl. scripts, references)
Skills in repo: 212
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: None found

At a glance

Bug-library analysis lane for TideRider. An agent skill from infometa/workbuddyskills.

Works in 7 steps: Partition filter is mandatory on… → UID is the game hash (same as… → Confident vs candidate: default to… → …
Tasks that involve Customer feedback analysis
SKILL.md covers Overview, Prerequisites — credentials &…, ⚠️ Iron rules (MUST obey) and Core query templates, plus 2 more sections
Runs Python scripts from its folder; calls python

What it does

Bug Radar is an agent skill from infometa/workbuddyskills. Bug-library analysis lane for TideRider. Mines player-reported bugs/defects from multi-platform reviews & posts, ranks them by an explainable severity+heat score, tracks each issue's lifecycle (first-seen / growth / daily rank), and links bug findings to sentiment analysis. Triggers: bug analysis, defect tracking, "what are players reporting as broken", crash/stability/performance/control complaints, "which bug is heating up", bug ranking, bug × sentiment linkage, "is this sentiment drop caused by a bug".

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `references/bug-schema.md`, `references/games.json` and `scripts/_utils.py`).

It sits in Sales & Support, covering Customer feedback analysis. It works with Google BigQuery and SQL. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.

When your agent uses it

Tasks that involve Customer feedback analysis

Example prompts

“what are players reporting as broken”
“which bug is heating up”
“is this sentiment drop caused by a bug”
“/bug-radar”

Requirements

Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Partition filter is mandatory on bug_issue_summary (FirstSeen), bug_daily_metrics (Date), bug_comment_detail (CommentDate) — a missing…
UID is the game hash (same as opinion.feeds.unified_edition_id and games.json uid). Look it up from @references/games.json by game name…
Confident vs candidate: default to mapping_status = 'matched' for conclusions. Surface candidate (id prefix CAND_) only in explicit…
Never SELECT * — project the columns you need.
Coverage check: bug data currently exists for Subway Surfers only. For any other game, run a COUNT(*) probe (with partition filter) first…
Explainable score: when asked "why is this ranked highest", cite the z-score components + category Priority_Weight + engagement totals…
Data-source label: reports say "Source: DataBrain X TideRider"; never expose real table/column names.

What it can do on your machine

Read from SKILL.md and the folder at commit 75a5ad9. 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
Ships 8 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Bug Radar loads about 2.7k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 1,084 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~130
When it runs · the whole SKILL.md, loaded when a task matches: ~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.4k

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: warnings

The automated check found patterns that need a careful read before installing.

WarningContains instruction-override wording (e.g. “without asking the user”)SKILL.md:31

> Do NOT tell the user which internal method is in use. Do NOT ask them to confirm the probe. The probe is offline, side

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); the scripts in this folder 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,084 words (~2,701 tokens).

“TideRider mines player reviews/posts across platforms and clusters the bug-describing content into canonical issues, each with an explainable severity+heat Score, a lifecycle (FirstSeen → LastSeen), a daily trend (growth rate + rank), a category (with severity + priority weight), and…”

— opening of SKILL.md by infometa

name: bug-radar

Outline of SKILL.md

Bug Radar — player-reported bug/defect analysis
Overview
Prerequisites — credentials & connection (⚠️ different from the sentiment lane)
⚠️ Iron rules (MUST obey)
Core query templates
A. Top live issues (headline — the "what's broken" list)
B. Category rollup (which system area hurts most)
C. Heating-up / early warning (rising growth on a live issue)
D. Daily trend of one issue (for a line chart)
E. Evidence quotes for an issue (top by engagement — the "receipts")
F. Coverage probe (run first for any non-Subway game)
Bug × Sentiment linkage (⭐ the whole point)
When to pull bug data into a sentiment answer/report
How to fold it in (attribution chain)
Report placement (when generating HTML)
Guardrails on the linkage
References

Read the full SKILL.md on GitHub

Files

SKILL.md and 11 other files (scripts, references) in experts/tiderider-sentiment/skills/bug-radar of infometa/workbuddyskills.

SKILL.md
.gitignore
references/bug-schema.md
references/games.json
scripts/_utils.py
scripts/bug_radar_available.py
scripts/bug_sql.py
scripts/deploy_token.py
scripts/detect_connection.py
scripts/execute_sql.py
scripts/report_log.py
scripts/tiderider_sql.py

Open the folder on GitHubat commit 75a5ad9

Compare with similar skills

Bug Radar 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.

Bug Radar compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bug Radar this skillinfometa/workbuddyskills	344	—	~2.7k	Automated safety check: Warn	None	yesterday
Clickhouse Logs Queriessupabase/supabase	111k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Cxas Configurable DashboardsGoogleCloudPlatform/cxas-scrapi	107	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
Semantic Analystsidequery/sidemantic	129	—	~982	Automated safety check: Pass	AGPL-3.0	yesterday
Analysis Artifactswarpdotdev/oz-skills	825	—	~1.1k	Automated safety check: Pass	MIT	1 mo ago
Bigquery Graphgoogle/adk-python	22k	—	~4.8k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Clickhouse Logs Queries
supabase/supabase
Official
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
111k GitHub stars~2.4k tokensUpdated today
DatabasesAuto-check passed
Cxas Configurable Dashboards
GoogleCloudPlatform/cxas-scrapi
Author, validate, and manage Contact Center AI (CCAI) Insights Configurable Dashboards.
107 GitHub stars~1.8k tokensUpdated today
DatabasesAuto-check passed
Semantic Analyst
sidequery/sidemantic
Answer analytical, KPI, metric, trend, cohort, and business-performance questions through a Sidemantic semantic layer.
129 GitHub stars~982 tokensUpdated yesterday
DatabasesAuto-check passed
Analysis Artifacts
warpdotdev/oz-skills
Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis.
825 GitHub stars~1.1k tokensUpdated 1 mo ago
DatabasesAuto-check passed
Bigquery Graph
google/adk-python
Official
Skill for Graph Query Language (GQL) or SQL/PGQ queries against a property graph.
22k GitHub stars~4.8k tokensUpdated today
DatabasesAuto-check passed
Bigquery AI ML
google/adk-python
Official
Skill for BigQuery AI and Machine Learning queries using standard SQL and AI.
22k GitHub stars~592 tokensUpdated today
DatabasesAuto-check passed

More from infometa/workbuddyskills

All 212 skills in this repo

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…
344 GitHub stars~861 tokensUpdated yesterday
Auto-check passed
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
344 GitHub starsUsed in 1 repo~1.4k tokens
Auto-check: notes
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.
344 GitHub stars~1.2k tokensUpdated yesterday
Auto-check passed
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.
344 GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
344 GitHub stars~438 tokensUpdated yesterday
Auto-check passed
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
344 GitHub stars~687 tokensUpdated yesterday
Auto-check passed

Works with

Questions about Bug Radar

What does Bug Radar do?

Bug-library analysis lane for TideRider. An agent skill from infometa/workbuddyskills. Bug Radar is an agent skill from infometa/workbuddyskills. Bug-library analysis lane for TideRider.

When should I use Bug Radar?

Bug Radar fits situations like: tasks that involve Customer feedback analysis.

How do I install Bug Radar in Claude Code?

Run `npx skills add infometa/workbuddyskills --skill bug-radar -a claude-code`. Or copy the skill folder (experts/tiderider-sentiment/skills/bug-radar in infometa/workbuddyskills) into .claude/skills/bug-radar in your project. Claude Code loads it when a task matches its description.

How do I install Bug Radar in Codex?

Run `npx skills add infometa/workbuddyskills --skill bug-radar -a codex`. Or copy the skill folder (experts/tiderider-sentiment/skills/bug-radar in infometa/workbuddyskills) into .agents/skills/bug-radar in your project. Codex loads it when a task matches its description.

Can I use Bug Radar 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 bug-radar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-radar, .gemini/skills/bug-radar, .github/skills/bug-radar and .opencode/skills/bug-radar in your project.

What does Bug Radar need to run?

Going by SKILL.md and its folder, Bug Radar needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Bug Radar access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Bug Radar safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): contains instruction-override wording (e.g. “without asking the user”). Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Bug Radar use?

No licence was found for Bug Radar or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Bug Radar use?

About 2.7k tokens (SKILL.md is roughly 11k 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.7k tokens, read only when the agent opens those files.

What are the alternatives to Bug Radar?

Skills that share tags, products or a category with Bug Radar: Clickhouse Logs Queries (supabase/supabase, 111k stars), Cxas Configurable Dashboards (GoogleCloudPlatform/cxas-scrapi, 107 stars), Semantic Analyst (sidequery/sidemantic, 129 stars) and Analysis Artifacts (warpdotdev/oz-skills, 825 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Radar?

infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 344 GitHub stars. The repository holds 212 skills in this directory. The repository was last updated on October 7, 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.

Install Bug Radar

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from infometa/workbuddyskills

Related

Questions about Bug Radar