call-smart-contracts

Deploy and interact with Algorand smart contracts using AlgoKit and TypeScript clients.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/SomehowLiving/Acre --skill call-smart-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: call-smart-contracts
Source: https://github.com/SomehowLiving/Acre/tree/main/.agents/skills/call-smart-contracts
Command: npx skills add https://github.com/SomehowLiving/Acre --skill call-smart-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploy and interact with Algorand smart contracts across localnet, testnet, and mainnet, enabling developers to move from contract ideas to runnable integration quickly.

Core Features & Use Cases

  • Build, deploy, and script interactions using the AlgoKit CLI and the generated TypeScript client.
  • Read global/local/box state and manage opt-in/close-out flows within end-to-end workflows.
  • Use cases include testing contracts locally, validating deployment pipelines, and scripting automated interaction scenarios.

Quick Start

Deploy a contract to localnet and begin calling methods with the generated TypeScript client.

Frequently Asked Questions about call-smart-contracts

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

FAQPage Schema
How do I deploy and interact with Algorand smart contracts across localnet, testnet, and mainnet?

You can deploy and interact with Algorand smart contracts by using the AlgoKit CLI alongside a generated TypeScript client to build, deploy, and script contract interactions across networks.

Do I need AlgoKit to build and script Algorand smart contract interactions?

Yes, AlgoKit is required. The workflow relies on AlgoKit tooling, generated TypeScript clients, and environment-configured accounts to build and script smart contract interactions.

Can I read global, local, and box state when scripting Algorand smart contract calls?

Yes, you can read global, local, and box state. The workflow supports reading contract state and managing opt-in or close-out flows within end-to-end interaction scripts.

What's the best way to test Algorand smart contracts locally before mainnet deployment?

The best way to test Algorand smart contracts locally is deploying to localnet using the AlgoKit CLI, then validating deployment pipelines and scripting automated interactions with the TypeScript client.

How do I manage opt-in and close-out flows for Algorand smart contracts in TypeScript?

You manage opt-in and close-out flows by scripting these interactions end-to-end using the generated TypeScript client, which handles the account logic and network calls for the smart contract.