Skill Tracer
Skills › Scientific Agent Skills › get-available-resources

get-available-resources

skill · 296 lines · MIT · skills/get-available-resources/SKILL.md

The facts

Its description

Detects host inventory and effective CPU, memory, disk, scheduler, container, and accelerator limits when a user asks for resource-aware planning or before a clearly resource-sensitive local workload. Produces a redacted JSON snapshot and conservative planning helpers without stress tests or assuming visible host hardware is usable.

The description the agent reads to decide when to use it.

From its settingsline 3

Runs scripts

python scripts/detect_resources.py, python scripts/plan_workload.py (first 5 of 12 lines)

Scripts the text names. Found by matching words, so treat them as pointers.

Found by matching wordsline 46 line 55 line 71 line 80 line 173

Files it mentions

references/resource_semantics.md, references/snapshot_schema.md, scripts/detect_resources.py, scripts/plan_workload.py, scripts/snapshot_tools.py (first 5 of 10 lines)

Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.

Found by matching wordsline 165 line 219 line 266 line 267 line 268

Licence

MIT, from the skill file

The terms its author shares it under, which let it be shown here.

From its settingsline 4 licence text

Other settings

compatibility: Python 3.11+ on Linux, macOS, or Windows; standard library by default, optional psutil 7.2.2; accelerator management CLIs are optional read-only probes. metadata: version: "1.5" last-reviewed: "2026-10-01" skill-author: K-Dense Inc.

More settings at the top of the file, shown as written.

From its settingsline 5 line 6
Other files in this skill (8) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: get-available-resources
3description: Detects host inventory and effective CPU, memory, disk, scheduler, container, and accelerator limits when a user asks for resource-aware planning or before a clearly resource-sensitive local workload. Produces a redacted JSON snapshot and conservative planning helpers without stress tests or assuming visible host hardware is usable.
4license: MIT
5compatibility: Python 3.11+ on Linux, macOS, or Windows; standard library by default, optional psutil 7.2.2; accelerator management CLIs are optional read-only probes.
6metadata:
7 version: "1.5"
8 last-reviewed: "2026-10-01"
9 skill-author: K-Dense Inc.
10---
12# Get Available Resources
14Build a conservative picture of resources available to the **current process**.
15Keep host inventory, process affinity, cgroup/container limits, scheduler
16allocation, and accelerator runtime usability separate.

Get Available Resources

Build a conservative picture of resources available to the current process. Keep host inventory, process affinity, cgroup/container limits, scheduler allocation, and accelerator runtime usability separate.

Raw lines 1 to 17
18## Safety contract
20Follow these rules:
22- Run detection when the user requests it or a specific workload needs resource
23 planning. Do not persist a fingerprint for every scientific task.
24- Use stdout by default. Persist only when the user chooses an explicit generic
25 local filename.
26- Do not run stress tests, benchmarks, large allocations, write probes, device
27 resets, driver installation, or clock/power changes.
28- Do not dump the environment. Read only the named Slurm and accelerator
29 variables implemented by the detector.
30- Do not report hostnames, absolute paths, cgroup paths, job IDs, device UUIDs,
31 PCI addresses, or raw visibility-variable values.
32- Treat a missing observation as unknown. Never convert unknown to unlimited.
33- Never infer that a visible host CPU, memory pool, or GPU is usable inside a
34 scheduler allocation or container.
36The bundled detector uses only fixed executable/argument tuples, no shell,
37short timeouts, bounded stdout/stderr, and partial-failure warnings.

Safety contract

Follow these rules:

  • Run detection when the user requests it or a specific workload needs resource planning. Do not persist a fingerprint for every scientific task.
  • Use stdout by default. Persist only when the user chooses an explicit generic local filename.
  • Do not run stress tests, benchmarks, large allocations, write probes, device resets, driver installation, or clock/power changes.
  • Do not dump the environment. Read only the named Slurm and accelerator variables implemented by the detector.
  • Do not report hostnames, absolute paths, cgroup paths, job IDs, device UUIDs, PCI addresses, or raw visibility-variable values.
  • Treat a missing observation as unknown. Never convert unknown to unlimited.
  • Never infer that a visible host CPU, memory pool, or GPU is usable inside a scheduler allocation or container.

The bundled detector uses only fixed executable/argument tuples, no shell, short timeouts, bounded stdout/stderr, and partial-failure warnings.

Raw lines 18 to 38
39## Quick start
41Run from this skill directory.

Quick start

Run from this skill directory.

Raw lines 39 to 42
43### Ephemeral stdout snapshot
45```bash
46python scripts/detect_resources.py
47```
49The command emits only JSON to stdout. Redirect it only when ordinary shell
50permissions are acceptable.

Ephemeral stdout snapshot

python scripts/detect_resources.py

The command emits only JSON to stdout. Redirect it only when ordinary shell permissions are acceptable.

Raw lines 43 to 51
Runs code python scripts/detect_resources.py :46
52### Explicit private file
54```bash
55python scripts/detect_resources.py --output resource-snapshot.json
56```
58Explicit output is restricted to one `.json` filename in the current
59directory, uses mode 0600 on POSIX, rejects symlinks and path traversal, and
60refuses overwrite unless `--force` is supplied. Forced output also rejects
61hard links and non-regular files. Windows privacy additionally depends on the
62directory ACL.

Explicit private file

python scripts/detect_resources.py --output resource-snapshot.json

Explicit output is restricted to one .json filename in the current directory, uses mode 0600 on POSIX, rejects symlinks and path traversal, and refuses overwrite unless --force is supplied. Forced output also rejects hard links and non-regular files. Windows privacy additionally depends on the directory ACL.

Raw lines 52 to 63
Runs code python scripts/detect_resources.py :55
64### Optional psutil enhancement
66The standard-library detector works without installation. For broader
67cross-platform physical-core, affinity, available-memory, swap, and disk
68coverage:
70```bash
71uv run --no-project --with "psutil==7.2.2" python scripts/detect_resources.py
72```
74The import is lazy. Failure to import psutil becomes a warning, not a fatal
75error.

Optional psutil enhancement

The standard-library detector works without installation. For broader cross-platform physical-core, affinity, available-memory, swap, and disk coverage:

uv run --no-project --with "psutil==7.2.2" python scripts/detect_resources.py

The import is lazy. Failure to import psutil becomes a warning, not a fatal error.

Raw lines 64 to 76
Runs code python scripts/detect_resources.py :71
77### Skip management-tool probes
79```bash
80python scripts/detect_resources.py --skip-accelerators
81```
83Use this when accelerator discovery latency is undesirable. The detector still
84summarizes the presence and state of allowlisted visibility variables without
85returning their values.

Skip management-tool probes

python scripts/detect_resources.py --skip-accelerators

Use this when accelerator discovery latency is undesirable. The detector still summarizes the presence and state of allowlisted visibility variables without returning their values.

Raw lines 77 to 86
Runs code python scripts/detect_resources.py :80
87## Required interpretation

Required interpretation

Raw lines 87 to 88
89### CPU
91Read these as different facts:
93- `cpu.host.logical`: system-visible scheduling units.
94- `cpu.host.physical`: physical topology, or null; never inferred from logical
95 count.
96- `cpu.process.affinity_logical`: current affinity-set size when supported.
97- `cpu.cgroup_v2.cpuset_logical`: effective cgroup cpuset size.
98- `cpu.cgroup_v2.quota_cores`: finite `cpu.max` capacity, possibly fractional.
99- `scheduler.allocation.cpu_per_process`: bounded Slurm per-task
100 interpretation when scope is clear.
101- `cpu.effective.capacity_cores`: minimum positive observed constraint.
102- `cpu.effective.worker_ceiling`: conservative floor for CPU process workers.
104A quota of 1.5 is CPU-time capacity, not 1.5 physical cores. Affinity and
105cpusets constrain placement; quota constrains bandwidth.

CPU

Read these as different facts:

  • cpu.host.logical: system-visible scheduling units.
  • cpu.host.physical: physical topology, or null; never inferred from logical count.
  • cpu.process.affinity_logical: current affinity-set size when supported.
  • cpu.cgroup_v2.cpuset_logical: effective cgroup cpuset size.
  • cpu.cgroup_v2.quota_cores: finite cpu.max capacity, possibly fractional.
  • scheduler.allocation.cpu_per_process: bounded Slurm per-task interpretation when scope is clear.
  • cpu.effective.capacity_cores: minimum positive observed constraint.
  • cpu.effective.worker_ceiling: conservative floor for CPU process workers.

A quota of 1.5 is CPU-time capacity, not 1.5 physical cores. Affinity and cpusets constrain placement; quota constrains bandwidth.

Raw lines 89 to 106
107### Memory
109Keep these separate:
111- host total/available memory;
112- current cgroup usage, hard `memory.max`, and remaining hierarchical capacity;
113- `memory.high`, which is a pressure/throttle boundary rather than a hard cap;
114- scheduler memory allocation and its scope; and
115- conservative effective hard limit and available estimate.
117On Apple silicon, `memory.model` is `unified_cpu_gpu`. Do not add integrated GPU
118memory to RAM or describe it as separate VRAM.

Memory

Keep these separate:

  • host total/available memory;
  • current cgroup usage, hard memory.max, and remaining hierarchical capacity;
  • memory.high, which is a pressure/throttle boundary rather than a hard cap;
  • scheduler memory allocation and its scope; and
  • conservative effective hard limit and available estimate.

On Apple silicon, memory.model is unified_cpu_gpu. Do not add integrated GPU memory to RAM or describe it as separate VRAM.

Raw lines 107 to 119
120### Accelerators
122Each device is a backend **candidate**:
124- NVIDIA GPU → CUDA candidate;
125- AMD GPU → ROCm candidate;
126- Apple integrated GPU → Metal candidate.
128Management-query visibility does not establish:
1301. scheduler/container permission;
1312. device-node access;
1323. driver/runtime compatibility;
1334. framework package compatibility; or
1345. operator/data-type support.
136Therefore `runtime_usable_devices` remains null and each device says
137`runtime_compatibility: not_tested`. Visibility/allocation counts constrain
138the observed management records, not the number of framework devices. MIG and AMD partition enumeration can differ.
139AMD `reported_total_bytes` is a device-reported memory pool; its relationship
140to host RAM is not established, so it is never added to the RAM budget.

Accelerators

Each device is a backend candidate:

  • NVIDIA GPU → CUDA candidate;
  • AMD GPU → ROCm candidate;
  • Apple integrated GPU → Metal candidate.

Management-query visibility does not establish:

  1. scheduler/container permission;
  2. device-node access;
  3. driver/runtime compatibility;
  4. framework package compatibility; or
  5. operator/data-type support.

Therefore runtime_usable_devices remains null and each device says runtime_compatibility: not_tested. Visibility/allocation counts constrain the observed management records, not the number of framework devices. MIG and AMD partition enumeration can differ. AMD reported_total_bytes is a device-reported memory pool; its relationship to host RAM is not established, so it is never added to the RAM budget.

Raw lines 120 to 141
142### Disk
144`capacity_bytes`, filesystem `free_bytes`, user-available blocks, and a
145non-writing permission check are distinct. Filesystem or project quotas can
146still be stricter. The absolute working path is always redacted.
148The disk snapshot covers the working filesystem only, matching
149[psutil's path-specific semantics](https://psutil.readthedocs.io/stable/index.html#psutil.disk_usage).
150If scratch, caches, and final outputs use different filesystems, inspect each
151from its target directory and label the reports by role. Budget temporary and
152final copies that coexist; free space on the input filesystem does not establish
153space on the output filesystem.

Disk

capacity_bytes, filesystem free_bytes, user-available blocks, and a non-writing permission check are distinct. Filesystem or project quotas can still be stricter. The absolute working path is always redacted.

The disk snapshot covers the working filesystem only, matching psutil's path-specific semantics. If scratch, caches, and final outputs use different filesystems, inspect each from its target directory and label the reports by role. Budget temporary and final copies that coexist; free space on the input filesystem does not establish space on the output filesystem.

Raw lines 142 to 154
155### Scheduler and container
157Slurm variables describe allocation scope, but enforcement depends on site
158configuration such as task affinity or cgroups. Prefer affinity and cgroup
159observations as enforcement evidence.
161Container markers identify context; cgroup controls identify limits. A
162container with no finite cgroup value can still see host inventory, and a
163non-root cgroup is not automatically labeled a container.
166the detailed platform rules.

Scheduler and container

Slurm variables describe allocation scope, but enforcement depends on site configuration such as task affinity or cgroups. Prefer affinity and cgroup observations as enforcement evidence.

Container markers identify context; cgroup controls identify limits. A container with no finite cgroup value can still see host inventory, and a non-root cgroup is not automatically labeled a container.

See [references/resource_semantics.md](references/resource_semantics.md) for the detailed platform rules.

Raw lines 155 to 167
168## Plan a workload
170The planner consumes a validated snapshot and performs no work:
172```bash
173python scripts/plan_workload.py resource-snapshot.json \
174 --workload cpu \
175 --tasks 100 \
176 --memory-per-worker-mib 2048
177```
179Optional controls:
181- `--workers N`: explicit upper bound.
182- `--reserve-memory-mib N`: memory kept outside the worker budget.
183- `--workload cpu|mixed|io`: selects a bounded worker heuristic.
184- `--accelerator none|any|cuda|rocm|metal`: requests a candidate backend
185 decision without claiming usability.
186- `--output plan.json`: explicit private local output; stdout is default.
188A known memory budget that cannot fit one worker returns zero workers and
189`recommendation.status: insufficient_memory`; do not launch that plan. Unknown
190CPU or available memory produces `review_required`. Positive counts are
191provisional estimates, not reservations.
193For CPU or mixed work, use `suggested_workers` and
194`threads_per_worker` together. Process workers multiplied by BLAS/OpenMP native
195threads can oversubscribe an allocation.
197The I/O plan permits bounded oversubscription (maximum 32) but labels it a
198heuristic. Benchmark only the real representative workload and stay within
199scheduler/container limits.

Plan a workload

The planner consumes a validated snapshot and performs no work:

python scripts/plan_workload.py resource-snapshot.json \
  --workload cpu \
  --tasks 100 \
  --memory-per-worker-mib 2048

Optional controls:

  • --workers N: explicit upper bound.
  • --reserve-memory-mib N: memory kept outside the worker budget.
  • --workload cpu|mixed|io: selects a bounded worker heuristic.
  • --accelerator none|any|cuda|rocm|metal: requests a candidate backend decision without claiming usability.
  • --output plan.json: explicit private local output; stdout is default.

A known memory budget that cannot fit one worker returns zero workers and recommendation.status: insufficient_memory; do not launch that plan. Unknown CPU or available memory produces review_required. Positive counts are provisional estimates, not reservations.

For CPU or mixed work, use suggested_workers and threads_per_worker together. Process workers multiplied by BLAS/OpenMP native threads can oversubscribe an allocation.

The I/O plan permits bounded oversubscription (maximum 32) but labels it a heuristic. Benchmark only the real representative workload and stay within scheduler/container limits.

Raw lines 168 to 200
Runs code python scripts/plan_workload.py :173
201## Validate or diff snapshots
203Validate:
205```bash
206python scripts/snapshot_tools.py validate resource-snapshot.json
207```
209Diff resource state while ignoring `observed_at`:
211```bash
212python scripts/snapshot_tools.py diff before.json after.json
213```
215Use `--include-volatile` to include the timestamp. Inputs must be regular,
216non-symlink JSON files no larger than 1 MiB. Diffs are bounded.
218The schema and null/zero meanings are documented in

Validate or diff snapshots

Validate:

python scripts/snapshot_tools.py validate resource-snapshot.json

Diff resource state while ignoring observed_at:

python scripts/snapshot_tools.py diff before.json after.json

Use --include-volatile to include the timestamp. Inputs must be regular, non-symlink JSON files no larger than 1 MiB. Diffs are bounded.

The schema and null/zero meanings are documented in [references/snapshot_schema.md](references/snapshot_schema.md).

Raw lines 201 to 220
Runs code python scripts/snapshot_tools.py :206
221## Optional accelerator diagnostic plan
223Generate a plan without executing any diagnostic:
225```bash
226python scripts/accelerator_diagnostics.py resource-snapshot.json \
227 --backend auto
228```
230The result contains fixed, read-only management query argument lists and
231separate gates for visibility, permission, and runtime compatibility. Run a
232framework's official availability check only in the exact environment that
233will execute the workload. Do not install or mutate drivers automatically.

Optional accelerator diagnostic plan

Generate a plan without executing any diagnostic:

python scripts/accelerator_diagnostics.py resource-snapshot.json \
  --backend auto

The result contains fixed, read-only management query argument lists and separate gates for visibility, permission, and runtime compatibility. Run a framework's official availability check only in the exact environment that will execute the workload. Do not install or mutate drivers automatically.

Raw lines 221 to 234
Runs code python scripts/accelerator_diagnostics.py :226
235## Partial failures and provenance
237One failed probe must not erase successful observations. Inspect:
239- `completeness`;
240- sorted `warnings` with stable codes;
241- sorted `provenance` source/status records; and
242- null fields.
244Subprocess stderr and raw exception text are not copied into the snapshot
245because they can contain identifiers or paths.

Partial failures and provenance

One failed probe must not erase successful observations. Inspect:

  • completeness;
  • sorted warnings with stable codes;
  • sorted provenance source/status records; and
  • null fields.

Subprocess stderr and raw exception text are not copied into the snapshot because they can contain identifiers or paths.

Raw lines 235 to 246
247## Platform notes
249- **Linux:** reads only bounded `/proc` and cgroup v2 files. Ancestor CPU and
250 memory limits visible through the cgroup2 mount are considered. Hidden
251 ancestors and cgroup v1 limits are not measured; unreadable v2 membership is
252 reported as unknown rather than substituted with the mount root.
253- **macOS:** uses fixed `sysctl` keys and a bounded
254 `system_profiler SPDisplaysDataType -json` query. Apple silicon memory is
255 unified.
256- **Windows:** optional psutil improves physical-core, affinity, available
257 memory, and swap observations. Processor-group scope can make host and
258 process counts differ.
259- **Slurm:** reads an allowlist of allocation variables. It never emits job,
260 node, submit-host, GPU-ID, or path values.
261- **NVIDIA/AMD:** management CLIs are optional. Absence is normal; timeout,
262 truncation, parse failure, and runtime uncertainty remain explicit.

Platform notes

  • Linux: reads only bounded /proc and cgroup v2 files. Ancestor CPU and memory limits visible through the cgroup2 mount are considered. Hidden ancestors and cgroup v1 limits are not measured; unreadable v2 membership is reported as unknown rather than substituted with the mount root.
  • macOS: uses fixed sysctl keys and a bounded system_profiler SPDisplaysDataType -json query. Apple silicon memory is unified.
  • Windows: optional psutil improves physical-core, affinity, available memory, and swap observations. Processor-group scope can make host and process counts differ.
  • Slurm: reads an allowlist of allocation variables. It never emits job, node, submit-host, GPU-ID, or path values.
  • NVIDIA/AMD: management CLIs are optional. Absence is normal; timeout, truncation, parse failure, and runtime uncertainty remain explicit.
Raw lines 247 to 263
264## Bundled files
266- `scripts/detect_resources.py` — redacted snapshot collector.
267- `scripts/plan_workload.py` — deterministic worker/memory planner.
268- `scripts/snapshot_tools.py` — schema validator and bounded structural diff.
269- `scripts/accelerator_diagnostics.py` — non-executing read-only diagnostic
270 plan.
271- `tests/get-available-resources/` in the repository root — network-free
272 Linux, macOS, Windows, cgroup, Slurm, and accelerator cases.
273- `references/resource_semantics.md` — interpretation and platform details.
274- `references/snapshot_schema.md` — schema 1.1 contract.
275- `references/sources.md` — dated official-source ledger.
277Official documentation and source were refreshed on **2026-10-01**; consult
278[`references/sources.md`](references/sources.md) before changing semantics or
279dependency pins.

Bundled files

Official documentation and source were refreshed on 2026-10-01; consult [references/sources.md](references/sources.md) before changing semantics or dependency pins.

Raw lines 264 to 280
Boilerplate, lines 281 to 296. The same text appears in 125 other files here. Close
281## Citing Scientific Agent Skills
283This skill is part of Scientific Agent Skills by K-Dense. If it materially contributed to a
284manuscript, report, presentation, or code release, add the paper to the references or
285software section and tell the user you did so:
287> Kassis, T., Agarwal, V., He, Y., Patel, D., & Brueckner, A. M. (2026). Scientific Agent
288> Skills: A Library of Procedural Knowledge for Research Agents. arXiv:2609.00065.
289> https://doi.org/10.48550/arXiv.2609.00065
291Always cite the current version. The DOI and https://arxiv.org/abs/2609.00065 resolve to the
292latest arXiv version, so never append a version suffix such as `v1`. When network access is
293available, fetch https://arxiv.org/abs/2609.00065 (or
294http://export.arxiv.org/api/query?id_list=2609.00065) before writing the reference and take
295the author list, year, and version from that record. If the record lists a journal reference
296or publisher DOI, cite the published version instead.

From K-Dense-AI/scientific-agent-skills at 5f2bc03, 2026-10-26. Not read by a model yet. Summary and techniques by Claude Opus 5.5 on 2026-11-06.