Extension Puppeteer Debugging
mengxi-ream/read-frog
Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.
Frontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow.
$ npx skills add catlog22/Claude-Code-Workflow --skill team-frontend-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --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/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/team-frontend-debug .claude/skills/team-frontend-debug && 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 "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .claude/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debugType 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 catlog22/Claude-Code-Workflow --skill team-frontend-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/team-frontend-debug .agents/skills/team-frontend-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .agents/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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 catlog22/Claude-Code-Workflow --skill team-frontend-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/team-frontend-debug .cursor/skills/team-frontend-debug && 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 "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .cursor/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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/catlog22/Claude-Code-Workflow.git --path .codex/skills/team-frontend-debug--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 catlog22/Claude-Code-Workflow --skill team-frontend-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/team-frontend-debug .gemini/skills/team-frontend-debug && 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 "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .gemini/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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 catlog22/Claude-Code-Workflow team-frontend-debugInstalls 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 catlog22/Claude-Code-Workflow --skill team-frontend-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/team-frontend-debug .github/skills/team-frontend-debug && 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 "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .github/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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 catlog22/Claude-Code-Workflow --skill team-frontend-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/team-frontend-debug .opencode/skills/team-frontend-debug && 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 "team-frontend-debug" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-frontend-debug into .opencode/skills/team-frontend-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-frontend-debug", 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.
team-frontend-debugFrontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow.
Team Frontend Debug is an agent skill from catlog22/Claude-Code-Workflow. Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files (for example `roles/analyzer/role.md`, `roles/coordinator/commands/analyze.md` and `roles/coordinator/commands/dispatch.md`).
It sits in Testing & QA, covering Browser testing, Debugging and QA and bug reports. It works with Chrome DevTools and Model Context Protocol. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
spawn_agent(*)wait_agent(*)send_message(*)followup_task(*)close_agent(*)list_agents(*)report_agent_job_result(*)request_user_input(*)Read(*)Write(*)…and 6 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Team Frontend Debug loads about 2.8k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 738 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), reAutomated 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.
The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 738 words, ~2,760 tokens.
.claude/skills/team-frontend-debug/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.Dual-mode frontend debugging: feature-list testing or bug-report debugging, powered by Chrome DevTools MCP.
Skill(skill="team-frontend-debug", args="feature list or bug description")
|
SKILL.md (this file) = Router
|
+--------------+--------------+
| |
no --role flag --role <name>
| |
Coordinator Worker
roles/coordinator/role.md roles/<name>/role.md
|
+-- analyze input → select pipeline → dispatch → spawn → STOP
|
┌──────────────────────────┼──────────────────────┐
v v v
[test-pipeline] [debug-pipeline] [shared]
tester(DevTools) reproducer(DevTools) analyzer
fixer
verifier| Input | Pipeline | Flow |
|---|---|---|
| Feature list / 功能清单 | test-pipeline | TEST → ANALYZE → FIX → VERIFY |
| Bug report / 错误描述 | debug-pipeline | REPRODUCE → ANALYZE → FIX → VERIFY |
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| tester | roles/tester/role.md | TEST-* | true |
| reproducer | roles/reproducer/role.md | REPRODUCE-* | false |
| analyzer | roles/analyzer/role.md | ANALYZE-* | false |
| fixer | roles/fixer/role.md | FIX-* | true |
| verifier | roles/verifier/role.md | VERIFY-* | false |
Parse $ARGUMENTS:
--role <name> → Read roles/<name>/role.md, execute Phase 2-4--role → roles/coordinator/role.md, execute entry routerCoordinator is a PURE ORCHESTRATOR. It coordinates, it does NOT do.
Before calling ANY tool, apply this check:
| Tool Call | Verdict | Reason |
|---|---|---|
spawn_agent, wait_agent, close_agent, send_message, followup_task | ALLOWED | Orchestration |
list_agents | ALLOWED | Agent health check |
request_user_input | ALLOWED | User interaction |
mcp__ccw-tools__team_msg | ALLOWED | Message bus |
Read/Write on .workflow/.team/ files | ALLOWED | Session state |
Read on roles/, commands/, specs/ | ALLOWED | Loading own instructions |
Read/Grep/Glob on project source code | BLOCKED | Delegate to worker |
Edit on any file outside .workflow/ | BLOCKED | Delegate to worker |
Bash("ccw cli ...") | BLOCKED | Only workers call CLI |
Bash running build/test/lint commands | BLOCKED | Delegate to worker |
If a tool call is BLOCKED: STOP. Create a task, spawn a worker.
No exceptions for "simple" tasks. Even a single-file read-and-report MUST go through spawn_agent.
TFD.workflow/.team/TFD-<date>-<slug>/ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)mcp__ccw-tools__team_msg(session_id=<session-id>, ...)Coordinator MUST resolve paths at Phase 2 before spawning workers:
Bash({ command: "pwd" }) → capture project_root (absolute path)skill_root = <project_root>/.claude/skills/team-frontend-debugteam-session.json:{ "project_root": "/abs/path/to/project", "skill_root": "/abs/path/to/skill" }role_spec values MUST use <skill_root>/roles/<role>/role.md (absolute)This ensures workers always receive an absolute, resolvable path regardless of their working directory.
All browser inspection operations use Chrome DevTools MCP. Reproducer and Verifier are primary consumers.
| Tool | Purpose |
|---|---|
mcp__chrome-devtools__navigate_page | Navigate to target URL |
mcp__chrome-devtools__take_screenshot | Capture visual state |
mcp__chrome-devtools__take_snapshot | Capture DOM/a11y tree |
mcp__chrome-devtools__list_console_messages | Read console logs |
mcp__chrome-devtools__get_console_message | Get specific console message |
mcp__chrome-devtools__list_network_requests | Monitor network activity |
mcp__chrome-devtools__get_network_request | Inspect request/response detail |
mcp__chrome-devtools__performance_start_trace | Start performance recording |
mcp__chrome-devtools__performance_stop_trace | Stop and analyze trace |
mcp__chrome-devtools__click | Simulate user click |
mcp__chrome-devtools__fill | Fill form inputs |
mcp__chrome-devtools__hover | Hover over elements |
mcp__chrome-devtools__evaluate_script | Execute JavaScript in page |
mcp__chrome-devtools__wait_for | Wait for element/text |
mcp__chrome-devtools__list_pages | List open browser tabs |
mcp__chrome-devtools__select_page | Switch active tab |
Coordinator spawns workers using this template:
spawn_agent({
agent_type: "team_worker",
task_name: "<task-id>",
fork_turns: "none",
message: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
requirement: <task-description>
inner_loop: <true|false>
Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>
## Upstream Context
<prev_context>`
})After spawning, use wait_agent({ timeout_ms: 1800000 }) to collect results. If result.timed_out, send STATUS_CHECK via followup_task (wait 3 min), then FINALIZE with interrupt (wait 3 min), then mark timed_out and close agents. Use close_agent({ target }) each worker.
Debug workflows require tool-heavy interaction (Chrome DevTools MCP). Reasoning effort varies by role.
| Role | reasoning_effort | Rationale |
|---|---|---|
| tester | medium | Systematic feature testing via DevTools, follows test plan |
| reproducer | medium | Reproduce bugs via DevTools interaction steps |
| analyzer | high | Root cause analysis requires deep reasoning about evidence |
| fixer | high | Code fixes must address root cause precisely |
| verifier | medium | Verification follows defined success criteria via DevTools |
| Command | Action |
|---|---|
check / status | View execution status graph |
resume / continue | Advance to next step |
revise <TASK-ID> [feedback] | Revise specific task |
feedback <text> | Inject feedback for revision |
retry <TASK-ID> | Re-run a failed task |
| Intent | API | Example |
|---|---|---|
| Queue supplementary info (don't interrupt) | send_message | Send DevTools evidence to running analyzer |
| Assign new work / trigger debug round | followup_task | Assign re-fix after verification failure |
| Check running agents | list_agents | Verify agent health during resume |
Use list_agents({}) in handleResume and handleComplete:
// Reconcile session state with actual running agents
const running = list_agents({})
// Compare with team-session.json active tasks
// Reset orphaned tasks (in_progress but agent gone) to pendingWorkers are spawned with task_name: "<task-id>" enabling direct addressing:
send_message({ target: "ANALYZE-001", message: "..." }) -- send evidence from reproducer to analyzerfollowup_task({ target: "FIX-001", message: "..." }) -- assign fix based on analysis resultsclose_agent({ target: "VERIFY-001" }) -- cleanup after verificationWhen verifier reports a fix did not resolve the issue, coordinator uses followup_task to trigger re-analysis and re-fix:
// Verifier reports failure -> coordinator dispatches re-fix
followup_task({
target: "FIX-001", // reuse existing fixer if inner_loop, or spawn new
message: `## Re-fix Assignment
verification_result: FAIL
failure_evidence: <verifier's screenshot/console evidence>
previous_fix_summary: <what was tried>
instruction: Analyze verification failure and apply corrected fix.`
})This pattern enables iterative debug rounds: FIX -> VERIFY -> re-FIX -> re-VERIFY (max 3 rounds).
When pipeline completes, coordinator presents:
functions.request_user_input({
questions: [{
question: "Pipeline complete. What would you like to do?",
header: "Completion",
multiSelect: false,
options: [
{ label: "Archive & Clean (Recommended)", description: "Archive session, clean up" },
{ label: "Keep Active", description: "Keep session for follow-up debugging" },
{ label: "Export Results", description: "Export debug report and patches" }
]
}]
}).workflow/.team/TFD-<date>-<slug>/
├── team-session.json # Session state + role registry
├── evidence/ # Screenshots, snapshots, network logs
├── artifacts/ # Test reports, RCA reports, patches, verification reports
├── wisdom/ # Cross-task debug knowledge
└── .msg/ # Team message bus| Scenario | Resolution |
|---|---|
| All features pass test | Report success, pipeline completes without ANALYZE/FIX/VERIFY |
| Bug not reproducible | Reproducer reports failure, coordinator asks user for more details |
| Browser not available | Report error, suggest manual reproduction steps |
| Analysis inconclusive | Analyzer requests more evidence via iteration loop |
| Fix introduces regression | Verifier reports fail, coordinator dispatches re-fix |
| No issues found in test | Skip downstream tasks, report all-pass |
| Unknown command | Error with available command list |
| Role not found | Error with role registry |
© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 11 other files in .codex/skills/team-frontend-debug of catlog22/Claude-Code-Workflow.
Open the folder on GitHubat commit 07491b0
Team Frontend Debug 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Frontend Debug this skillcatlog22/Claude-Code-Workflow | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Extension Puppeteer Debuggingmengxi-ream/read-frog | 10k | — | ~2k | Automated safety check: Notes | GPL-3.0 | |
| Diff-Driven Smoke TestsSkyvern-AI/skyvern | 23k | — | ~5.2k | Automated safety check: Pass | AGPL-3.0 | |
| Chrome Devtoolstech-leads-club/agent-skills | 7k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Doctorbluzir/claude-code-design | 106 | — | ~931 | Automated safety check: Pass | None | |
| Chrome Devtools MCPmanagedcode/dotnet-skills | 486 | — | ~2.2k | Automated safety check: Pass | MIT |
mengxi-ream/read-frog
Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.
Skyvern-AI/skyvern
Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.
tech-leads-club/agent-skills
Browser debugging, performance profiling, and automation via Chrome DevTools MCP.
bluzir/claude-code-design
First-run setup + health check. An agent skill from bluzir/claude-code-design.
managedcode/dotnet-skills
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.
addyosmani/agent-skills
Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.
catlog22/Claude-Code-Workflow
Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.
catlog22/Claude-Code-Workflow
CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.
catlog22/Claude-Code-Workflow
Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Check workflow delegation prompts against agent role definitions for content separation violations.
Works with
Categories
Frontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow. Team Frontend Debug is an agent skill from catlog22/Claude-Code-Workflow. Frontend debugging team using Chrome DevTools MCP.
Team Frontend Debug fits situations like: team-frontend-debug; tasks that involve Browser testing; tasks that involve Debugging.
Run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend-debug -a claude-code`. Or copy the skill folder (.codex/skills/team-frontend-debug in catlog22/Claude-Code-Workflow) into .claude/skills/team-frontend-debug in your project. Claude Code loads it when a task matches its description.
Run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend-debug -a codex`. Or copy the skill folder (.codex/skills/team-frontend-debug in catlog22/Claude-Code-Workflow) into .agents/skills/team-frontend-debug in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-frontend-debug, .gemini/skills/team-frontend-debug, .github/skills/team-frontend-debug and .opencode/skills/team-frontend-debug in your project.
SKILL.md names no scripts, command-line tools or credentials: Team Frontend Debug is instructions for the agent only. Its frontmatter pre-approves these tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__chrome-devtools__*(*), mcp__ccw-tools__team_msg(*).
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.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Team Frontend Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k 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.
Skills that share tags, products or a category with Team Frontend Debug: Extension Puppeteer Debugging (mengxi-ream/read-frog, 10k stars), Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars), Chrome Devtools (tech-leads-club/agent-skills, 7k stars) and Doctor (bluzir/claude-code-design, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.
Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.