Repository navigation
Place the example skill's helper in scripts/ and run the golden in a workflow (ADR C) - #21
Merged
Merged
Conversation
…workflow (ADR C) The template now starts a new capability in the shape the placement gate expects: one skill with a scripts/ directory and a golden that reads verification/fixtures/. - skills/example-workflow/scripts/example_helper.py: a standard library PEP 723 script that summarizes one column of a small CSV series (count, mean, sample standard deviation, range and a seeded bootstrap interval on the mean), with --json and --selftest. The SKILL.md invokes it through the plugin root, explains why a runtime helper lives in the skill's scripts/, and describes the golden in words instead of naming the goldens' tree (gate P4). - verification/fixtures/example_series.csv, written by the committed make_fixtures.py (closed-form, so the bytes are the same on every machine) and recorded in the fixtures README. The golden notebook reads it, computes the same statistic with numpy, imports the helper by path and asserts the two agree on the expected value and its uncertainty range. - .github/workflows/goldens.yml runs every notebook at the top of verification/ headless on the committed fixtures, with the action shas the plugin gate pins (gate P5). - .github/workflows/plugin-gate.yml runs osp.py placement-check right after plugin-check. - README.md names skills/<name>/scripts/ in the tree and the merge rules, and states the placement rule in one sentence citing ADR C. osp.py placement-check . --strict: PASSED (0 errors, 0 warnings). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DVKYxSeRJWncZVsmaxC4p4 Signed-off-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the template to the placement rule of ADR C (code placement by plane), so a capability copied from it starts in the shape
osp.py placement-checkexpects: one skill with ascripts/directory and a golden that readsverification/fixtures/. Roadmap deliverable c5-template-placement; closes #20.skills/example-workflow/scripts/example_helper.py: a standard-library PEP 723 script that summarizes one column of a small CSV series (count, mean, sample standard deviation, range and a seeded bootstrap interval on the mean), with--jsonand--selftest.SKILL.mdinvokes it through${CLAUDE_PLUGIN_ROOT}, explains why a runtime helper lives in the skill'sscripts/, and describes the golden in words instead of naming the goldens' tree.verification/fixtures/example_series.csv, written by the committedmake_fixtures.py(closed-form, so the bytes are the same on every machine) and recorded in the fixtures README. The golden notebook reads it, computes the same statistic with numpy, imports the helper by path and asserts the two agree on the expected value and its uncertainty range..github/workflows/goldens.ymlruns every notebook at the top ofverification/headless on the committed fixtures, with the action shas the plugin gate pins..github/workflows/plugin-gate.ymlrunsosp.py placement-checkright afterplugin-check.README.mdnamesskills/<name>/scripts/in the tree and the merge rules and states the placement rule in one sentence citing ADR C.Checks from the repository root:
osp.py validate --standalone,render --check,plugin-check,advertise --check,placement-check --strict(PASSED, 0 errors, 0 warnings; main reported P4 and P5),check_okf_v02.py,check_script_deps.py(3 scripts),check_prose.py(clean),signature_check.py --report, the golden and the helper selftest all pass.osp.py lock --reportlists the skills and verification digests as stale beside the evals and knowledge digests that were already stale; a release commit re-runsosp.py lock.🤖 Generated with Claude Code
https://claude.ai/code/session_01DVKYxSeRJWncZVsmaxC4p4
Generated by Claude Code