get-available-resources
Detect 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.
npx skills add K-Dense-AI/scientific-agent-skills --skill get-available-resources --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## 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
- Safety contract
- Quick start
- Ephemeral stdout snapshot
- Explicit private file
- Optional psutil enhancement
- Skip management-tool probes
- Required interpretation
- CPU
- Memory
- Accelerators
- Disk
- Scheduler and container
- Plan a workload
- Validate or diff snapshots
python scripts/detect_resources.py python scripts/detect_resources.py --output resource-snapshot.json uv pip install "psutil==7.2.2" python scripts/detect_resources.py --skip-accelerators python scripts/plan_workload.py resource-snapshot.json \ python scripts/snapshot_tools.py validate resource-snapshot.json python scripts/snapshot_tools.py diff before.json after.json python scripts/accelerator_diagnostics.py resource-snapshot.json \
What does the get-available-resources skill do?
Detect 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.
How do I install it?
Run `npx skills add K-Dense-AI/scientific-agent-skills --skill get-available-resources --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From K-Dense-AI/scientific-agent-skills, a repository with 32,619 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.