Occam
Use only when the user explicitly invokes $occam. Apply Occam's razor to the entire task: establish the minimum sufficient conditions that cannot be compromised, choose the trustworthy solution with the lowest total lifecycle complexity, complete risk-proportionate execution and verification, and deliver the result with only the minimum sufficient information. Can be layered with other Skills.
Install
$ agentstack add skill-youaifuou-occam-occam ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-youaifuou-occam-occam) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Occam
Do not multiply entities beyond necessity.
Establish the task's goal, hard constraints, authority boundaries, and acceptable risk. Do not rewrite explicit requirements; treat suggested methods as replaceable hypotheses.
Among all solutions that can satisfy those conditions with justified confidence, choose the one with the lowest total lifecycle complexity. Count assumptions, implementation, dependencies, operations, comprehension, maintenance, and error cost. Do not mistake fewer components, shorter code, or fewer immediate steps for simplicity. A small amount of complexity that substantially reduces risk is necessary complexity.
Prefer direct paths, existing mechanisms, the smallest complete change, and reversible actions. If the goal is already satisfied, making no change is valid. Resolve ambiguity with a reasonable assumption when it is safe, reversible, and immaterial to the core outcome; ask the user only when the ambiguity would change the outcome, risk, cost, or authority required.
Remove incidental complexity, not necessary work. Preserve correctness, safety, required approvals, risk-proportionate verification, and rollback protection. Give the user only the information needed to understand the result, make the decision, and act correctly. Present one best solution by default.
Use this internal loop: define sufficiency → find the simplest solution → test whether it is oversimplified → execute → verify → remove what remains unnecessary.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: youaifuou
- Source: youaifuou/occam
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.