Locate Animals or Plants
Find what is alive, where it lives, and what it is feeding on.
What This Skill Does
Locate Animals or Plants is service discovery with ecological instincts. It helps you find running services, background jobs, data stores, dependency roots, and other living things in an environment before you touch them. The point is not just location, but context: what is active, who depends on it, and what keeps it alive.
In this grimoire, Locate Animals or Plants is treated as a metaphorical spell with a shipping-now delivery profile.
Canonical reference input: Locate Animals or Plants (spell).
When To Use
- You need an inventory of active services, dependencies, or data flows in an unfamiliar environment.
- The problem involves discovering what is running rather than debugging one known component.
- You suspect there are hidden dependencies or stale registrations mixed in with live systems.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Sweep the environment for active services, scheduled jobs, stores, queues, and known dependency markers.
- Trace the discovered components to the systems they depend on or feed.
- Return a live-system map with confidence levels and any blind spots in the survey.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A discovery map of live services and dependencies.
- A shortlist of the most likely roots, leaves, and chokepoints.
- A confidence note on stale entries, missing telemetry, or unobservable zones.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not mistake stale config, dead DNS, or abandoned containers for living systems without corroborating signals.
- Stay within authorized discovery boundaries when scanning networks or environments.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/locate-animals-or-plants discover what services and dependencies are alive in this environment and how they connect
1---2name: locate-animals-or-plants-23description: Locate Animals or Plants is service discovery with ecological instincts. It helps you find running services, background jobs, data stores, dependency roots, and other living things in an environment before you touch them. The point is not just location, but context: what is active, who depends on it, and what keeps it alive.4license: CC0-1.05---6# Locate Animals or Plants7Find what is alive, where it lives, and what it is feeding on.8## What This Skill Does9Locate Animals or Plants is service discovery with ecological instincts. It helps you find running services, background jobs, data stores, dependency roots, and other living things in an environment before you touch them. The point is not just location, but context: what is active, who depends on it, and what keeps it alive.10In this grimoire, Locate Animals or Plants is treated as a metaphorical spell with a shipping-now delivery profile.11Canonical reference input: Locate Animals or Plants (spell).12## When To Use1314- You need an inventory of active services, dependencies, or data flows in an unfamiliar environment.15- The problem involves discovering what is running rather than debugging one known component.16- You suspect there are hidden dependencies or stale registrations mixed in with live systems.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Sweep the environment for active services, scheduled jobs, stores, queues, and known dependency markers.263. Trace the discovered components to the systems they depend on or feed.274. Return a live-system map with confidence levels and any blind spots in the survey.285. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.2930## Deliverables3132- A discovery map of live services and dependencies.33- A shortlist of the most likely roots, leaves, and chokepoints.34- A confidence note on stale entries, missing telemetry, or unobservable zones.3536## Pitfalls / Guardrails3738- Keep the metaphor anchored to a real mechanism instead of drifting into lore.39- Do not mistake stale config, dead DNS, or abandoned containers for living systems without corroborating signals.40- Stay within authorized discovery boundaries when scanning networks or environments.4142## Verification4344- Check that the result includes every deliverable promised above.45- Check that confirmed facts, assumptions, and inferences are visibly separated.46- Check that the metaphor still maps cleanly to a real operational mechanism.4748## Example Invocation49```text50/locate-animals-or-plants discover what services and dependencies are alive in this environment and how they connect51```
Hmbown