Agent Skills: rtvi-cv-scaffold-vss-service declares compatibility inside metadata
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, yaml
- Domain
- developer-experience
Research direction
The problem is in the frontmatter of skills/rtvi-cv-scaffold-vss-service/SKILL.md, where compatibility sits under metadata. Read the Agent Skills spec at agentskills.io to confirm the expected top-level layout, then move the compatibility key (Python 3.10+ and the VSS prerequisites) up to the top level. Done when the field is top-level, metadata no longer holds it, and the rest of the frontmatter is unchanged. The reporter's branch linked in the issue shows one possible edit to compare against.
Written by the indexing model from the issue text.
Description
Agent Skills: rtvi-cv-scaffold-vss-service declares compatibility inside metadata
While reviewing the skills in this repository against the Agent Skills specification, I found that skills/rtvi-cv-scaffold-vss-service/SKILL.md declares its compatibility field nested inside metadata instead of at the top level. Spec-conformant harnesses read the top-level compatibility field, so the requirements (Python 3.10+, VSS deployment prerequisites) are effectively invisible to them.
Fix available at https://github.com/janEbert/DeepStream/tree/fix-agent-skills.
- Dominant language
- C++
- Stars
- 270
- Forks
- 59
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from NVIDIA/DeepStream
-
[BUG]Openhelp wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
NVIDIA/DeepStream#71 · 1 comment ·
All issues in NVIDIA/DeepStream
Similar issues
-
[request] vsg/1.1.16Openupstream update
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
conan-io/conan-center-index#31142 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
LaneDibello/Kotor-Patch-Manager#328 ·
Maintainers usually reply within 1 day