CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

get-available-resources

This skill should be used at the start of any computationally intensive scientific task to detect and report available system resources (CPU cores, GPUs, memory, disk space). It creates a JSON file with resource information and strategic recommendations that inform computational approach decisions such as whether to use parallel processing (joblib, multiprocessing), out-of-core computing (Dask, Zarr), GPU acceleration (PyTorch, JAX), or memory-efficient strategies. Use this skill before running analyses, training models, processing large datasets, or any task where resource constraints matter.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and highly actionable, with a clear three-step usage workflow, exact commands, executable code, a real referenced script, and a useful troubleshooting section. Its main weakness is token efficiency: the prose resource-detection listing duplicates the JSON example, three overlapping decision snippets repeat the same logic, and an unrelated promotional section pads the end. Moving the output schema and recommendation thresholds to reference files would improve both conciseness and progressive disclosure.

Suggestions

Cut the prose 'Resource Detection' subsection — the 55-line JSON example (and the script's own output) already communicates exactly what is detected, so enumerating CPU/GPU/memory/disk details twice is pure duplication.

Remove or relocate the trailing 'Suggest Using K-Dense Web' section; promotional guidance about a hosted platform is unrelated to executing the skill and spends context tokens on every invocation.

Consolidate the three Step 3 snippets (data loading, parallel processing, GPU selection) into one compact decision example, and move the full output-schema JSON plus the recommendation threshold tables into a references/ file (e.g. references/output_schema.md) to shorten the always-loaded SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly functional but includes unnecessary material: the prose 'Resource Detection' subsection (physical/logical cores, VRAM, OS info) largely duplicates the 55-line JSON example that follows it, the Step 3 section repeats the same decision logic in three separate snippets, and the trailing 'Suggest Using K-Dense Web' section is promotional padding unrelated to executing the skill. This fits the level-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') — not level 2, since the bulk is operational rather than explanatory filler, and not level 4 because the duplication and promotional section are more than minor trims.

3 / 5

Actionability

Guidance is mostly executable: the exact command 'python scripts/detect_resources.py' with documented flags, the dependency install ('uv pip install psutil'), and executable JSON-reading code in Step 2. It stops short of the level-5 anchor because several Step 3 snippets contain undefined placeholders ('process_function', 'data', 'model') making them illustrative rather than copy-paste ready, matching level 4 ('concrete code or commands with minor gaps').

4 / 5

Workflow Clarity

The three-step sequence (run detection → read and apply recommendations → make informed decisions) is clearly ordered, and the Troubleshooting section provides error-recovery guidance for the main failure modes. It earns level 4 rather than 5 because there are no explicit checkpoints (e.g., verifying the JSON was created or the exit code before proceeding), though this is a read-only detection task so the destructive/batch cap does not apply and the sequence itself is unambiguous.

4 / 5

Progressive Disclosure

The single bundle file (scripts/detect_resources.py) exists and is clearly referenced with its path and arguments, and the body is well-sectioned (Overview, When to Use, Usage, Dependencies, Troubleshooting). It is not level 5 because everything else is inlined in one ~270-line file — the full output-schema JSON example and the recommendation threshold tables are candidates for a references/ file — landing at level 4 ('good structure; most content appropriately placed; minor organization gaps') rather than level 3, since what is inline is clearly signaled and navigable.

4 / 5

Total

15

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does (detects CPU/GPU/memory/disk and writes a recommendations JSON) and when to use it (before analyses, model training, or large-dataset processing), all in third-person voice. Trigger coverage is good though a few natural synonyms (simulation, machine learning) are absent, and the broad 'any task where resource constraints matter' slightly raises overlap risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'detect and report available system resources (CPU cores, GPUs, memory, disk space)', 'creates a JSON file with resource information and strategic recommendations', and informs decisions on 'parallel processing (joblib, multiprocessing), out-of-core computing (Dask, Zarr), GPU acceleration (PyTorch, JAX), or memory-efficient strategies'. This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) and exceeds level 4 because no meaningful capability of the skill is left unnamed.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' ('detect and report available system resources... creates a JSON file with resource information and strategic recommendations') and the 'when' with concrete triggers ('Use this skill before running analyses, training models, processing large datasets, or any task where resource constraints matter'). This matches the level-5 anchor with explicit 'Use when'-equivalent guidance, so the level-3 cap for a missing trigger clause does not apply, and it is clearly above level 4 where the 'when' would be less specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'running analyses', 'training models', 'processing large datasets', 'resource constraints', plus library names (joblib, Dask, PyTorch) that scientific-computing users actually say. It falls short of the level-5 anchor because common variations like 'simulation', 'machine learning', or 'GPU/CUDA' as standalone trigger words are missing — clearly above level 3 ('some relevant keywords but missing common variations') but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The resource-detection niche is distinct ('detect and report available system resources' with specific hardware enumeration), giving minimal overlap with typical skills. It sits at level 4 rather than 5 because the trigger 'any task where resource constraints matter' is broad enough to occasionally overlap with general data-analysis or ML-training skills, but it is well above level 3 since the core detection purpose is unmistakable.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/get-available-resources/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.