presence-check

Read vitals.yaml and tree.yaml to summarize operational readiness evidence.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/scilid/Being --skill presence-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: presence-check
Source: https://github.com/scilid/Being/tree/main/organisms/prokaryotes/presence-check
Command: npx skills add https://github.com/scilid/Being --skill presence-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It determines whether Being has completed at least one real execution loop by checking recorded runtime truth sources and producing an evidence-based readiness snapshot.

Core Features & Use Cases

  • Vitals-based operational status: Reads .being/homeostasis/vitals.yaml to extract structural and operational status plus metabolism totals and last activity.
  • Phylogeny-based lifecycle readiness: Reads .being/phylogeny/tree.yaml to confirm there is at least one operational_state: "recorded" Skill and to identify recent major transitions and newly born-but-unrun Skills.
  • Evidence-first readiness reporting: Outputs a concise report and explicitly returns insufficient-evidence when the required facts are not available.

Quick Start

Use the presence-check Skill to generate a readiness snapshot that reports whether Being is operationally-alive based on the latest vitals and phylogeny evidence.

Frequently Asked Questions about presence-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify if my system has completed a real execution loop?

A readiness snapshot confirms operational lifecycle status by reading vitals.yaml and tree.yaml to extract structural and operational data, explicitly returning insufficient-evidence when required facts are missing.

How do I check homeostasis and operational status from metabolism logs?

Checking homeostasis and operational status involves reading vitals.yaml to extract structural_status, operational_status, total_invocations, and last_activity, summarizing these metabolism logs into a readiness snapshot.

What happens when runtime validation lacks sufficient evidence for a readiness audit?

During a readiness audit, if tree.yaml lacks a recorded operational_state or vitals.yaml is missing last_activity, the validation explicitly returns an insufficient-evidence output instead of a readiness snapshot.

How do I identify newly born-but-unrun skills using phylogeny data?

Identifying newly born-but-unrun skills involves reading the phylogeny in tree.yaml to check for recorded operational states, pinpointing recent major transitions, and isolating skills without recorded execution.

Does a readiness snapshot require both vitals and phylogeny sources?

A readiness snapshot requires both vitals.yaml for structural and operational status plus tree.yaml for phylogeny-based lifecycle readiness, ensuring a complete heartbeat-like proof of execution.