test-as-self

Validate throwaway Instar deployments and detect health regressions from lease and log artifacts.

75|18|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/JKHeadley/instar --skill test-as-self
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-as-self
Source: https://github.com/JKHeadley/instar/tree/main/.claude/skills/test-as-self
Command: npx skills add https://github.com/JKHeadley/instar --skill test-as-self

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you confirm that a fresh Instar deployment starts correctly, owns the right polling behavior, and fails visibly when something is broken, instead of forcing you to debug from scattered logs after the fact.

Core Features & Use Cases

  • Throwaway Deploy Verification: Deploys Instar into a disposable agent home so you can safely validate changes before or after shipping.
  • Lease and Health Checks: Confirms the Telegram poll-ownership lease exists, is fresh, is well formed, and does not expose the raw bot token.
  • Deterministic Crash Detection: Scans server and lifeline logs for fatal, memory, and abort signatures so crash analysis is reproducible.
  • Use Case: Run this when you change the deploy, lifeline, or startup path and want a clean PASS or FAIL report from a controlled test agent.

Quick Start

Ask the agent to run the test-as-self verification against a throwaway Instar directory and report whether the deploy is healthy.

Frequently Asked Questions about test-as-self

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

FAQPage Schema
How do I verify a Telegram bot polling deployment without exposing the raw token?

You can verify a Telegram polling deployment by checking the Instar lease artifacts in a throwaway agent directory. This process confirms the lease exists, is fresh, and does not expose the raw bot token.

What is the best way to detect health regressions after shipping an agent deploy?

Detecting health regressions after shipping requires running a verification script against a disposable agent home. It checks server and lifeline logs for fatal, memory, and abort signatures to reproduce crash analysis.

How do I check if my Instar lifeline and server startup logs are healthy?

Checking Instar lifeline and server startup logs involves scanning them for deterministic crash detection signatures. The verification confirms the startup path is healthy and produces a clean PASS or FAIL report.

What files do I need to validate a throwaway agent deployment directory?

Validating a throwaway agent deployment directory requires .instar lease artifacts, server and lifeline logs, and a valid lease schema. These files must be present with a fresh heartbeat to run the verification.

Why does my self-propagation harness check fail after a fresh deployment?

A self-propagation harness check fails after deployment if the Telegram poll-ownership lease is malformed or lacks a fresh heartbeat. It also fails visibly if server or lifeline logs contain fatal crash signatures.

Can I run crash reproduction tests in a disposable agent home?

Yes, you can run crash reproduction tests in a disposable agent home. The verification process scans server and lifeline logs for fatal, memory, and abort signatures to make crash analysis reproducible.