skills.rest
ofelixdev
ofelixdevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

entry-point-analyzer

Detect state-changing entry points in smart contract codebases.

Updated Feb 24, 2026
Search Tags:#access control#security audit#smart contract#solidity#entry points#state-changing functions#vyper
One-click install
npx skills add https://github.com/ofelixdev/cc-kit --skill entry-point-analyzer-ofelixdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: entry-point-analyzer
Source: https://github.com/ofelixdev/cc-kit/tree/main/template/skills/entry-point-analyzer
Command: npx skills add https://github.com/ofelixdev/cc-kit --skill entry-point-analyzer-ofelixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill systematically identifies all state-changing entry points in smart contract codebases, crucial for security audits by mapping the attack surface.

Core Features & Use Cases

  • State-Changing Function Identification: Detects and categorizes functions that modify contract state, excluding read-only operations.
  • Access Control Analysis: Classifies functions by access level (public, role-restricted, contract-only).
  • Multi-Language Support: Analyzes Solidity, Vyper, Solana, Move, TON, and CosmWasm.
  • Use Case: When starting a smart contract security audit, use this Skill to get a comprehensive list of all functions that can alter contract state, along with their access controls, to prioritize testing.

Quick Start

Use the entry-point-analyzer skill to analyze the smart contracts in the current directory for state-changing functions.

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 for a smart contract security audit?▼

Mapping smart contract attack surfaces involves detecting externally callable functions that alter state and classifying them by access controls like public or role-restricted. It is needed when prioritizing security testing to focus on functions that can modify contract state.

Can I analyze Vyper and Solidity smart contracts for externally callable functions?▼

Yes, you can analyze Vyper and Solidity smart contracts for externally callable functions. The analysis detects state-changing functions across multiple blockchain languages, categorizing them by access level while filtering out read-only operations to generate structured audit reports.

Does the entry-point analyzer exclude view and pure functions from the audit report?▼

To start mapping your contract's attack surface, use the analyzer to scan the smart contracts in your current directory. It will process the codebase, identify state-changing functions, categorize them by access level, and output a structured audit report for security testing.

What is the best way to categorize smart contract functions by access level for an audit?▼

The best way to categorize smart contract functions by access level for an audit is to use an analyzer that classifies state-changing functions as public, role-restricted, or contract-only. This structured approach prioritizes testing for externally callable vulnerabilities.

Related Skills

Explore More Software Engineering Skills→
iiammaeiiammae

entry-point-analyzer

Analyze smart contract codebases for state-changing entry points across multiple languages.

Community
Advanced
carlheathcarlheath
9

Security Specialist

Assess software and infrastructure security vulnerabilities and threats.

Community
Advanced
manuelbrandner85manuelbrandner85

entry-point-analyzer

Identify and categorize state-changing entry points in smart contract codebases.

Community
Advanced
telihateliha

Smart Contract Security Audit

Audit Solidity smart contracts for security vulnerabilities and generate Markdown reports.

Official
Advanced