entry-point-analyzer

Catalog state-changing entry points across smart contract codebases.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/erenisiklar/Pusula --skill entry-point-analyzer-erenisiklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entry-point-analyzer
Source: https://github.com/erenisiklar/Pusula/tree/main/.claude/skills/entry-point-analyzer
Command: npx skills add https://github.com/erenisiklar/Pusula --skill entry-point-analyzer-erenisiklar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and catalog state-changing entry points across smart contract codebases to guide security audits. It detects externally callable functions that modify state, categorizes them by access level (public, admin, role-restricted, contract-only), and generates structured audit reports. It excludes view/pure/read-only functions.

Core Features & Use Cases

  • Detects externally callable, state-changing entry points across languages (Solidity, Vyper, Solana, Move, TON, CosmWasm).
  • Classifies entry points by access level (public, role-restricted, admin, contract-only) and compiles an audit-ready report.
  • Supports generation of audit workflows and documentation for security reviews.

Quick Start

Analyze a codebase to enumerate all externally facing state-changing entry points and produce an audit-ready report.

Frequently Asked Questions about entry-point-analyzer

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

FAQPage Schema
How do I identify state-changing entry points in smart contracts for security audits?

Identify state-changing entry points by parsing externally callable functions that modify state, categorizing them by access level, and generating a structured audit report to guide security reviews.

Does the entry point analyzer work with Vyper, Solana, Move, and CosmWasm codebases?

Yes, the entry point analyzer supports Vyper, Solana, Move, TON, and CosmWasm codebases, alongside Solidity, to catalog externally callable state-changing functions across multiple smart contract languages.

What's the best way to catalog privileged operations and external calls for an audit report?

Catalog privileged operations and external calls by detecting externally callable functions, classifying them by access level such as admin or role-restricted, and compiling the results into audit-ready documentation.

Why does the entry point analyzer exclude view and pure read-only functions from the audit report?

The entry point analyzer excludes view and pure read-only functions because security audits focus on state-changing entry points where external calls and privileged operations can modify contract state and introduce vulnerabilities.

How do I generate an audit-ready report of access-control patterns across a smart contract codebase?

Generate an audit-ready report by analyzing the codebase to enumerate all externally facing state-changing entry points, categorizing access-control patterns, and outputting a structured document for security review.