deploy-awid-site
Skill129 starsChanged 5 days agoMITView on GitHub
Deploy the reviewed aweb main commit to the awid.ai static site through its dedicated landing branch.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-review-disciplineSkill
- cross-repo-changeSkill
- releaseSkill
- aweb-bootstrapSkill
- aweb-coordinationSkill
- aweb-identitySkill
- aweb-messagingSkill
- aweb-tasksSkill
- aweb-team-membershipSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 13
After the outward production action has been authorized, run:
- Distinctive: line 25
After the branch advances, verify the Render deploy completed and that https://awid.ai plus both mirrored documents serve the intended …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy awid.ai
The site source is awid/site/. Its committed mirrors of
docs/identity-guide.md and docs/trust-model.md must already be current and
reviewed before deployment. If they are stale, run make sync-awid-site-docs,
commit the result, obtain review, and merge it normally.
After the outward production action has been authorized, run:
make deploy-siteThe command builds the site, refuses a dirty checkout or a commit other than
the fetched origin/main, requires a fast-forward from the current
deploy-awid-landing tip, pushes the exact main SHA, and reads the remote ref
back. It does not create a commit or participate in artifact release.
Render must be configured to build awid/site from deploy-awid-landing.
After the branch advances, verify the Render deploy completed and that
https://awid.ai plus both mirrored documents serve the intended content.
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.

