feat(skills): separate public and contributor workflows - #2899
feat(skills): separate public and contributor workflows#2899johnnygreco wants to merge 4 commits into
Conversation
|
🌿 Preview your docs: https://nvidia-preview-pr-2899.docs.buildwithfern.com/openshell |
|
lgtm @johnnygreco but you'll need to rebase and resolve conflicts then can re-stamp |
44b4c7a to
3c8523c
Compare
|
/ok to test 3c8523c |
3c8523c to
4f4632f
Compare
|
/ok to test 4f4632f |
4f4632f to
9d23899
Compare
|
@johntmyers This is rebased onto the latest |
|
/ok to test 9d23899 |
Closes #2736 Publish the four user-facing OpenShell skills from the top-level skills directory, mark contributor workflows internal, and update portability guidance, validation, and documentation. Signed-off-by: Johnny Greco <jogreco@nvidia.com>
Signed-off-by: Johnny Greco <jogreco@nvidia.com>
Signed-off-by: Johnny Greco <jogreco@nvidia.com>
Signed-off-by: Johnny Greco <jogreco@nvidia.com>
9d23899 to
64b8ca3
Compare
|
/ok to test 64b8ca3 |
| ## Authoritative References | ||
|
|
||
| See [cli-reference.md](cli-reference.md) for the current command tree and commonly used flags. Use it as a quick-reference, then confirm uncommon or security-sensitive options with `--help`. | ||
| Use `openshell --help` and nested `--help` output as the authority for the installed CLI version. Use the published documentation for product concepts and supported workflows: |
There was a problem hiding this comment.
I'm curious about adding something to the CLI that will give agent a reference, so it doesn't need to explore the nested commands each time (and potentially if there are 2 ways of doing something, e.g. port forward and service exposure, it can select one thing it finds, where the other may fit better).
3 participants
Summary
Publish the four user-facing OpenShell skills as a portable top-level collection while keeping repository contributor workflows internal. Public skills now use installed CLI help and published documentation as their sources of truth, and repository guidance clearly distinguishes using OpenShell from developing it.
Related Issue
Closes #2736
Changes
openshell-cli,generate-sandbox-policy,debug-inference, anddebug-openshell-clustertoskills/..agents/skills/with internal discovery metadata.sync-agent-infrato validate audience placement, metadata, unique names, references, portability, and public discovery.Deviations from Plan
None — implemented as planned.
Testing
npx -y skills add <disposable-local-copy> --listfinds exactly the four public skills.mise run pre-commitpasses.mise run docspasses with zero errors.mise run cipasses. An initial Go SDK test returned a transientEOF;mise run go:ciand the full CI rerun both passed.Checklist
Documentation updated:
README.md: public versus contributor skills and thenpx skills add NVIDIA/OpenShellinstallation command.AGENTS.mdandCONTRIBUTING.md: canonical locations, inventories, and maintenance guidance.docs/CONTRIBUTING.mdxanddocs/get-started/quickstart.mdx: contributor workflow distinction and public skill installation.