General-purpose coding policy for Baruch's AI agents
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
These preconditions bind the exceptions named in rules/script-delegation.md.
Applies to another plugin's scoped skill lookup or stdout contract, for an installed plugin or one authored in its own verified repository.
Preconditions (all required):
Every other command block follows Scripts Are Real Files and Script Requirements unchanged.
rules/ci-safety.md names the release readback scope and co-shipped targets.
The consumer resolves only the host-installed jbaruch/coding-policy provider;
caller data cannot choose a replacement root or executable. Resolve an
installation-root alias once, then validate the actual provider manifest's
name, version, declared release skill and declared authority rule. Each target
must be a regular contained file under that same provider. Refuse linked
target components, missing files and provider/target substitution before
execution. Retain the verified provider identity across the readback sequence.
The helpers retain their own watch budgets and publication gates. Their input,
output, exit-code and recovery contracts are canonical in
skills/release/references/PUBLICATION.md; the confirmation helper's successful
version stdout also follows Version Stdout below.
A successful lookup never substitutes for successful source-bound publication,
registry advance or moderation. Readback grants no approval of changed bytes.
The central fleet mode co-ships fleet_publish_resolver.py and
fleet_publish_confirm.py under the same verified release provider. Their JSON
selection and confirmation contracts are declared in their docstrings and
skills/release/references/fleet-publication.md. Neither changes the legacy
version-stdout helper contract. Central source identity is separate from the
workflow's own commit; resolve and retain both through confirmation.
Provider regressions live in tests/release/tests/test_resolve_publish_run.sh,
tests/release/tests/test_release_helpers.sh and
tests/release/tests/test_verify_moderation_cleared.sh. Consumer lookup and
link/substitution refusal coverage lives in jbaruch/nanoclaw-admin
tests/test_learning_delivery.py.
Applies to skills/release/registry-baseline.sh and
skills/release/confirm-tessl-landed.sh when the wrapper's whole output is the
version or verified unpublished baseline its caller passes to the next gate command.
Preconditions (all required):
unpublished requires verified registry absence or a supported empty versions response; authentication failures and indeterminate reads never prove absence.Every other release script retains the JSON-producing requirement.
Applies to skills/release/lib/bounded-run.sh when a caller runs another script
under a wall-clock budget.
Preconditions (all required):
Every other skill script retains the JSON-producing requirement.
.tessl-plugin
rules
skills
coding-contracts
migrate-to-plugin
onboard-repo
release
hooks
references