algorand-ts-migration

Migrate Algorand smart contracts to TypeScript 1.0 from TEALScript or Beta.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/KudbeeZero/Algo-Unify-Dev --skill algorand-ts-migration-kudbeezero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: algorand-ts-migration
Source: https://github.com/KudbeeZero/Algo-Unify-Dev/tree/main/.claude/skills/algorand-ts-migration
Command: npx skills add https://github.com/KudbeeZero/Algo-Unify-Dev --skill algorand-ts-migration-kudbeezero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This migration guide helps teams convert Algorand smart contracts from TEALScript or Algorand TypeScript Beta into Algorand TypeScript 1.0, ensuring code modernization and compatibility with Puya 1.0 APIs.

Core Features & Use Cases

  • Guided migration steps: Step-by-step checklist covering imports, logic signatures, inner transactions, and type changes.
  • Reference material: Access to migration references and examples for beta to 1.0 and TEALScript to 1.0 transitions.
  • Practical scenarios: Suitable for projects updating existing contracts or starting new contracts with 1.0 tooling and APIs.

Quick Start

Begin the migration by selecting a TEALScript or Beta contract, then follow the corresponding references and checklist to produce a 1.0-compatible version.

Frequently Asked Questions about algorand-ts-migration

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

FAQPage Schema
How do I migrate Algorand smart contracts from TEALScript to TypeScript 1.0?

To migrate Algorand smart contracts from TEALScript to TypeScript 1.0, follow a step-by-step checklist covering imports, logic signatures, inner transactions, and type changes to ensure compatibility with Puya 1.0 APIs. Updated references guide the transition.

What is the process for converting Algorand TypeScript Beta codebases to version 1.0?

Converting Algorand TypeScript Beta codebases to version 1.0 involves updating imports, enforcing updated APIs, and applying type changes. The migration provides a practical checklist and directs users to specific references for achieving code parity.

Does Algorand TypeScript 1.0 migration support inner transactions and logic signatures?

Yes, Algorand TypeScript 1.0 migration fully supports inner transactions and logic signatures. The migration checklist explicitly covers the required type changes and API updates needed to transition these features from TEALScript or Beta.

What's the best way to update imports and types when migrating to Algorand TypeScript 1.0?

The best way to update imports and types during Algorand TypeScript 1.0 migration is to follow the guided checklist that enforces updated Puya APIs. This checklist provides specific references and examples for accurate type conversion.

Why do I need a migration checklist for Algorand TypeScript Beta to 1.0 transitions?

You need a migration checklist for Algorand TypeScript Beta to 1.0 transitions to systematically address breaking changes in imports, logic signatures, and inner transactions. It ensures code modernization and achieves parity with Puya 1.0 APIs.