Add create-site-skills to skills docs section

[dprevoznik]

Summary

• add a docs page for the create-agent-site-skill skill (turns verified browser workflows into reusable site-automation skills)
• register it in the Agent Skills nav group in docs.json
• link it from the skills overview page's "especially useful skills" list

Test plan

• validated docs.json is well-formed JSON
• followed the existing skill-stub pattern (title + skills.sh url) used by the other three skill pages

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only navigation and stub page changes with no runtime or security impact.

Overview
Documents the Create Site Skills agent skill by adding a Mintlify stub page that links to the create-agent-site-skill entry on skills.sh, following the same frontmatter pattern as the other skill pages.

The new page is wired into the Agent Skills sidebar in docs.json and listed on the skills overview under “Especially useful skills,” describing how agents can turn a verified browser workflow into reusable site automation.

^{Reviewed by Cursor Bugbot for commit b70b92a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 16, 2026, 6:20 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Risk Assessment: Very Low

Verdict: Approve

This PR adds a documentation stub for an existing skill page pattern. The diff is 3 files / 8 lines:

• skills/create-site-skills.mdx — new Mintlify stub with title + external skills.sh URL, matching bot-detection, profiles, and kernel-auth
• docs.json — registers the page in the Agent Skills sidebar group
• skills/overview.mdx — one additional overview bullet linking to the new page

No application logic, auth, infrastructure, or production codepaths are modified. Blast radius is limited to docs navigation and a new stub page. No CODEOWNERS file is present, so codeowner review is not required.

Risk factors considered: docs-only surface, small scoped change, no shared systems, no operational or security impact.

  

_{Sent by Cursor Automation: Assign PR reviewers}