agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/TensorRT-Model-Connect/plugins/trtmc-agent-skills/skills/doc-sync/SKILL.md

doc-sync

Skill290 starsChanged 45 days agoApache-2.0View on GitHub

Audit and update TensorRT-Model-Connect documentation when code, public APIs, family ownership, commands, or model support have changed.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-endpoint, perf-budget and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tadoEngSkill

    api-endpoint

    Add or change a backend API endpoint on this product, keeping Pydantic as the single contract authority and regenerating the TypeScript client. Use when asked to add an endpoint, expose data to the frontend, change a request or response shape, or wire a new backend capability into a page.

    Also in 4 projects that use this

  • vindreshsinghSkill

    perf-budget

    Optimizes performance by measuring first and fixing the real bottleneck. Use when something is slow, before optimizing, when setting latency or bundle targets, or reviewing changes for performance traps — not for speculative micro-tuning.

    Also in 3 projects that use this

  • AnasX7Skill

    improve

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat implementation, tests, executable help, and family manifests as the source of truth.

    line 10
  2. Distinctive:

    Verify every changed path, symbol, option, and command locally when practical.

    line 25
  3. Distinctive:

    If hardware or dependencies prevent execution, inspect the consuming code and state that boundary explicitly.

    line 26
  4. Distinctive:

    Keep one canonical explanation and link to it instead of copying large policy sections.

    line 30
  5. Distinctive:

    Run additional focused tests for any documented command or API that changed.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “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

Synchronize Documentation

Treat implementation, tests, executable help, and family manifests as the source of truth. Update only documentation affected by the requested change.

Route the change

  • Public build behavior: check core/builder/ and the Python API docs.
  • Native user behavior: check core/runtime/include/trtmc/, CLI parsing, and the C++ API docs.
  • Model behavior: check only the owning families/<family>/ implementation, manifests, thresholds, and model recipe.
  • Developer workflow: check README.md, CONTRIBUTING.md, and the relevant page under website/docs/.
  • Benchmark behavior: check apps/benchmark/ and its performance README.
  • Repo-local skills: check plugins/trtmc-agent-skills/skills/.

Verify every changed path, symbol, option, and command locally when practical. If hardware or dependencies prevent execution, inspect the consuming code and state that boundary explicitly. Do not turn source presence into a runtime, parity, performance, or qualification claim.

Keep one canonical explanation and link to it instead of copying large policy sections. Remove stale links and generated counts rather than replacing them with unverified values.

Validate

git diff --check
PYTHONPATH=core/builder:apps/benchmark:. python3 -m tools.model_ci validate
npm --prefix website run test:model-support
npm --prefix website run build

Run additional focused tests for any documented command or API that changed. Summarize corrected claims, validation actually run, and remaining evidence boundaries. Publish or open a pull request only when the user requested it.

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.

Reviews can't be read right now.

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