skill-maintenance
Skill13 starsChanged 26 days agoMITView on GitHub
Maintain the Frontend Testing Skill in this repo. Use when asked to review the skill, run a spec/quality review, install-local (wire one example app to the local marketplace), sync up (an example app → root), install-marketplace (switch the vitest-browser app to the published GitHub marketplace), run a sanity test of the skill end-to-end (single app or the monorepo example, per package), run validate-release (install from GitHub marketplace → sanity → restore) against the vitest-browser app, or create a fresh example app copy at a given path for manual install testing.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- delorenj/skillstheir own version, first seen Nov 7, 2026
- ComposioHQ/composiotheir own version, first seen Nov 5, 2026
- LuisUrrutia/skillstheir own version, first seen Nov 1, 2026
- Gopyr/gopyr-skills-hubtheir own version, first seen Oct 11, 2026
- m2ai-mcp-servers/claude-skillstheir own version, first seen Oct 11, 2026
- CowboyLogic/ai-devtheir own version, first seen Oct 11, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- ComposioHQ/composio★ 31ksame name
- SRombauts/SQLiteCpp★ 2.8ksame name
- delorenj/skills★ 17same name
- meteor/agent-skills★ 10same name
- CowboyLogic/ai-dev★ 4same name
- LuisUrrutia/skills★ 2same name
- yuanJewel/skills★ 2same name
- DojoGenesis/openclaw-plugin★ 0same name
- gclm/super-stack★ 0same name
- Gopyr/gopyr-skills-hub★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- example-app-playwright/AGENTS.mdAGENTS.md
- example-app-vitest-browser/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- example-app-playwright/CLAUDE.mdCLAUDE.md
- example-app-vitest-browser/CLAUDE.mdCLAUDE.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- practica-brand-designSkill
- vercel-react-best-practicesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Keep all maintenance docs short.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Maintenance
A toolkit for local maintainers of this repo. It reviews, syncs, and sanity-tests
the Frontend Testing Skill, whose source of truth is
plugin/frontend-testing/ (this is what ships to users). The two example apps —
example-app-vitest-browser/ and example-app-playwright/ — resolve the skill
via a local marketplace reference; no skill files are embedded in them. The root
the-testing-skill/ tree is deprecated; ignore it.
Keep all maintenance docs short. Trust your judgment and ask the user when unsure.
Operations
Pick the matching reference doc and follow it.
| When the user asks to… | Read |
| review / audit the skill, check the spec, find issues | references/review.md |
| install local — wire one named example app to the local marketplace (the current, non-copy way both apps are actually set up) | references/install-local.md |
| sync up — pull one named example app back to root | references/sync-up.md |
| install-marketplace — switch vitest-browser from local wiring to the published GitHub marketplace | references/install-marketplace.md |
| sanity-test the skill end-to-end (build a feature, verify tests) | references/sanity-test.md |
sanity-test the skill in the monorepo (example-monorepo, per package) | references/sanity-test-monorepo.md |
| validate-release — install from GitHub marketplace → sanity → restore, on vitest-browser | references/validate-release.md |
| publish / release the skill to the Claude plugin marketplace | references/publish-claude.md |
| publish / release the skill to the Cursor marketplace | references/publish-cursor.md |
| fresh example app — copy vitest-browser to a path, stripped of skill/marketplace, ready for a clean install | references/fresh-example-app.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.