Skip to content

build(skills): manage third-party skills with skills.sh - #2616

Open
spike-rabbit wants to merge 1 commit into
mainfrom
build/update-playwright-skill
Open

build(skills): manage third-party skills with skills.sh#2616
spike-rabbit wants to merge 1 commit into
mainfrom
build/update-playwright-skill

Conversation

@spike-rabbit

@spike-rabbit spike-rabbit commented Aug 25, 2026

Copy link
Copy Markdown
Member

Documents the project policy for managing third-party agent skills with skills.sh via npx skills.\n\nUpdates the Playwright CLI skill from microsoft/playwright-cli, records its source and hash in skills-lock.json, and excludes third-party skill sources from Prettier formatting.


Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@spike-rabbit
spike-rabbit force-pushed the build/update-playwright-skill branch from 22543e5 to d5ea680 Compare August 25, 2026 09:13
@spike-rabbit spike-rabbit changed the title build(skills): update Playwright CLI skill build(skills): manage third-party skills with skills.sh Aug 25, 2026
@spike-rabbit
spike-rabbit marked this pull request as ready for review August 25, 2026 13:21
@spike-rabbit
spike-rabbit requested review from a team as code owners August 25, 2026 13:21
@spike-rabbit spike-rabbit added the core-team-discussion Topics that should be discussed in the core team meeting label Aug 25, 2026
Comment thread DEVELOPER.md Outdated
@kfenner

kfenner commented Aug 27, 2026

Copy link
Copy Markdown
Member

I think this is fine for the moment. Even if skills.sh is not a real standard yet, we can change the solution at any time. IMHO, we can move forward with this 👍

@kfenner kfenner added discussion Topic needs to be discussed and clarified. It is blocked and not ready for implementation and removed core-team-discussion Topics that should be discussed in the core team meeting labels Aug 27, 2026
Comment thread DEVELOPER.md
Comment on lines +79 to +81
When adding a third-party skill, add its path under `.agents/skills/` to
`.prettierignore`. Third-party skill sources must not be reformatted by this
repository's Prettier configuration.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how about just using wildcard in prettierignore for skills folder

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have the problem, that the skills we maintain should be formatted by prettier.
Only 3rd part skills should be excluded.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can always use negation in that case !skills-maintained-by-us

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the question is what we want here?

  • should all skills be formatted by default and we manually exclude the 3rd party ones
  • no skill is formatted and we include ours manually

I think we should format all by default. Otherwise we may forget one of ours.

@spike-rabbit
spike-rabbit force-pushed the build/update-playwright-skill branch from d5ea680 to 50b12f1 Compare August 27, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

discussion Topic needs to be discussed and clarified. It is blocked and not ready for implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants