chore(skills): refresh stale Relay signatures#469
Conversation
github-actions
Bot
added
size:XS
|
/nvskills-ci |
WalkthroughRefreshes get-started and observability skill metadata, benchmark reports, documentation formatting, and signed DSSE bundle payloads. Evaluation results now report unavailable datasets or signals as ChangesSkill refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
coderabbitai
Bot
added
the
DO NOT MERGE
github-actions
Bot
added
size:S
|
/nvskills-ci |
coderabbitai
Bot
removed
the
DO NOT MERGE
|
@exactlyallan could this target |
|
/nvskills-ci |
Remove the two signature bundles that no longer match their skill content so NVSkills CI can regenerate content-aligned signatures without changing the underlying skills. Signed-off-by: Allan Enemark <aenemark@nvidia.com>
Reflow existing Markdown without changing rendered instructions so NVSkills CI detects both affected skills and can regenerate their stale signature bundles. Signed-off-by: Allan Enemark <aenemark@nvidia.com>
Signed-off-by: nvskills-svc-account <svc-nvskills-signing@nvidia.com>
a5b5020 to
5c3a8b5
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/nemo-relay-get-started/BENCHMARK.md`:
- Around line 32-46: The benchmark report’s overall PASS and publication
recommendation must not imply successful evaluation when dataset and Tier 3
results are unavailable. Update the verdict and recommendation sections
associated with the report to mark the benchmark incomplete/unscored, or
explicitly scope PASS to Tier 1 static validation only, while preserving the
documented N/A results.
In `@skills/nemo-relay-get-started/skill-card.md`:
- Around line 68-69: Add a blank line immediately after the “Skill Version(s)”
heading in the skill card, before the version value, so the heading is
surrounded by blank lines and satisfies markdownlint.
In `@skills/nemo-relay-plugin-observability/BENCHMARK.md`:
- Around line 32-46: Update the Overall verdict and publication recommendation
in BENCHMARK.md to reflect that the evaluation dataset and Tier 3 signals were
unavailable. Do not report an overall PASS; scope the verdict to completed
validations or mark the evaluation as incomplete/not evaluated.
In `@skills/nemo-relay-plugin-observability/skill-card.md`:
- Around line 40-42: Update the “Evaluation Agents Used” section in
skill-card.md by adding a blank line after the heading and formatting the agent
names `claude-code` and `codex` as inline code elements.
- Around line 34-35: Insert a blank line immediately after the headings “##
Skill Output: <br>” and “## Skill Version(s): <br>” in the skill card,
preserving the existing content and formatting otherwise.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Enterprise
Run ID: 409b8863-4e50-48e9-a1fb-8e41e1d13ba2
📒 Files selected for processing (8)
skills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/skill-card.mdskills/nemo-relay-get-started/skill.oms.sigskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-plugin-observability/skill.oms.sig
📜 Review details
🧰 Additional context used
📓 Path-based instructions (9)
**/*.{md,rst,html,txt}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)
**/*.{md,rst,html,txt}: Always spellNVIDIAin all caps. Do not useNvidia,nvidia,nVidia,nVIDIA, orNV.
Usean NVIDIAbefore a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol afterNVIDIAwhen referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names withNVIDIAon first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms withs, not an apostrophe, such asGPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such asCPU,GPU,PC,API, andUIusually do not need to be spelled out for developer audiences.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*.{md,rst,html}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)
Link the first mention of a product name when the destination helps the reader.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*.{md,rst,txt}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)
Spell
NVIDIAin all caps. Do not useNvidia,nvidia, orNV.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*.{md,rst}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)
**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Usecanfor possibility and reservemayfor permission.
Useafterfor temporal relationships instead ofonce.
Preferrefer tooverseewhen the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*.md
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)
**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as/home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring[NVIDIA/NeMo](link)over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/SKILL.md
📄 CodeRabbit inference engine (AGENTS.md)
SKILL.mdfiles are skill entrypoints and must start with YAML frontmatter containing at leastnameanddescription.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.md
⚙️ CodeRabbit configuration file
**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.md
**/*.{md,mdx}
📄 CodeRabbit inference engine (AGENTS.md)
Update
README.md,fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.
**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such asRELEASING.md, not as user-facing docs pages orCHANGELOG.md
Keep stable user-facing wrappers atscripts/root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, andgrpc-v1protocol details on separate pagesIf links in documentation change, run
just docs-linkcheck.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*.{md,markdown,mdx}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-get-started/skill-card.md
**/*
📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, usemaintain-dynamic-pluginsand include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, preferuv run pre-commit run --files <changed files...>.
Before review or handoff, runuv run pre-commit run --all-files.
Files:
skills/nemo-relay-plugin-observability/SKILL.mdskills/nemo-relay-get-started/SKILL.mdskills/nemo-relay-get-started/BENCHMARK.mdskills/nemo-relay-plugin-observability/BENCHMARK.mdskills/nemo-relay-plugin-observability/skill-card.mdskills/nemo-relay-plugin-observability/skill.oms.sigskills/nemo-relay-get-started/skill.oms.sigskills/nemo-relay-get-started/skill-card.md
🪛 markdownlint-cli2 (0.23.0)
skills/nemo-relay-plugin-observability/skill-card.md
[warning] 34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 65-65: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
skills/nemo-relay-get-started/skill-card.md
[warning] 68-68: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🪛 SkillSpector (2.3.11)
skills/nemo-relay-get-started/SKILL.md
[warning] 33: [EA2] Autonomous Decision Making: Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Remediation: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
(Excessive Agency (EA2))
🔇 Additional comments (7)
skills/nemo-relay-get-started/skill-card.md (1)
12-12: LGTM!Also applies to: 38-38, 48-49, 57-67
skills/nemo-relay-get-started/SKILL.md (1)
93-95: 📐 Maintainability & Code QualityNo frontmatter change needed.
skills/nemo-relay-get-started/SKILL.mdstill has valid YAML frontmatter with bothnameanddescription.> Likely an incorrect or invalid review comment.skills/nemo-relay-get-started/skill.oms.sig (1)
1-1: 🔒 Security & PrivacyNo bundle drift to flag.
> Likely an incorrect or invalid review comment.skills/nemo-relay-plugin-observability/skill-card.md (1)
12-12: LGTM!Also applies to: 28-31, 35-38, 54-63
skills/nemo-relay-plugin-observability/BENCHMARK.md (1)
10-12: LGTM!skills/nemo-relay-plugin-observability/SKILL.md (1)
57-58: 📐 Maintainability & Code QualityNo action needed.
skills/nemo-relay-plugin-observability/SKILL.mdalready starts with valid YAML frontmatter and non-emptynameanddescriptionfields.> Likely an incorrect or invalid review comment.skills/nemo-relay-plugin-observability/skill.oms.sig (1)
1-1: 🔒 Security & PrivacyValidate the DSSE bundle in a checkout that contains all referenced files The current checkout is missing at least one referenced resource (
BENCHMARK.md), so the inline digest check cannot run as written. Keep the NVSkills validation-signature bot gate for the certificate chain and DSSE signature.
| - No Tier 3 evaluation signal details were available in this report. | ||
|
|
||
| ## Test Tasks | ||
|
|
||
| The benchmark dataset contained 15 evaluation tasks: | ||
|
|
||
| - Positive tasks: 14 tasks where the skill was expected to activate. | ||
| - Negative tasks: 1 tasks where no skill was expected. | ||
| - Unlabeled tasks: 0 tasks where positive/negative intent could not be inferred. | ||
|
|
||
| Task composition is derived from the evaluation dataset when possible. Entries with `expected_skill` set are treated as positive skill-activation cases, while entries with `expected_skill: null` are treated as negative activation cases. | ||
| The evaluation dataset was not available in this report payload. | ||
|
|
||
| ## Results | ||
|
|
||
| | Dimension | Num | `claude-code` | `codex` | | ||
| |---|---:|---:|---:| | ||
| | Security | 8 | 97% (+0%) | 97% (+10%) | | ||
| | Correctness | 8 | 89% (+61%) | 76% (+38%) | | ||
| | Discoverability | 8 | 82% (+50%) | 74% (+35%) | | ||
| | Effectiveness | 8 | 74% (+50%) | 65% (+32%) | | ||
| | Efficiency | 8 | 72% (+34%) | 68% (+29%) | | ||
| | Security | N/A | N/A | N/A | | ||
| | Correctness | N/A | N/A | N/A | | ||
| | Discoverability | N/A | N/A | N/A | | ||
| | Effectiveness | N/A | N/A | N/A | | ||
| | Efficiency | N/A | N/A | N/A | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Do not report an overall benchmark pass when evaluation data is unavailable.
This block now states that the dataset and Tier 3 signals are unavailable and every result is N/A, but the report still claims Overall verdict: PASS and recommends publication in Lines 13 and 64-66. Qualify the result as incomplete/unscored, or explicitly limit the pass to Tier 1 static validation so missing evaluation data cannot be interpreted as successful benchmark evidence.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemo-relay-get-started/BENCHMARK.md` around lines 32 - 46, The
benchmark report’s overall PASS and publication recommendation must not imply
successful evaluation when dataset and Tier 3 results are unavailable. Update
the verdict and recommendation sections associated with the report to mark the
benchmark incomplete/unscored, or explicitly scope PASS to Tier 1 static
validation only, while preserving the documented N/A results.
| ## Skill Version(s): <br> | ||
| 0.6.0-alpha.20260715 (source: git tag) <br> | ||
| 0.7.0-alpha.20260717 (source: git tag) <br> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add a blank line after the heading.
markdownlint reports that ## Skill Version(s) is not surrounded by blank lines. Add an empty line before the version value.
Proposed fix
## Skill Version(s): <br>
+
0.7.0-alpha.20260717 (source: git tag) <br>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## Skill Version(s): <br> | |
| 0.6.0-alpha.20260715 (source: git tag) <br> | |
| 0.7.0-alpha.20260717 (source: git tag) <br> | |
| ## Skill Version(s): <br> | |
| 0.7.0-alpha.20260717 (source: git tag) <br> |
🧰 Tools
🪛 markdownlint-cli2 (0.23.0)
[warning] 68-68: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemo-relay-get-started/skill-card.md` around lines 68 - 69, Add a
blank line immediately after the “Skill Version(s)” heading in the skill card,
before the version value, so the heading is surrounded by blank lines and
satisfies markdownlint.
Source: Linters/SAST tools
| - No Tier 3 evaluation signal details were available in this report. | ||
|
|
||
| ## Test Tasks | ||
|
|
||
| The benchmark dataset contained 20 evaluation tasks: | ||
|
|
||
| - Positive tasks: 16 tasks where the skill was expected to activate. | ||
| - Negative tasks: 4 tasks where no skill was expected. | ||
| - Unlabeled tasks: 0 tasks where positive/negative intent could not be inferred. | ||
|
|
||
| Task composition is derived from the evaluation dataset when possible. Entries with `expected_skill` set are treated as positive skill-activation cases, while entries with `expected_skill: null` are treated as negative activation cases. | ||
| The evaluation dataset was not available in this report payload. | ||
|
|
||
| ## Results | ||
|
|
||
| | Dimension | Num | `claude-code` | `codex` | | ||
| |---|---:|---:|---:| | ||
| | Security | 8 | 100% (+0%) | 100% (+0%) | | ||
| | Correctness | 8 | 98% (+53%) | 93% (+31%) | | ||
| | Discoverability | 8 | 99% (+67%) | 85% (+42%) | | ||
| | Effectiveness | 8 | 91% (+47%) | 87% (+30%) | | ||
| | Efficiency | 8 | 92% (+51%) | 82% (+35%) | | ||
| | Security | N/A | N/A | N/A | | ||
| | Correctness | N/A | N/A | N/A | | ||
| | Discoverability | N/A | N/A | N/A | | ||
| | Effectiveness | N/A | N/A | N/A | | ||
| | Efficiency | N/A | N/A | N/A | |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Do not report an overall PASS without evaluation evidence.
This section explicitly says the dataset and Tier 3 signals were unavailable, yet the report retains Overall verdict: PASS and a publication recommendation. Scope PASS to the validations actually completed, or mark the evaluation as incomplete/not evaluated.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemo-relay-plugin-observability/BENCHMARK.md` around lines 32 - 46,
Update the Overall verdict and publication recommendation in BENCHMARK.md to
reflect that the evaluation dataset and Tier 3 signals were unavailable. Do not
report an overall PASS; scope the verdict to completed validations or mark the
evaluation as incomplete/not evaluated.
| ## Skill Output: <br> | ||
| **Output Type(s):** [Configuration instructions, Code, Analysis] <br> | ||
| **Output Type(s):** [Configuration instructions, Code] <br> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add blank lines after the headings.
Insert a blank line after ## Skill Output: <br> and ## Skill Version(s): <br> to satisfy Markdown heading-spacing rules.
Also applies to: 65-66
🧰 Tools
🪛 markdownlint-cli2 (0.23.0)
[warning] 34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemo-relay-plugin-observability/skill-card.md` around lines 34 - 35,
Insert a blank line immediately after the headings “## Skill Output: <br>” and
“## Skill Version(s): <br>” in the skill card, preserving the existing content
and formatting otherwise.
Source: Linters/SAST tools
| ## Evaluation Agents Used: <br> | ||
| - `claude-code` <br> | ||
| - `codex` <br> | ||
| - claude-code <br> | ||
| - codex <br> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Keep agent names in inline code and separate the heading with a blank line.
Format claude-code and codex as code elements, and add a blank line after the heading. As per coding guidelines, format code elements in monospace.
🧰 Tools
🪛 markdownlint-cli2 (0.23.0)
[warning] 40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemo-relay-plugin-observability/skill-card.md` around lines 40 - 42,
Update the “Evaluation Agents Used” section in skill-card.md by adding a blank
line after the heading and formatting the agent names `claude-code` and `codex`
as inline code elements.
Sources: Coding guidelines, Linters/SAST tools
|
Waiting for CI fixes to enable benchmark data. |
3 participants
Overview
Refresh two stale NeMo Relay skill signatures that are currently blocking publication through the NVIDIA skills catalog sync.
Details
skill.oms.sigbundle fromnemo-relay-get-started.skill.oms.sigbundle fromnemo-relay-plugin-observability.SKILL.mdwithout changing renderedinstructions, ensuring NVCARPS includes both skills in its signing input set.
/nvskills-ciso the signing bot regenerates content-aligned bundles and validation artifacts.Do not merge until the
Attach NVSkills validation signaturesbot commit lands and both affected skills pass content-integrity verification.Where should the reviewer start?
Start with the two deleted signature bundles and the rendered-content-neutral Markdown reflows. NVSkills CI should restore each bundle with digests matching the current skill content.
Validation before opening:
NVIDIA/NeMo-Relay/main.nemo-relay-get-started.nemo-relay-plugin-observability.SKILL.mdfiles.git diff --checkRelated Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit
Chores / Security
Documentation
N/A) and updated version indicators.