smithery.ai

cairo-contract-functions

Explain Starknet contract entry points (external, view, constructor, l1 handler) and ABI configuration; use when a request involves defining or exposing contract functions in Cairo.

First seen Apr 4, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,022 B
  • docs SUMMARY.md 213 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Cairo Contract Functions

Overview

Guide how to define contract entry points and control ABI exposure in Cairo.

Quick Use

  • Read references/contract-functions.md before answering.
  • Use #[starknet::interface] with #[abi(embed_v0)] for standard ABI definitions.
  • Use self: ContractState for view, ref self: ContractState for state-mutating entry points.

Response Checklist

  • Mark constructors with #[constructor] and L1 handlers with #[l1_handler].
  • Use #[external(v0)] for public entry points if using per-item ABI.
  • Explain that view functions are not enforced by the protocol.

Example Requests

  • "How do I define a view function vs external function?"
  • "Where do I put a constructor in a Cairo contract?"
  • "How do I expose a function in the ABI?"