ingpoc/skills

determinism

Design machine-checkable assertions, stable hashes, fixtures, and exit-code contracts for behavior that must be reproducible.

First seen Jan 25, 2026

Installation

$ npx skills add ingpoc/skills --skill determinism

Summary

  • Design machine-checkable assertions, stable hashes, fixtures, and exit-code contracts for behavior that must be reproducible.
  • Use when an outcome currently depends on subjective agent judgment or when prompts and generated artifacts need versioned integrity checks.
  • Do not use merely to run an existing repository verification gate; that is verify's job.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ingpoc/skills · top by installs.

npx skills add ingpoc/skills

Browse all from ingpoc/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 9
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,463 B
  • docs SUMMARY.md 373 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

Determinism

Turn a repeated judgment into an executable contract.

Procedure

  1. Name the exact input, expected invariant, and authoritative readback.
  2. Use the simplest deterministic mechanism: parser, schema, fixture, checksum, query, or narrow test.
  3. Return a meaningful exit status: 0 for satisfied, nonzero for a specific failure class.
  4. Keep diagnostics compact and stable enough for another script or agent to consume.
  5. Version prompts or generated contracts when their semantics affect the result; record a hash when drift must be detected.
  6. Prove both a passing case and a deliberately failing case.

Boundary

  • determinism designs the assertion or integrity mechanism.
  • verify selects and runs the repository's declared gates.
  • testing skills construct broader behavioral test suites.

References

  • [references/code-verification.md](references/code-verification.md) — executable assertion patterns.
  • [references/prompt-versioning.md](references/prompt-versioning.md) — semantic versions and hashes for prompt contracts.