Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓

Ethereum Base Smart Contract Security Capability Pack Skill

Expert EVM capability skill for secure contract architecture across Ethereum and Base, including Foundry testing and operational controls.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/ethereum-base-smart-contract-security-capability-pack
Source URLs
https://docs.base.org/get-started/deploy-smart-contracts, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/ethereum-base-smart-contract-security-capability-pack.mdx
Package URL
/downloads/skills/ethereum-base-smart-contract-security-capability-pack.zip
Package SHA256
3f10c007835d0f339dc11a96b12cc7951032f9d14ce505951d2c0bf0f43d4312
Safety notes
Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible., Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.
Privacy notes
Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context., Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

91/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime1General2

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyExecution & processesDo not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible.
  • SafetyCredentials & tokensUse local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.
  • PrivacyGeneralPrompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context.
  • PrivacyCredentials & tokensNever paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.

Safety notes

  • Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible.
  • Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.

Privacy notes

  • Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context.
  • Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.

Prerequisites

  • Solidity codebase and deployment scripts
  • Security requirements and risk tolerance
  • Testnet staging environment

Schema details

Install type
package
Reading time
10 min
Difficulty score
91
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
3f10c007835d0f339dc11a96b12cc7951032f9d14ce505951d2c0bf0f43d4312
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-10
Retrieval sources
https://ethereum.org/developers/docs/https://book.getfoundry.sh/https://docs.openzeppelin.com/contractshttps://docs.base.org/get-started/deploy-smart-contracts
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Use the Ethereum/Base smart contract security capability pack for this protocol."

# Required output
1) Threat model and trust assumptions
2) Contract architecture and invariants
3) Foundry test/fuzz/invariant suite plan
4) Deployment and incident response checklist

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.

Retrieval Sources

Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.

Core Workflow

  1. Confirm target version/runtime and pull latest official docs for the task scope.
  2. Build an execution plan with explicit read-only discovery before any mutation.
  3. Validate contracts, permissions, and safety constraints before applying changes.
  4. Execute with deterministic checkpoints and rollback criteria.
  5. Produce a verification report with evidence, caveats, and next actions.

Overview

This capability pack teaches agents to reason about Solidity security at protocol depth across Ethereum and Base environments. It combines architecture discipline, robust testing, and safer operational rollout.

Capability Scope

  • Threat modeling and trust assumptions
  • Permission and upgrade model hardening
  • Arithmetic/oracle/reentrancy/griefing defense strategies
  • Foundry unit/fuzz/invariant methodology
  • Deployment, monitoring, and emergency controls

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Treat invariant violations as release blockers.
  • Minimize privileged operations and centralization risk.
  • Verify deployment config parity with audited assumptions.
  • Maintain emergency pathways (pause/kill-switch) with governance constraints.

Troubleshooting

Issue: Safe tests pass but adversarial behavior still possible
Fix: Expand fuzz + invariant suites and include cross-contract interaction scenarios.

Issue: Upgrade path introduces hidden risk
Fix: Add storage-layout and permission diff checks to release gating.

Issue: Incident response is untested
Fix: Simulate emergency controls before mainnet launch.

Output Contract

  1. Provide an implementation plan ordered by risk and dependency.
  2. Provide exact production-ready config/commands with no placeholders.
  3. Call out secrets, permissions, and least-privilege requirements.
  4. Include rollback and recovery guidance for each risky step.

Validation Checklist

  • Verify all referenced docs/versions before applying changes.
  • Run regression checks for core user flow and error paths.
  • Confirm observability/logging is enabled for changed components.
  • Confirm security controls (auth, rate limits, input validation) still pass.
  • Record final known limitations and follow-up actions.
#ethereum#base#solidity#security#capability-pack

Source citations

Add this badge to your README

Show that Ethereum Base Smart Contract Security Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/ethereum-base-smart-contract-security-capability-pack.svg)](https://heyclau.de/entry/skills/ethereum-base-smart-contract-security-capability-pack)

How it compares

Ethereum Base Smart Contract Security Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field
Ethereum Base Smart Contract Security Capability Pack Skill

Expert EVM capability skill for secure contract architecture across Ethereum and Base, including Foundry testing and operational controls.

Open dossier
Ethereum Solidity Security Foundry Skill

Build and harden Ethereum smart contracts with Foundry, invariant testing, and battle-tested OpenZeppelin security patterns.

Open dossier
Base L2 Smart Contract Launchpad Skill

Ship smart contracts on Base with secure deployment, verification, environment management, and production-readiness checklists.

Open dossier
GitHub logoGitHub Actions Secure CI/CD Capability Pack Skill

Expert GitHub Actions capability skill for secure workflow architecture, token minimization, supply-chain controls, and CI reliability.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verified2026-04-10Package verified2026-04-10Package verified2026-04-10Package verified2026-04-10
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter————
Install riskReview firstLow riskLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand———GitHub logoGitHub
Categoryskillsskillsskillsskills
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorJSONboredJSONboredJSONboredJSONbored
Added2026-04-102026-04-102026-04-102026-04-10
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
Privacy notes✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
Prerequisites
  • Solidity codebase and deployment scripts
  • Security requirements and risk tolerance
  • Testnet staging environment
  • Solidity project initialized with Foundry
  • Clear protocol/token specification
  • Target chain and deployment constraints
  • Solidity contracts and deployment scripts
  • Base testnet/mainnet environment variables
  • Defined ownership, admin, and upgrade strategy
  • Existing workflows or target CI/CD architecture
  • Branch protection and environment policy context
  • Security/compliance requirements
Install
curl -L https://heyclau.de/downloads/skills/ethereum-base-smart-contract-security-capability-pack.zip -o ethereum-base-smart-contract-security-capability-pack.zip && unzip -o ethereum-base-smart-contract-security-capability-pack.zip -d ./ethereum-base-smart-contract-security-capability-pack
curl -L https://heyclau.de/downloads/skills/ethereum-solidity-security-foundry.zip -o ethereum-solidity-security-foundry.zip && unzip -o ethereum-solidity-security-foundry.zip -d ./ethereum-solidity-security-foundry
curl -L https://heyclau.de/downloads/skills/base-l2-smart-contract-launchpad.zip -o base-l2-smart-contract-launchpad.zip && unzip -o base-l2-smart-contract-launchpad.zip -d ./base-l2-smart-contract-launchpad
curl -L https://heyclau.de/downloads/skills/github-actions-secure-cicd-capability-pack.zip -o github-actions-secure-cicd-capability-pack.zip && unzip -o github-actions-secure-cicd-capability-pack.zip -d ./github-actions-secure-cicd-capability-pack
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev
guides

Claude Code in Regulated Finance Environments

Deploy Claude Code in security-sensitive finance environments.

Review firstSource-backedReview firstAdded 8mo ago
Safety ✓ Privacy ✓by JSONbored

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.