How do I install the Self Observe skill?

Run npx skillmds@latest add pipixia-labs/self-observe in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Self Observe safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Self Observe?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Self Observe free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Self Observe?

pipixia-labs (@pipixia-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Self Observe by pipixia-labs — Agent Skill

Name: Self Observe
Author: pipixia-labs

File contents

Self Observe Skill

Use this skill when the user asks for agent self-inspection, runtime health checks, or diagnostics such as token cost, error logs, and service status.

What To Check

Token usage:

otw operations usage --json
otw operations usage --provider google --limit 50 --json
otw operations usage --provider openai --limit 50 --json

Runtime status:

otw operations status --json
otw operations health --json
otw operations heartbeat status --json
otw operations cron list --json

Error logs (read-only):

tail -n 200 ~/.openteamwork/logs/node.err.log
rg -n "ERROR|Error|Traceback|Exception|failed|timeout" ~/.openteamwork/logs/node.err.log ~/.openteamwork/logs/node.out.log

SQLite quick verification (if sqlite3 exists):

sqlite3 ~/.openteamwork/database/token_usage.db "SELECT provider, COUNT(*) AS requests, SUM(total_tokens) AS total_tokens FROM llm_token_usage_events GROUP BY provider ORDER BY total_tokens DESC;"
sqlite3 ~/.openteamwork/database/token_usage.db "SELECT response_at, provider, model, request_tokens, response_tokens, total_tokens FROM llm_token_usage_events ORDER BY response_at_ms DESC LIMIT 20;"

Fast Path

Generate one consolidated report:

bash openppx/skills/self-observe/scripts/self_status_report.sh

Output Format

When reporting to user, include:

Runtime Summary: Node/heartbeat/cron health highlights.
Token Summary: total requests/tokens and provider split.
Recent Errors: latest error signatures with file and timestamp.
Risks: what might break soon (missing usage data, repeated failures, disconnected provider).
Next Actions: concrete commands to validate/fix.

Guardrails

Keep checks read-only by default.
Do not delete or truncate logs unless the user explicitly asks.
If status/log files are missing, report "not found" explicitly instead of guessing.
Prefer structured output (--json) first, then summarize in natural language.

---name: self-observedescription: Observe OpenTeamwork Node health with usage, automation status, audit facts, logs, and quick diagnostics.---# Self Observe SkillUse this skill when the user asks for agent self-inspection, runtime health checks, or diagnostics such as token cost, error logs, and service status.## What To Check1. Token usage:```bashotw operations usage --jsonotw operations usage --provider google --limit 50 --jsonotw operations usage --provider openai --limit 50 --json```2. Runtime status:```bashotw operations status --jsonotw operations health --jsonotw operations heartbeat status --jsonotw operations cron list --json```3. Error logs (read-only):```bashtail -n 200 ~/.openteamwork/logs/node.err.logrg -n "ERROR|Error|Traceback|Exception|failed|timeout" ~/.openteamwork/logs/node.err.log ~/.openteamwork/logs/node.out.log```4. SQLite quick verification (if `sqlite3` exists):```bashsqlite3 ~/.openteamwork/database/token_usage.db "SELECT provider, COUNT(*) AS requests, SUM(total_tokens) AS total_tokens FROM llm_token_usage_events GROUP BY provider ORDER BY total_tokens DESC;"sqlite3 ~/.openteamwork/database/token_usage.db "SELECT response_at, provider, model, request_tokens, response_tokens, total_tokens FROM llm_token_usage_events ORDER BY response_at_ms DESC LIMIT 20;"```## Fast PathGenerate one consolidated report:```bashbash openppx/skills/self-observe/scripts/self_status_report.sh```## Output FormatWhen reporting to user, include:1. Runtime Summary: Node/heartbeat/cron health highlights.2. Token Summary: total requests/tokens and provider split.3. Recent Errors: latest error signatures with file and timestamp.4. Risks: what might break soon (missing usage data, repeated failures, disconnected provider).5. Next Actions: concrete commands to validate/fix.## Guardrails- Keep checks read-only by default.- Do not delete or truncate logs unless the user explicitly asks.- If status/log files are missing, report "not found" explicitly instead of guessing.- Prefer structured output (`--json`) first, then summarize in natural language.

Frequently asked questions

Self Observe