plugin-creator validator rejects policy.products in skill agent metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
The bundled plugin-creator validator rejects policy.products in a skill's agents/openai.yaml metadata, even though product restrictions are supported by the skill metadata model.
Minimal reproduction
interface:
display_name: Example
short_description: Example skill
policy:
products:
- chatgpt
- codex
allow_implicit_invocation: true
Run:
python3 scripts/validate_plugin.py <plugin-root>
Actual behavior
Validation fails because policy.products is reported as an unsupported field.
Expected behavior
Validation should accept policy.products when it is a non-empty array of non-empty strings, while continuing to reject malformed values.
Proposed fix
Add products to the allowed skill-agent policy fields and validate its array shape. Add regression coverage for both a valid product list and malformed values.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with scripts/validate_plugin.py and trace validation of skill agents/openai.yaml policy fields. Add regression coverage for a non-empty products list and malformed values, then run python3 scripts/validate_plugin.py to confirm valid metadata is accepted and invalid shapes remain rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100