agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/IsaacTeleop/.claude/skills/cmake-structure/SKILL.md

cmake-structure

Skill438 starsChanged 31 days agoApache-2.0View on GitHub

Isaac Capture CMake target layout and #include conventions. Use whenever you create or edit a CMakeLists.txt, add or move a module/library/executable/test target, set up target_include_directories or target_link_libraries, decide where a header file goes (private vs public inc/), write or reorder #include directives in C/C++ sources, or restructure directories under src/ or deps/. Also use when reviewing diffs that touch CMakeLists.txt, header placement, include paths, or the overall project/directory structure.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Read that file and apply it before changing CMake files, header placement, or include paths — for both authoring and review.

    line 24

≈ “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
<!-- SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Isaac Capture CMake & include structure

The rules, recommended structure, repo conventions, and review checklist live in the repo's single source of truth: cmake/cmake-structure.md.

Read that file and apply it before changing CMake files, header placement, or include paths — for both authoring and review.

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