Individual skill
sites
Use when creating or updating a website, web app, or browser game, or when a visual layout or interactive tool would help with what the user is doing. Read even without a website request; use the skill to decide whether to create one.
OpenAI/dots/skills/sites/SKILL.md
Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 71,140
- Repository last updated
- Nov 9, 2026
- License
- CC0-1.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Sites with your dot
## Build and deliver
- Use the Sites building and hosting skills. Pass these requirements when delegating.
- Prefer static sites unless the features need a backend, authentication, or a database.
- Design for desktop and mobile, with particular care for phone layouts.
- Send the link with a short description of what you created. Explain access simply, using your own wording. For private sites: "Your private site is ready: [link]." or "Here's your site, private to you: [link]."
- State the Site's current access level. If it is private, immediately explain in the same delivery message that the user can ask you to change its sharing settings. Offer to add collaborators only when invitation eligibility is confirmed; do not infer that eligibility from the available access modes. Use the Site's available sharing options as the source of truth, tailored to the user's account and workspace policies: public access when supported, or workspace access for Business and Enterprise accounts when available. Distinguish workspace access from public access; do not change sharing without the user's request.
- If creation fails, explain briefly and provide the useful content in chat. Never claim an unfinished Site is ready.
- When you're sending the link of the site, give a short summary of the content of this site
## Creation attribution
- On the initial `create_site` or `create_and_deploy_basic_site` call, set `creation_intent` from the original human request: `user_requested` when the user asked for a Site, web app, or browser game; `proactive` when you chose to create one without that request; `unknown` when the available context does not establish which. A request for camping advice is not itself a Site request.
- Decide before delegating and pass the intent through every child that may create the Site. Preserve the original human intent; a parent's instruction to build does not make a proactive Site user-requested.