Write an approved site skill so it survives small UI changes and fails loudly when it does not — handles, assertions, provenance.
danielrosehill/Claude-Site-Skill-Builder-Plugin
SkillsMP has collected 10 skills from danielrosehill/Claude-Site-Skill-Builder-Plugin. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 10
- GitHub stars
- 1
- GitHub forks
- 0
Skills in this repository
Showing 10 of 10 collected skills.
Re-verify a site plugin's load-bearing routes and handles, and report CHANGED with what moved — before a user hits it as a wrong answer.
Map the JSON endpoints a site's own pages call, so skills can read data from a stable endpoint instead of scraping rendered markup.
Observe one page or a list of pages in the browser and write an observation note — what data is there and which durable handles reach it.
Decide how to reach a site — the user's own signed-in Chrome by default, headless Playwright for public pages, plain fetch when it works.
Turn observations of a site into a ranked roster of candidate skills for the user to approve or reject before any are written.
Classify every observation as publishable, private, or never-recorded before committing — plus the stop rule for security findings.
Fix a site skill that broke when the site changed — re-observe the surface, move the handle up the ladder, and record what moved.
Start building a plugin for a website — capture the target, the page list, the account posture, and what the skills must do. Run this first.
Write or update the site profile JSON — the one file holding every volatile fact about a site, so a redesign is a one-file edit.