metabolic-tracker

Record and analyze per-invocation token, tool, and context signals into YAML logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of understanding how much energy (token/tool work) and value (quality/efficiency) each Being Skill invocation produces, so you can evaluate fitness and detect regressions.

Core Features & Use Cases

  • Record per-invocation metabolism: Logs tokens in/out, tool call counts, context size, products (primary/byproducts/waste), and outcome (success, optional quality, computed efficiency).
  • Generate aggregated statistics: Produces per-skill summaries including totals, averages, success rate, and energy trend comparisons (last 5 vs historical average).
  • Run metabolic comparisons: Outputs an efficiency and reliability comparison report across multiple skills to support selection pressures in overlapping niches.

Quick Start

Use metabolic-tracker after running any Skill so it records that invocation’s metabolism into .being/metabolism/ for later stats and comparison.

Frequently Asked Questions about metabolic-tracker

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

FAQPage Schema
How do I track token usage and efficiency for skill invocations?

You can track skill invocation metabolism by recording tokens in, tokens out, tool call counts, and context size into YAML log files. The tool then computes aggregated statistics and efficiency metrics deterministically from those stored records.

What is metabolic tracking for skill execution and why is it needed?

Metabolic tracking for skill execution quantifies the energy use and output value of each run by logging token and tool work. It is needed to evaluate skill fitness, measure efficiency, and detect performance regressions over time.

How do I log skill execution data to YAML for later analysis?

You log skill execution data to YAML by running the tracker after any skill invocation. It extracts token, tool, and context signals, classifies products, and appends a detailed YAML record to the .being/metabolism/ directory for later analysis.

Can I compare efficiency and reliability across multiple skills?

You can compare efficiency and reliability across multiple skills by generating a metabolic comparison report. The tracker uses stored YAML log data to output comparative metrics that support selection pressures in overlapping niches.

Does metabolic tracking require any dependencies to run?

Metabolic tracking requires no dependencies to run. The tracker operates independently to read metabolism protocol guidance, extract invocation signals, and generate statistics deterministically from stored YAML logs.

What statistics are generated from skill metabolism logs?

Statistics generated from skill metabolism logs include per-skill totals, averages, success rates, and energy trend comparisons. The tracker compares the last 5 invocations against the historical average to identify recent performance shifts.