Skip to content
Skills Library
DevOps & cloud · Analysis

environment-intelligence

/environment-intelligence

Discover and reuse the current machine’s tools, runtime, hardware, network capabilities and dependencies; acquire missing trusted tools when needed rather than compromising the technical route. Use when environmental constraints, setup, downloads or tool selection affect a task.

Licence
MIT
Last repository change
01.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Discover and reuse the current machine’s tools, runtime, hardware, network capabilities and dependencies; acquire missing trusted tools when needed rather than compromising the technical route. Use when environmental constraints, setup, downloads or tool selection affect a task.

Original author description

Discover and reuse the current machine’s tools, runtime, hardware, network capabilities and dependencies; acquire missing trusted tools when needed rather than compromising the technical route. Use when environmental constraints, setup, downloads or tool selection affect a task.

How it works

SKILL.md has no level-two headings · 16 lines, 248 words

SKILL.md preview
---
name: environment-intelligence
description: Discover and reuse the current machine’s tools, runtime, hardware, network capabilities and dependencies; acquire missing trusted tools when needed rather than compromising the technical route. Use when environmental constraints, setup, downloads or tool selection affect a task.
license: MIT
---

# Let the environment serve the task

**Purpose.** A missing tool is normally a solvable setup issue, not proof that the user's preferred outcome is impossible.

- Inspect only relevant capabilities first: OS, architecture, runtime, CPU/GPU/memory, tool paths/versions, permissions, available services, network/proxy configuration, storage and installed integrations.
- On first encounter with an environment, build a lightweight **capability index**; on subsequent tasks read it and verify affected entries rather than rescanning everything.
- Look for mature, suitable tools by **capability class** (search, build, rendering, media, network routing, debugging, download, automation), not by a hardcoded product list.
- Prefer a working existing tool; otherwise research and obtain an appropriate trusted dependency when access allows. Check provenance, compatibility, licenses, space/time cost and conflicts. Never silently turn off protection or change system-wide routing without appropriate permission.
- Treat network failures as diagnosable: inspect endpoints, DNS, proxy/routing settings, credentials, ports, trust and mirrors before abandoning a sound technical route.
- Save only useful operational knowledge: capability, verified invocation, path/version where relevant, working context, limitations and last checked date. Never store passwords or secrets in a tool wiki.
- A capability catalog is **evidence of this environment**, not a universal installation command list.

**Success:** tasks select the best viable route using actual available capabilities, and future tasks benefit from the discovery without wasteful repeated probing.
**Avoid:** “I cannot do it because the package is not already installed” when it can legitimately be installed, and “install everything” when the task needs only one tool.

Versions

The database has no other skills named environment-intelligence.

Database snapshot: 13.11.2026 · package version 87f5725fffe5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90preflight
    Use when checking whether the current execution environment is ready for a project's development work, including missing tools, incompatible versions, and setup blockers.
  • 100platform-environment-validate
    Validate and configure the local Salesforce development environment. Runs a prerequisite scan across required tools with per-tool status and offers to install or update missing items. Use when the user asks to 'check my setup', 'validate tools', 'verify prerequisites', 'am I set…
  • 100env-adoption
    Use when checking tool availability (Codex, Antigravity CLI (agy), Copilot, gh, Docker), determining environment tier, reading cached inventory or session state, setting up missing tools, or when any skill needs to know what capabilities are available in the current environment.
  • 100sentinel-env
    Environment-aware pre-flight check. Use when starting work in a new environment, switching machines, or when 'works on my machine' bugs surface. Validates OS, runtime versions, installed tools, port availability, env vars, and disk space BEFORE coding starts. Like sentinel but…
  • 100research-environment-vs-production-environment-parity
    Use when promoting a model or feature pipeline out of notebooks into live execution and the question is whether production computes the same number, auditing runtime, package and data-path parity vectors. Deployment gating is environment-parity-dev-staging-production.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.