typescript-eval

Execute TypeScript snippets with bun and report stdout/stderr.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill typescript-eval-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-eval
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/typescript-eval
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill typescript-eval-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken or unsafe TypeScript skills by letting you test code snippets locally before saving them as managed skills.

Core Features & Use Cases

  • Snippet-first evaluation: Run TypeScript stored in a temporary file to quickly validate correctness.
  • Function-based testing support: Execute exported default or run functions via a small runner to inspect returned results.
  • Guardrails for persistence: Enforces explicit user consent before persisting and avoids unsafe iteration loops.

Quick Start

Ask the assistant to evaluate your TypeScript snippet by creating a temporary file, running it with bun using a short timeout, and reporting stdout/stderr so you can decide whether to persist it.

Frequently Asked Questions about typescript-eval

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

FAQPage Schema
How do I test a TypeScript snippet before saving it as a skill?

To test a TypeScript snippet before saving it, you execute the code in a temporary file using bun, capturing stdout and stderr to verify behavior and prevent persisting broken skill implementations.

Can I run exported functions in TypeScript for rapid local testing?

Yes, you can run exported default or run functions for rapid local testing by using a small runner that executes the TypeScript snippet via bun and reports the returned results directly.

Does TypeScript snippet evaluation require explicit user consent to persist?

Yes, TypeScript snippet evaluation requires explicit user consent to persist because it enforces guardrails that prevent unsafe iteration loops and avoid automatically saving code without permission.

What is the best way to verify TypeScript snippet behavior without risking broken files?

The best way to verify TypeScript snippet behavior safely is by using a temporary file workflow with bun, applying short timeouts to execute standalone snippets before deciding to persist them.

Are there limitations when using bun to evaluate TypeScript code snippets?

Limitations when using bun to evaluate TypeScript code include enforced short timeouts for execution and strict iteration guardrails, making it suitable only for standalone snippets rather than long-running processes.