Agent skills hide information in unspecified field
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #1006 by @janEbert — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
Research direction
Start by locating the agent skill files that use argument-hint and compare their frontmatter with the official Agent Skills specification linked in the issue. Remove that field and express each invocation in the description using natural language and quoted literal values. Done when the skill instructions follow the requested format; the linked pull request may show the intended changes.
Written by the indexing model from the issue text.
Description
Priority Level
Low (Cosmetic / Minor)
Describe the bug
The agent skills in the repo are using a field called argument-hint to specify usage instructions. This is not part of the official agent skill specification and thus won't transfer as well to all harnesses.
Steps/Code to reproduce bug
Refer to the official agent skills specification:
Expected behavior
It would be desirable to keep divergence from the Agent Skills spec to a minimum, so that degradation between harnesses is minimized.
How to fix (PR here):
- Remove
argument-hintand describe the invocation indescriptionin natural language, with literal values quoted.
Agent Diagnostic / Prior Investigation
No response
Additional context
How to fix (PR here):
- Remove
argument-hintand describe the invocation indescriptionin natural language, with literal values quoted.
Checklist
- I reproduced this issue or provided a minimal example
- I searched the docs/issues myself, or had my agent do so
- If I used an agent, I included its diagnostics above
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 227
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from NVIDIA-NeMo/DataDesigner
-
docs: required_columns description is incomplete for LLM and multimodal columnsMay be free again @nightcityblade claimed this 7 days ago, and no pull request is open. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NVIDIA-NeMo/DataDesigner#1002 · 3 comments ·
Maintainers usually reply within 1 day
-
enforce \from future import annotations` via ruff FA102 rule`Possibly taken @chethanuk claimed this 35 days ago. Opentask
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA-NeMo/DataDesigner#760 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
NVIDIA-NeMo/DataDesigner#1033 ·
Maintainers usually reply within 1 day
-
bug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
NVIDIA-NeMo/DataDesigner#1017 · 1 comment ·
Maintainers usually reply within 1 day
-
Numeric sampler rounding can violate constraints and invalidate conditional samplingPossibly taken @Avaivartika claimed this 2 days ago. Openbug triaged
Difficulty 4/5 3-5 days Newbie friendliness 63/100
NVIDIA-NeMo/DataDesigner#1001 · 3 comments ·
Maintainers usually reply within 1 day
All issues in NVIDIA-NeMo/DataDesigner
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws-samples/sample-per-model-bedrock#261 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
pwncollege/dojo#1188 ·
Maintainers usually reply within 1 day
-
bug launcher packaging
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tenstorrent/tt-studio#1426 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-attrs/cattrs#796 ·
Maintainers usually reply within 1 day