Skip to content

chore: add workflow to sync webperf skills from webperf-snippets#1106

Closed
nucliweb wants to merge 1 commit intoChromeDevTools:mainfrom
nucliweb:feat/sync-webperf-skills
Closed

chore: add workflow to sync webperf skills from webperf-snippets#1106
nucliweb wants to merge 1 commit intoChromeDevTools:mainfrom
nucliweb:feat/sync-webperf-skills

Conversation

@nucliweb
Copy link
Copy Markdown

@nucliweb nucliweb commented Mar 4, 2026

Motivation

WebPerf skills originate in nucliweb/webperf-snippets. This PR proposes a GitHub Actions workflow to automate keeping them in sync, so new releases are picked up automatically without manual intervention.

How it works

  • Checks the latest release from nucliweb/webperf-snippets
  • Compares it against the last synced version stored in .github/webperf-snippets-version
  • If a new release is available:
    • Downloads and extracts the skills into skills/
    • Adapts tool references from the standalone format (mcp__chrome-devtools__tool_name) to the MCP server internal format (tool_name)
    • Opens a PR with the changes
  • Skips gracefully if already up to date or if a PR for that version already exists

Schedule

The workflow runs every Monday at 09:00 UTC — this is a proposal and the cadence can be adjusted or replaced with a different trigger. It also supports manual runs via workflow_dispatch.

Example execution

You can see the workflow in action here: nucliweb/chrome-devtools-mcp#2

@natorion
Copy link
Copy Markdown
Contributor

natorion commented Mar 5, 2026

In general I think it would be great to have the skills available within the DT MCP, thank you @nucliweb! I have a few remarks though:

  • I don't think we want an automated import of 3rd party content.
  • I think it makes sense first to migrate the skills over to this repo 1-by-1 - in particular because I also expect we will have to make some changes to optimize them for the MCP.

@OrKoN @devnook @matthiasrohmer for thoughts too please.

@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented Mar 5, 2026

Yes, we cannot mix third party code (skills in this case) with our own. I also was thinking that if you are open to upstreaming the skills we can maintain them here (+ we already have some skills around performance) so it probably makes sense to have skills be consistent and in the same style (instead of a second set of skills).

@nucliweb
Copy link
Copy Markdown
Author

nucliweb commented Mar 5, 2026

Ok, make sense, I'll send another PR with the skills.

@natorion @OrKoN, WDYT about the structure and naming?

  • webperf
  • webperf-core-web-vitals
  • webperf-interaction
  • webperf-loading
  • webperf-media
  • webperf-resources

@nucliweb nucliweb closed this Mar 5, 2026
@nucliweb nucliweb deleted the feat/sync-webperf-skills branch March 5, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants