Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions skills/maya-plugin-e2e/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,24 @@ Run real Maya plugin proof without rediscovering the same traps. Prefer determin
6. Inspect Scenario Result JSON first, then screenshots/recordings, logs, and saved scene.
7. Close only with exact-head proof: commit, CI artifact job/id/hash/size, run id, screenshot/recording paths/sizes, Scenario Result fields, confidentiality pass.

## Consuming Repo Contract

Do not create a project-specific copy of this skill. Make each consuming repo
own the deterministic test inputs:

- `.maya-stall.yaml` with named Scenario, `pluginArtifacts`, Maya scripts,
expected outputs, Visual Evidence, and Validators;
- a checked-in Maya script that drives real product controls and writes the
Scenario Result;
Comment on lines +27 to +30
- a short repo doc with exact build, artifact download, `plan`, `doctor`, and
`run` commands;
- an `AGENTS.md` route to this skill and the repo doc.

Keep Host Config outside the repo. Prefer a stable operator-owned path such as
`~/.config/maya-stall/hosts.yaml`, selected through `MAYA_STALL_HOST_CONFIG`.
The skill owns the workflow; the consuming repo owns product assertions; the
host config owns private infrastructure and trust policy.

## Preflight

Use exact queries; do not print secrets or full host configs.
Expand Down
Loading