agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/simready-foundation/.agents/skills/simready-foundation-update-capability/SKILL.md

simready-foundation-update-capability

Skill156 starsChanged 52 days agoApache-2.0View on GitHub

Use for updating SimReady capability docs, requirement indexes, validation registration, and feature references.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to maintain an existing capability folder.

    line 17
  2. Very specific:

    Use simready-foundation-add-capability when the capability folder does not exist.

    line 19
  3. Distinctive:

    Use this checklist when changing the repository:

    line 46
  4. Very specific:

    Update capability-<slug>.md when scope, requirement list, related docs, or validation status changes.

    line 50
  5. Very specific:

    Update requirements.md to include every requirement doc exactly once.

    line 51
  6. Very specific:

    Add or move requirement docs with simready-foundation-add-requirement or simready-foundation-update-requirement guidance.

    line 52
  7. Very specific:

    Update validation.py and capabilities/__init__.py only when executable validators or imports change.

    line 53
  8. Distinctive:

    If requirement semantics changed, hand off to feature/profile update skills.

    line 54
  9. Distinctive:

    every requirement doc is indexed

    line 56
  10. Distinctive:

    every indexed requirement file exists

    line 57
  11. Distinctive:

    Avoid broad reorganization unless it removes real confusion.

    line 79
  12. Distinctive:

    Keep capability scope broad enough for related requirements but narrow enough to be meaningful.

    line 81
  13. Distinctive:

    Do not silently change published contracts.

    line 86
  14. Distinctive:

    Do not update docs without checking validator, manifest, profile, adapter, and runtime-test impact.

    line 87
  15. Distinctive:

    Do not broaden a change beyond the selected requirement, capability, feature, profile, validator, or adapter.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SimReady Update Capability

Purpose

Use this skill to maintain an existing capability folder. This includes adding requirement entries, clarifying the capability overview, reorganizing requirement docs, and keeping validators and imports aligned.

Use simready-foundation-add-capability when the capability folder does not exist.

Prerequisites

Before editing, read:

  • AGENTS.md
  • nv_core/sr_specs/docs/guides/naming_conventions.md
  • target capability-*.md
  • target requirements.md
  • target requirements/*.md
  • target validation.py
  • feature manifests that reference requirements in this capability

Inputs

Collect or infer:

InputRequirement
capability_pathExisting capability folder.
change_typeAdd requirement, reorganize docs, update scope, validator registration, or cleanup.
requirement_changesRequirement docs being added, moved, or updated.
validator_changesValidation module updates needed.
feature_impactFeatures affected by requirement changes.

Instructions

Use this checklist when changing the repository:

  1. Confirm the capability folder and overview/index files exist.
  2. Classify the change as documentation-only, requirement-index, validator, or contract-impacting.
  3. Update capability-<slug>.md when scope, requirement list, related docs, or validation status changes.
  4. Update requirements.md to include every requirement doc exactly once.
  5. Add or move requirement docs with simready-foundation-add-requirement or simready-foundation-update-requirement guidance.
  6. Update validation.py and capabilities/__init__.py only when executable validators or imports change.
  7. If requirement semantics changed, hand off to feature/profile update skills.
  8. Validate consistency:
    • every requirement doc is indexed
    • every indexed requirement file exists
    • validator registrations reference documented requirement IDs
    • features do not reference removed or renamed requirement IDs

Examples

Example request:

Update an existing SimReady Foundation capability to clarify its requirements and validation coverage.

Expected result summary:

changed_files: updated docs, manifests, indexes, validators, or adapters
validation: focused checks for the changed contract
remaining_gaps: downstream feature, profile, adapter, or runtime-test follow-up

Policies

  • Avoid broad reorganization unless it removes real confusion.
  • Preserve existing requirement codes and links whenever possible.
  • Keep capability scope broad enough for related requirements but narrow enough to be meaningful.
  • Record validation gaps honestly instead of implying coverage that does not exist.

Limitations

  • Do not silently change published contracts; add versions when behavior changes.
  • Do not update docs without checking validator, manifest, profile, adapter, and runtime-test impact.
  • Do not broaden a change beyond the selected requirement, capability, feature, profile, validator, or adapter.

Troubleshooting

  • Error: the requested change alters a published contract. Solution: create a new version and preserve the old artifact.
  • Error: docs and machine-readable manifests diverge. Solution: make the JSON/TOML and markdown agree, then rerun focused checks.
  • Error: downstream profile or adapter impact is unclear. Solution: list the affected artifacts before making broad edits.

Resources

  • assets/openai.yaml preserves optional UI metadata for clients that read skill display hints. It is not required for the workflow.

Summary Format

Report:

FieldMeaning
capability_pathCapability changed.
docs_changedOverview/index/requirement docs changed.
validators_changedValidation files changed.
requirements_addedNew requirement IDs.
requirements_movedMoved docs or none.
feature_followupFeature version impacts.
validationChecks run and remaining gaps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free