check-entropy-runtime
Check the optional pinned JSON Schema runtime required by entropy evidence helpers and hooks without installing software.
- License 许可
- MIT
- 所属仓库
- dasobral/skills
- 最近更新
- 2026-08-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- check-entropy-runtime
- metadata
- { "internal": true }
- description
- Check the optional pinned JSON Schema runtime required by entropy evidence helpers and hooks without installing software.
02 资源文件 3
- 参考文档index.json716 B
- 脚本scripts/check_runtime.py860 B
- 脚本scripts/register_control_state.py5.1 KB
03 SKILL.md 正文
Check Entropy Runtime
Run python3 scripts/check_runtime.py.
The check is read-only and idempotent. It does not install or upgrade packages. If it reports evidence-gap, show the setup guidance and obtain user approval before they install jsonschema==4.26.0; then rerun the check.
Provision a non-writable Ed25519 public key outside the project. Set ENTROPY_FLIGHT_RECORDER_TRUST_BOUNDARY to its explicit managed boundary, ENTROPY_FLIGHT_RECORDER_TRUST_ROOT to the key within that boundary, and optionally ENTROPY_FLIGHT_RECORDER_TRUSTED_UID for a non-root provisioning owner. Every component from boundary through key must be non-symlink, trusted-owned, non-writable by group/other, and non-replaceable by the invoking user. First run:
python3 scripts/register_control_state.py --state-dir "$PLUGIN_DATA/entropy-flight-recorder" --project-root "$PWD" --artifact /trusted/candidate/entropy-baseline.json --approver-id ID --signed-at UTC_TIMESTAMP --prepare
Sign the canonical signing_payload externally, then rerun with the same arguments and --signature SIGNATURE. Registration never creates a private signing key and refuses missing, writable, or invalid trust roots and signatures with evidence-gap. The signed payload binds plugin, approver identity, timestamp, baseline digest, decision, and prior entry. A mode-0600 HMAC chain protects local storage only after signature verification.
04 同仓库更多 Skills
fixture-skill
Fixture skill used to prove trust inventory coverage.
write-conformant-code
Write code in any language that matches project conventions exactly. Reads CODING_REQUIREMENTS.md, prior review output, or built-in defaults before writing. Part of Codecraft pipeline: analyze → write → review → audit. Use when implementing features, functions, or any code that should fit seamlessly into an existing codebase.
test-crypto-interoperability
Record reproducible cryptographic interoperability cases, including negotiation, fallback, sizes, latency, fragmentation, and negative tests.
scientific-platform-architect
Design scientific computing platforms combining HPC kernels with modern infrastructure. Enforces compute-layer separation (Rust/PyTorch/Python), emulator-first thinking, and right-sized infrastructure. Use for MCMC pipelines, neural emulators, platform design, or scientific code review.
rust-systems
Rust systems engineering for daemons, HTTP APIs, and AOS components. Enforces Tokio/Axum async-first, LiteLLM-compatible OpenAI APIs, workspace layouts, tracing, and systemd-compatible daemon design. Part of AOS Stack plugin. Use for .rs files, Cargo.toml, daemons, or Rust orchestrator services.
run-agent-attack-replay
Aggregate isolated agent attack trials with deterministic side-effect assertions, Wilson intervals, and preserved trace evidence.