validate-before-share
Skill0 starsChanged 2 months agoMITView on GitHub
Verify URLs, previews, and endpoints yourself (HTTP 200, correct content) before sharing with the user. Use when about to send a link, deploy URL, local dev URL, or "open this to test".
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/automate-before-manual.mdcCursor rule
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- google-calendar-mcpSkill
- init-fmzSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- skills-sh-maintainerSkill
- ui-change-e2eSkill
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 12
Before sending the user any URL, preview, endpoint, build, or screen to open:
- Distinctive: line 22
Do not say "try this link" or "should work" without evidence from step 1.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Validate before share
Before sending the user any URL, preview, endpoint, build, or screen to open:
1. Verify yourself
- HTTP GET (or equivalent) on the URL
- Confirm 200 (or expected redirect chain ends OK)
- Confirm content matches intent: page title, hero text, JSON shape — not a generic health stub alone when the user cares about the product UI
2. Only share after pass
Do not say "try this link" or "should work" without evidence from step 1.
3. On failure
Fix or restart the environment, re-validate, then share. Report the effective URL (including port or path if different from default).
4. Production vs local
| Context | Minimum check |
| Local dev | Title or documented health route |
| Production | User-facing URL from docs/commit-push.json or project docs; match expectTitle / expectInBody when configured |
| API only | Response body matches contract — not empty 200 |
Pair with finish-with-dev-server for local URLs after coding tasks.
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.

