agentsclimarketplace

Cyber mysophobia

Skill PRO-2684/skills/skills/cyber-mysophobia

My personal skills gallery

Install
npx -y skills add PRO-2684/skills --skill cyber-mysophobia

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when Codex should modernize aggressively: prefer ideal architecture and API design, remove legacy/unused code, disregard compatibility, avoid outdated dependencies, reject lint/type errors, avoid suppression hacks, and replace silent fallbacks with explicit failures. Trigger on Cyber Mysophobia, uncompromising cleanup, modernization, API redesign, dependency refresh, legacy removal, lint/type strictness, explicit error handling, or compatibility-disregarding refactors.

SKILL.md

2.7 KB, 444 tokens by cl100k_base, as published. Nobody here has run it

Cyber Mysophobia

Prefer clean target design over compatibility. Delete rot. Break old contracts when cleaner.

Stance

Clean target shape wins over legacy continuity unless user explicitly requires compatibility. Prefer explicit failure over hidden accommodation.

Design Rules

  • Design first: idiomatic arch, narrow APIs, minimal surface.
  • Compatibility expendable unless user explicitly requires it.
  • Update all local callers to new contract; do not keep wrappers for old shape.

Deletion Rules

  • Delete unused code, dead branches, shims, aliases, deprecated paths, obsolete tests.
  • Use current maintained deps; remove stale dep imports/config/lockfile/docs.

Diagnostics

  • Lint/type errors intolerable. Fix every diagnostic, however small.
  • Avoid # type: ignore, lint disables, broad allowlists, fake casts. Use only when unavoidable; explain.

Failure Handling

  • Hate silent fallback. No swallowed errors, hidden defaults, temp workaround branches.
  • Prefer explicit error with precise fix path.

Guardrails

  • Preserve correctness, security, data integrity, explicit user constraints.

API Shape

  • Prefer methods, constructors, or associated functions over public free functions when behavior belongs to a type. Private helper functions are fine when they keep implementation readable without widening public surface.
  • Prefer typed domain objects over untyped maps, loose objects, or implicit structure.
  • Avoid wildcard imports/import-all forms; import explicit names unless language tooling makes that impractical.
  • Prefer explicit contracts over dynamic lookup, reflection, magic defaults, or convention-only coupling.
  • For CLI args, prefer dashed form (--model-path) over underlined form (--model_path).

Workflow

  1. Pick ideal new shape.
  2. Move callers.
  3. Delete old surface.
  4. Replace fallbacks with explicit errors; fix root cause.
  5. Update tests for new contract.
  6. Run formatter, linter, type checker, relevant tests.

Language Notes

Language-specific examples and exceptions live under langs/, with slug as file stem. List and read based on project language.

Communication

State target design, deletions, breaking changes, verification, remaining explicit failures.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.