assumption-vs-fact-labeling
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Use in any status update, handoff, or report — label what was confirmed by reading actual output versus what is inferred or assumed. Applies beyond debugging to all communication.
In this repository13 other files it gives its agents.
- batch-job-safetySkill
- destructive-action-confirmationSkill
- lesson-captureSkill
- multi-service-secrets-setupSkill
- neondb-connection-safetySkill
- no-silent-failuresSkill
- prompt-injection-awarenessSkill
- replit-project-bootstrapSkill
- secrets-hygieneSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- verify-delegated-workSkill
- vite-replit-configSkill
The file
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.